9:00 am
Kanban and large-scale
strategic planning
Eric Brechner
Dev Manager, Xbox
9:05 am
Outline
•
•
•
•
•
•
•
•
•
•
•
What is large-scale strategic planning?
Why not use only Kanban?
Our product
Ideation: market analysis, technology themes, and business model
McGrath and MacMillan Options Portfolio
Customer segmentation and scenarios with KPIs and prioritization
Mock press release
System architecture
Backlog generation, estimation, and prioritization
Overall release schedule
Backlog ordering
9:10 am
What is large-scale strategic planning?
Organization
Division
Division
Division
Division
Division
Division
Division
Division
Division
Group
Division
Division
Division
Group
Group
Division
Group
Group
Division
Group Team
Team
Team
Group
Division
Team
Team
Team
Team
Division
Team
Group
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
9:12 am
Feature
Release
Product
Why not use only Kanban?
Vision
Document
Engineering
System
Establish
milestone
dates and
goals
Estimate and
prioritize
features
Report status
and remove
blockages
Mitigate risks
and
dependencies
Milestone
Schedule
Conduct
milestone
reviews
Align
schedules &
communicate
status
Align features
to milestones
Complete
work
Feature
Schedule
Review tasks
and assign
resources
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
9:14 am
Our product
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
9:15 am
Ideation:
• Market analysis
• Competitors, table stakes, differentiation, and opportunities
• Technology themes
• Emerging technologies, breakthrough innovations, and game changers
• Business models
• Pricing, COGS, subscriptions, advertising, and partnerships
THE GOAL: An overview and potential features on sticky notes
Finish by 9:40 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
9:40 am
McGrath and MacMillan Options Portfolio
THE GOAL: Place features (yours or others) in portfolio and balance
Finish by 10:00 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
10:00 am
Customer scenarios with KPIs
• Customer segmentation
• SPICIER scenarios
• KPIs: measure of delight
• Prioritization
THE GOAL: A customer segment, SPICIER scenario, and three KPIs
Finish by 10:30 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
10:30 am
Mock press release
• Headline and subhead
• Location, date, and lead
• Key issue or barrier resolved for target audience
• High-level messaging around top scenarios, highlighting
differentiation
THE GOAL: Mock press release
Finish by 11:00 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
11:00 am
System architecture
Catalog and
Purchasing Services
Personalization and
Social Services
Apps
DVR/Guide
Natural User Interface
Operating system and drivers
Hardware and accessories
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
11:10 am
Backlog population
• Generate (brainstorm) high-level work items for your area
• Based on mock press release scenarios
• Estimate size of each item
• T-shirt sizing: S (days), M (weeks), L (months), XL (6+ months)
• Prioritize items
• Separate must-have from should-have and like-to-have
THE GOAL: Prioritized and estimated set of items on sticky notes
Finish by 11:40 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
11:40 am
Overall release schedule
• Three 3-month milestones
• Milestone 1: must-haves
• Milestone 2: remaining must-haves plus should-haves (preview ships)
• Milestone 3: remaining items that fit (product ships)
• Order your items (sticky notes) in corresponding milestones
• Check timing of your dependencies
• Sign-up for 10-minute speed dating
• Work out issues and reorder items
Repeat until 12:20
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
Backlog ordering
• Collect your items in their new order
• Add them to your Kanban board backlog
• Build it and ship it!
12:20 am
•
What is large-scale s
•
Why not use only Ka
•
Our product
•
Ideation: market ana
•
McGrath and MacMi
•
Customer segmentat
•
Mock press release
•
System architecture
•
Backlog generation,
•
Overall release sched
•
Backlog ordering
12:25 am
Wrap-up
• Different scale  different planning
• Balanced portfolio
• SPICIER scenarios
• Start at the end
• Estimate, prioritize, align, order
Please submit your evaluations—
Thank you!
For more details read:
Agile Project Management with Kanban