what_do_we_need_to_think_about_when_we_go_from_a_pi_planning_approach_to_a_more_continuous_planning_approach
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
what_do_we_need_to_think_about_when_we_go_from_a_pi_planning_approach_to_a_more_continuous_planning_approach [2020/06/02 14:22] – external edit 127.0.0.1 | what_do_we_need_to_think_about_when_we_go_from_a_pi_planning_approach_to_a_more_continuous_planning_approach [2020/10/27 13:50] (current) – Reworked to improve discussion hans | ||
---|---|---|---|
Line 9: | Line 9: | ||
* No real dependencies between Teams. The PI Planning approach is really aimed at working dependencies that exist between Teams that are delivering to a common multi-team value stream. | * No real dependencies between Teams. The PI Planning approach is really aimed at working dependencies that exist between Teams that are delivering to a common multi-team value stream. | ||
- | Just because you have decided not to do a PI Planning event it does not mean that that’s it. You will need to help through what it means. The best way to think about this is to think about the purposes of the various | + | Just because you have decided not to do a PI Planning event it does not mean that that’s it. You will need to think through what it means. The best way to think about this is to think about the purposes of the various |
- | For example, the purpose of PI Planning is to get have multiple Teams get to alignment on the priorities for the next quarter (and keep roadmap up to date), work dependencies, | + | For example, the purpose of PI Planning is to get have multiple Teams get to alignment on the priorities for the next quarter (and keep roadmap up to date), work dependencies, |
- | Then, when we say “we don’t do PI Planning” then there are a number of execution | + | Then, when we say “we won't do PI Planning” then there are a number of execution |
- | * Scrum of scrums: purpose is to work execution issues across multiple Teams. What do we need to do to ensure we are addressing execution issues. | + | * Scrum of scrums: |
* PO Sync: is this just the refinement meeting? | * PO Sync: is this just the refinement meeting? | ||
* ART Sync: is it worthwhile to combine PO Sync / Scrum of Scrums? | * ART Sync: is it worthwhile to combine PO Sync / Scrum of Scrums? | ||
Line 22: | Line 22: | ||
Then we also need to make sure we are responding to our values: | Then we also need to make sure we are responding to our values: | ||
- | * We value innovation and learning: | + | * We value innovation and learning: |
- | * We value continuous / relentless improvement: | + | * We value continuous / relentless improvement: |
- | * We value working solutions (and finishing): | + | * We value working solutions (and finishing): |
- | By the way, this type of thinking applies to complete Kanban Teams as well. While Kanban doesn’t say “have a retrospective” if we value continuous improvement then we need to make this happen. One way to make this happen is to set up the ceremony | + | By the way, this type of thinking applies to complete Kanban Teams as well. While Kanban doesn’t say “have a Retrospective” if we value continuous improvement then we need to make this happen. One way to make this happen is to set up the event on the cadence. |
====== Want To Know More? ====== | ====== Want To Know More? ====== |
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_do_we_need_to_think_about_when_we_go_from_a_pi_planning_approach_to_a_more_continuous_planning_approach.1591132941.txt.gz · Last modified: 2020/06/02 14:22 by 127.0.0.1