Software
  • Introduction
  • Code craft
    • Clean code
    • Reusable code
    • Refactoring
    • Code smells
  • Service craft
  • Software Principles
  • Big Data
    • Introduction
    • Data modelling
  • Patterns
    • Enterprise patterns
    • Software patterns
  • Agile & proj management
    • Scrum vs Kanban
    • Kanban
    • Scrum
  • Conflict management
  • Reading
  • Software Architecture
    • Architecture components
Powered by GitBook
On this page
  • Objective of agile
  • Principles
  • Starting a project
  • Managing risks

Was this helpful?

Agile & proj management

Or baby steps project delivery

Objective of agile

  • Adapt to change in project priorities

  • Rapid release, and short time to market

  • Avoid burnout

  • Shift responsibilities from project manager to team

Principles

  • People over procedures

  • Working code over comprehensive documentation

  • Customer collaboration over contract negotiation

  • Responding to change over following a plan

Starting a project

  • Gather high level requirements from client/ stakeholder(s)

  • Define MVPs, or what has the highest priority to be delivered

  • Initial design with engineers

  • Draft a timeline based on initial tasks and deliverables

  • Run planning sessions to split the work into manageable chunks

  • Define definition of done

  • Define best practices and conventions

  • Choose programming languages, tools and applications

  • Setup a document management system (confluence)

  • Setup a board (kanban/scrum) (confluent)

  • organise code on a git server (github, gitlab, bitbucket)

  • define work automation (cicd) for rapid release

  • Setup test environment

Managing risks

PreviousSoftware patternsNextScrum vs Kanban

Last updated 5 years ago

Was this helpful?