Skip to content

practices: planning backwards #42

@practicalli-johnny

Description

@practicalli-johnny

Some projects can benefit from planning backwards. Ensuring everyone has the same expectations early on and allowing focus on the most critical aspects.

Also helps to identify areas that need more investigation or where skills and understanding need to be grown for successful completion.

Establish what DONE looks like for everyone:

  • Define who the end users / stakeholders want
  • what does the project do when finished
  • establish a clear description of DONE that everyone understands and agrees on
  • how are you going to ensure that done is DONE

Work backwards to figure out the features and task needed to get to DONE

Identify milestones or phases if the project is more than a few weeks. Identify goals (or capability expected) for each milestone.

Remove any work that does not support getting DONE

Related

  • regular demos (at least one per milestone, ideally every week)

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions