Planning as a Team vs Planning as an Enterprise

Planning as a Team vs Planning as an Enterprise Silicon Valley Agile Leadership Network Meetup Kathryn Kuhn May 2016

But Does it Scale? How Do you Know?

One common goal Creating a shared purpose for Big Room Planning Transforming an enterprise requires full support and clarity of purpose across all levels. Consensus-driven planning creates buyin and commitment as it vets alternative implementation plans. What it takes Active participation in decision making and tradeoff conversations Surfacing risks and impediments during planning for immediate and visible action by leadership Listening to and are aligning with the overall mission and objectives, not just a to-do list of action items Actively and visibly voting on support of the overall plan

So How do You Do this?

Agenda Day 1 8:00am - 11:30am Break 11:30pm - 12:30pm 12:30pm - 4:00pm 2:00pm - 2:10pm 3:00pm - 3:10pm 4:00pm - 6:00pm 6:00pm - 7:00pm Long Term Borrow Winston W Product Management..John H Architectural and System Vision Bryan O Cadence Ecosystem Overview..Cathy P Accenture Mortgage Cadence Paul W Program Experiences..Trey F Team Instructions.John S. Teams create draft plans. Progress assessment. Progress assessment. Teams present draft plans. Problem solving 11 2016 CA. ALL RIGHTS RESERVED.

Working Agreements for Very Large Meetings How can we work together effectively in such a large room with so many people? Directionally Correct is ok Be Present Be Heard Electronics by Exception Respect Your Humanity Raise Risks Early No Surprises Shared/Transparent Note-Taking https://www.rallydev.com/community/agile/working-agreements-huge-meetings 12 2016 CA. ALL RIGHTS RESERVED.

Bring a Well-Structured Backlog Initiatives and Features, with capacity allocations and Feature Estimates Initiative 1 - Link to PI (Feature Points Allocated) Feature 1 (Feature Point Estimate) Feature 2 (Estimate)... Initiative 2 - Link to PI (Points) Feature 1 (Feature Point Estimate) Feature 2 (Estimate)... Initiative 3 - Link to PI (Points) Architecture - Link to PI (Points) CV -Link to PI (Points) 14 2016 CA. ALL RIGHTS RESERVED.

Have a Countdown-Based View - 9 weeks - 8 weeks - 7 weeks - 6 weeks - 5 weeks 3 Next Quarter High Level Pass 4 Initiatives broken down into Features to present to sizing team 5 Features Estimates Due - Roadmap Review with Leadership 6 The Why Kickoff with all of Engineering 7 Features to Teams. Feature Estimates Finalized - 3 weeks - 2 Weeks 9 Story Breakdowns Begin / UX Mockups for Stories 10 Week Of 11 Roadmap Plan 3rd Draft. User Story estimates with Iterations/Quarterly R&D Demo Hackathon Demo/Quarterly R&D Retrospective 12 Big Room Planning 16 2016 CA. ALL RIGHTS RESERVED.

Views to Bring into Big Room Planning Capacity Planning - High level Plan and team Readouts (Capacity / Work / Risks / Dependencies) Team Planning - Story level / Iteration level plan Release Tracking - Visualize the detailed plan with dependencies Release Tracking - In Quarter Status and Steering 19 2016 CA. ALL RIGHTS RESERVED.

So How Do I Convince the Leadership Team?

Ceremony that Connects Strategy with Execution How much does lack of alignment cost you each quarter? # of hours in Status Meetings Change in direction and throw away work While we re at it list Late decision making (only pull the quality lever) Treat Decisions in Progress like Work in Progress The Value of Buy-In # of decisions / cost of event 24 2016 CA. ALL RIGHTS RESERVED.

How Much Does Lack of Alignment cost You? 8 Teams (assuming 8 people per team) = 64 people x $100,000 annual salary =$6,400,000 annual run rate or $1,600,000 per quarter How much does it cost you to be unaligned by 5%? $80,000 each quarter SAI quotes run rates of $2.2 Million every 11 weeks or $11 Million per year 25 2016 CA. ALL RIGHTS RESERVED.

Common Pitfalls

Q&A

Kathryn Kuhn Director of Services kathrynkuhn@ca.com @Kathryn_e_kuhn https://www.linkedin.com/in/kathrynekuhn