1. The document discusses lessons for large scale lean and agile product management from a presentation at the Atlassian Summit 2012.
2. It provides a 10 point plan for transitioning to agile and emphasizes embracing change, focusing on people over process, and maintaining a sustainable pace of work.
3. The document also discusses techniques for improving backlogs through envisioning, estimating at a large scale, and coordinating feature and component teams.
18. Envisioning
Envisioning develops a clear product vision /roadmap to deliver the right
product to the right market using the right technology through consultation with
users and choosers.
10% of overall effort Prototypes
& Models
Market & Product Requirements
Technology AnalysisBrainstorming Backlog
Evaluations & Visioning Deliverables
Prototyping
Competitive Delta Risk
Analysis Acceptance
Criteria Backlog
Customer Field
QFD Studies & Interviews
House of Quality GUI
Guidelines
Practices Deliverables
Brainstorming & visioning Competitive Requirements backlog Risk
analysis (SWOT) Delta analysis QFD backlog Analysis & Verification
Customer studies Hardware, platform & Reports Prototypes/Models
component evals Prototyping/modeling
Look-and-Feel Guidelines
19. AIL Portfolio (Backlogs)
Program Feature Team Company Backlog
P1 F1 Blue
Program Backlogs
F2 Blue
F3 Red Team Backlogs
F4 Red
F5 Red
F6 Red Program Medical Imaging
P2 F7 Yellow
F8 Green Feature MRI Mechanical Control
F9 Green
F10 Purple Epic Table Movement
F11 Purple
P3 F12 White Story Horizontal Movement
F13 White
F14 White Task Position w/ Joy Sticks
F15 White
Component F16 Orange
F17 Orange
F18 Orange
20. Estimates – Do Them Fast and Often
Collectively Owned By Team
2 or 3 point estimates to include
uncertainty 3 point
All items in backlog 2 point
AIL uses Ideal Days 1 Point
Planning Poker (wide band
delphi)
Low, Relati Ideal
Medium,
ve Days
High Point
s
21. Program and Feature Estimation Planning
Feature and Program Estimation Dev Estimation, Negotiation, and Commitment
Feature Team Features are The scrum team refines Based on discussion,
builds backlog allocated to the features into work work items may be
containing list a specific items called stories, moved from one sprint
of feature with release. A divides the stories into to another sprint,
a first release is a 3-6 sprints, and prepares a moved from one team
estimate. sprint time second estimate. The to another, deferred to
box. estimates are compared another release.
and consensus is
reached thru discussion.
Product Scrum 1
Product Sprint 1
Release Release
Backlog Backlog
Backlog Backlog
Product Scrum 2 Sprint 2
Release
Backlog
Scrum 3 Sprint 3
22. Activity Based Estimates – Managing Risk for Large
Projects
Activity Examples Worst Best Expected Likely
Java Code (classes, methods)
Interface
Pricing Table (table size)
Process (steps)
Product/Data Definition (Tables/Fields)
Rules (Decision Table (conditions/rules)
Forms (screens, widgets)
Printed Forms (page types, widgets)
Story
Estimate Risk
Window
Activity Estimate
23. Feature and Component Teams Coordination
.
Feature Epic
Component Component Component
A B C
Component Epics
Component 1 Component 2 Component 3
Feature A Priority 1 Feature A Work Feature A&B Work Feature A Work
Feature B Priority 2 Feature B Work
Feature C Priority 3 Feature C Work Feature C Work
reduced gap external expertscustomer exposure brings tangible requirementsexecutive exposure brings business tangibilityshort delivery always increases trust put it on the walk – transparency increases trustwhole teams increase trust and break silostimely decision increase trust