Guides

PI Planning Draft Plan

Issue link: https://read.uberflip.com/i/1255121

Contents of this Issue

Navigation

Page 0 of 0

Decompose features into user stories and assign story size estimates in the team backlog. Teams can use Estimably, available in VersionOne TeamRooms, to run quick estimation games so they can collaboratively evaluate their backlog. As teams reach decisions, the story size is automatically updated. Allocate user stories to iterations considering team capacity and velocity. The VersionOne Velocity Trend report shows a team's hostorical velocity over a set period of time. Sprint Member Capacity Planning allows members and teams to capture detailed hourly capacity targets so they can define the workload on a sprint-by-sprint basis. Any remaining stories in the PI backlog not planned into iterations due to team capacities being reached are brought to the PI Plan review sessions for re-assessment. Map dependensies across sprint with other teams on the ART and visualize the impact using the Program Board. It provides clarity into where user story sequencing may add risk to the plan. These issues are seen with arrows flowing from right to left. Teams use the program board to start collaborating with other teams to resolve dependency issues themselves, risk can be formalized as issues in the VersionOne to be addressed either during the scrum-of-scrums session or during the management problem solving session. Document key objectives for the upcoming PI and align all work to these objectives. Team PI objectives will ultimately inform PI objectives for the whole ART. Team and ART PI objectives can be viewed in the PI Planning view or the Objectives grid view. Use VersionOne conversations within Team Planning Rooms to communicate in-context with others by tagging specific participants and/ or work items. This visibility also helps the team with decision making during the planning event. Conversations can also be leveraged in the AFT PI Planning room to communicate during the business context session and plan review meetings after team breakouts. Source: www.scaledagileframework.com Planning Context and Lunch: The Release Train Engineer (RTE) explains how the PI Planning process will work, key deliverables, and expected outcomes for the meeting. Team Breakout: During this time, teams will create a draft plan in VersionOne Team Planning Rooms. Apply filters to the Portfolio Tree, Team PI Planning, and other areas to show assigned features for your specific team. • Decompose features into user stories and assign story size estimates in the team backlog. Teams can use Estimably, available in VersionOne TeamRooms, to run quick estimation games so they can collaboratively evaluate their backlog. As teams reach decisions, the story size is automatically updated. • Allocate user stories to iterations considering team capacity and velocity. The VersionOne Velocity Trend report shows a team's historical velocity over a set period of time. Sprint Member Capacity Planning allows members and teams to capture detailed hourly capacity targets so they can define the workload on a sprint-by-sprint basis. PI Planning Inputs Business Context Roadmap and Vision Top Ten Features Source: www.scaledagileframework.com Planning Context and Lunch: The Release Train Engineer (RTE) explains how the PI Planning process will work, key deliverables, and expected outcomes for the meeting. Team Breakout: During this time, teams will create a draft plan in VersionOne Team Planning Rooms. Apply filters to the Portfolio Tree, Team PI Planning, and other areas to show assigned features for your specific team. • Decompose features into user stories and assign story size estimates in the team backlog. Teams can use Estimably, available in VersionOne TeamRooms, to run quick estimation games so they can collaboratively evaluate their backlog. As teams reach decisions, the story size is automatically updated. • Allocate user stories to iterations considering team capacity and velocity. The VersionOne Velocity Trend report shows a team's historical velocity over a set period of time. Sprint Member Capacity Planning allows members and teams to capture detailed hourly capacity targets so they can define the workload on a sprint-by-sprint basis. PI Planning Inputs Business Context Roadmap and Vision Top Ten Features Source: www.scaledagileframework.com • Map dependencies across sprints with other teams on the ART and visualize the impact using the Program Board. It provides clarity into where user story sequencing may add risk to the plan. These issues are seen with arrows flowing from right to left. Teams use the program board to start collaborating with other teams to resolve dependencies and identify risks. Where teams are unable to resolve the dependency issues themselves, risks can be formalized as issues in VersionOne to be addressed either during the scrum-of-scrums session or during the management problem solving session. • Teams can document their key objectives for the upcoming PI and align all work to these objectives. Team PI objectives will ultimately inform PI objectives for the whole ART. • Use VersionOne conversations within Team Planning Rooms to communicate in-context with others by tagging specific participants and/or work items. This visibility also helps the team with decision making during the planning event. Source: www.scaledagileframework.com • Map dependencies across sprints with other teams on the ART and visualize the impact using the Board. It provides clarity into where user story sequencing may add risk to the plan. These issues with arrows flowing from right to left. Teams use the program board to start collaborating with teams to resolve dependencies and identify risks. Where teams are unable to resolve the dependency issues themselves, risks can be formalized as issues in VersionOne to be addressed either during scrum-of-scrums session or during the management problem solving session. • Teams can document their key objectives for the upcoming PI and align all work to these objectives. PI objectives will ultimately inform PI objectives for the whole ART. • Use VersionOne conversations within Team Planning Rooms to communicate in-context with others tagging specific participants and/or work items. This visibility also helps the team with decision during the planning event. Part III: Day Two of PI Planning Team Breakouts: if you have teams across time zones, they can use this time on the second day of PI Planning work on user stories and dependencies. Draft Plan View: This is a time-boxed meeting where teams present their draft plans to business owners, product management, and other teams in the ART to get feedback. Remote PI Planning Create a Draft Plan in VersionOne © 2020 Digital.ai

Articles in this issue

Links on this page

view archives of Guides - PI Planning Draft Plan