Introduction
“By failing to prepare, you are preparing to fail.” - Benjamin Franklin (American Icon)
In order to have a successful planning event (e.g. program increment planning), preparation is key. Bringing in the right information with the right amount of detail will ensure teams have the information they need to create a plan the entire program feels comfortable committing to during planning.
Decisions to make
- Identify the most valuable features to complete in the upcoming planning period
- Confirm that we have the right amount of appropriately-sized features for the upcoming planning period
- Decide whether the teams in the program are capable of delivering features by themselves
- Decide whether other teams outside of our program depend on our work to complete theirs
- Confirm that we are prepared to do planning without the benefit of having everyone in the same room
Context
- A backlog of features exist that can be targeted for the next planning period
- Features have been reviewed and the program has an understanding of which teams may be needed to support each feature
Why we care
- We want to right-size the amount of preparation
- We want to go into planning with the right work and a crisp message to set expectations for planning
- We want to scale execution beyond the team, even to the point where we can coordinate with external suppliers and vendors
The Atlassian view
- Jira Align provides a number of ways to align execution with strategy, including implementations of the popular scaling frameworks such as SAFe, LeSS, etc.
- While we should strive for autonomous teams capable of delivering value directly to the customer or end-user, we recognize the level of autonomy does vary in any organization
- Jira Align supports you through best-in-class dependency management
Next step:
Jobs to be doneWas this content helpful?
Connect, share, or get additional help
Atlassian Community