Big room planning is the secret sauce for effective agile planning and execution because it brings together all the people in an organization responsible for delivering software value to market from development and test to program management and the business to plan collaboratively.
Big room planning agenda.
I ve just completed my first ever big room planning meeting a type of exercise made famous by safe in their pi planning.
That was quite an excerises and i m totally worn out.
Big room planning is real time collaborative release planning where you identify risks early untangle dependencies and effectively scope your work so you can prioritize and deliver value faster.
All planning takes place in a single large room so everybody can discuss their teams needs and identify conflicts.
The output from the big room planning event are the following.
The main deliverable in a safe big room planning session is a program board which is essentially a sprint by sprint breakout of the work for all of the teams in the program increment.
It was quite noisy at times but after 8 hours we went home with our sights aligned and a much better feel for.
In this blog i will dive deep into the week leading up to big room planning and the event itself.
Pi planning has a standard agenda that includes a presentation of business context and vision followed by team planning breakouts where the teams create their iteration plans and objectives for the upcoming program increment pi.
A committed delivery plan from each lean agile team.
When you have multiple teams working on a project the big room planning technique comes in handy.
Planning is essential to agile but for larger projects it can become problematic.
But also immensely impressed by the team and the amount of learning that took place in the room today.
Remote teams are planning at the same time using video conferencing.
While both the agile manifesto and safe highlight the benefits of face to face planning often organizations will need to run these events across multiple locations.
The reasons for a distributed pi planning event can be varied it may be due to financial.
If you have multiple development teams collaborating on time sensitive projects join ca agile central services architect carolina weibring on.
Identification ownership of inter team dependencies.
Big room planning is two days of planning together with all program and team members every quarter.
It can depict dependencies and assumptions but it s basically the plan for the quarter five two week sprints or so.