Program discovery
Discovery
During discovery, the program leadership team must set expectations on the amount of organizational change they are willing (and able) to take on in the next several months. This conversation is best facilitated by enterprise coaches (or change leaders) that can assess the current state of the team-of-teams practices and choose an immediate path forward. A crawl-walk-run model can support these conversations and drive choices on the initial configuration of Atlassian products.
- Crawl: Program leadership team is still transitioning away from a project-based PMO and just seeks improved visibility into the work-in-process.
- Walk: Program leadership team is adopting new team-of-teams behaviors based on industry standards and curriculum.
- Run: Program leadership team is transforming to a leaner, product-led, outcome-oriented, value-driven, decision-making behavioral model.
For a deeper look at the topics that can be covered during the discovery consultation, explore the Program Discovery sections in Success Central.
Program discovery
Program Discovery sections drive the conversations that yield a “best fit” initial configuration of Atlassian products. They walk through key areas that help leaders accelerate their adoption of scaled agile practices.
Program Discovery is composed of nine Discovery Areas, each leveraging a set of Discovery Aids, which elicit the answers that drive the initial configuration. Discovery Aids explore different practice areas of the program and ask the team to make choices on where (and how much) to innovate from the current state. These choices point to specific How Tos, which drive the initial configuration of the solution.
Discovery Area | Purpose |
|---|---|
01: Purpose and Boundaries | Decide the purpose for the program. |
02: Program Leadership Team | Decide on a program leadership team. |
03: Program Scope Impact | Decide on the value stream elements, products, and/or assets that the program is accountable for. |
04: Value Delivery | Decide how value will be delivered. |
05: Team Visibility | Decide on the teams that will compose the program. |
06: Pursuing Changes | Decide on how your program will approach the change associated with transformation. |
07: Capacity | Decide on an expected velocity or capacity for the next quarter / program increment. |
08: Guardrails | Decide on guardrails for spending in the next quarter / program increment. |
09: Work Types | Decide how to characterize work to associate with the products, customers, affected countries, etc. |
Agile at scale path summary
Previous step:
Next step:
Program leadershipWas this content helpful?
Connect, share, or get additional help
Atlassian Community