96
Agile Past the Team An Experience Report Presented by: Mike Cottmeyer
| Date post: | 20-Aug-2015 |
| Category: |
Technology |
| Upload: | mike-cottmeyer |
| View: | 1,073 times |
| Download: | 1 times |
Agile Past the TeamAn Experience Report
Presented by: Mike Cottmeyer
mike cottmeyervice-president, pillar technology [email protected]+1.404.312.1471www.pillartechnology.comwww.leadingagile.comtwitter.com/mcottmeyer
Agenda
• A little project background
Agenda
• A little project background• What was going well
Agenda
• A little project background• What wasn’t going well
Agenda
• A little project background• What wasn’t going well• The team’s initial response to problems
Agenda
• A little project background• What wasn’t going well• The team’s initial response to problems • Team based coaching approach
Agenda
• A little project background• What wasn’t going well• The team’s initial response to problems • Organization based coaching approach
Agenda
• A little project background• What wasn’t going well• The team’s initial response to problems • Organization based coaching approach
Ready?
Background
• Waterfall since the company had formed
Background
• Waterfall since the company had formed• Evaluated Scrum
Background
• Waterfall since the company had formed• Evaluated Scrum and RUP
Background
• Waterfall since the company had formed• Evaluated Scrum and RUP• Chose Scrum because it was quicker to
implement
Background
• Waterfall since the company had formed• Evaluated Scrum and RUP• Chose Scrum because it was they though
quicker to implement
Background
• Waterfall since the company had formed• Evaluated Scrum and RUP• Chose Scrum because it was they thought
quicker to implement• Flipped the switch overnight
Background
• Waterfall since the company had formed• Evaluated Scrum and RUP• Chose Scrum because it was they thought
quicker to implement• Flipped the switch overnight during the
Christmas holidays
Going Well?
Going Well?
• Moved away from functional silos
Going Well?
• Moved toward cross functional teams
Going Well?
• Moved toward cross functional teams• Moved away from component teams
Going Well?
• Moved toward cross functional teams• Moved toward feature based teams
Going Well?
• Moved toward cross functional teams• Moved toward feature based teams• Product Manager for each team
Going Well?
• Moved toward cross functional teams• Moved toward feature based teams• Product Owner for each team
Going Well?
• Moved toward cross functional teams• Moved toward feature based teams• Product Owner for each team• Committed to following the Scrum process
Not Going Well?
Not Going Well?
• Critical people shared across teams
Not Going Well?
• Critical people shared across teams• Didn’t know what to build
Not Going Well?
• Critical people shared across teams• Didn’t know what to build• Teams had trouble delivering
Not Going Well?
• Critical people shared across teams• Didn’t know what to build• Teams had trouble delivering anything
Not Going Well?
• Critical people shared across teams• Didn’t know what to build• Teams had trouble delivering anything• Unstable and not predictable
Textbook Scrum
Textbook ScrumNo working software
My Role
My Role
• Purchased VersionOne
My Role
• Purchased VersionOne• Came in as a product trainer
My Role
• Purchased VersionOne• Came back as an agile coach
My Role
• Purchased VersionOne• Came back as an agile coach• The goal was to help the teams get better
My Role
• Purchased VersionOne• Came back as an agile coach• The goal was to help the teams get better• Learned quickly it was the organization that
needed help
Team Coaching
Team Coaching
• Big Rocks
Team Coaching
• Big Rocks• The Million Dollar Question
Team Coaching
• Big Rocks• The Million Dollar Question• Don’t game the numbers
Team Coaching
• Big Rocks• The Million Dollar Question• Don’t game the numbers• Retrospectives
Org Coaching
Org Coaching
• Scrum-But
Org Coaching
• Scrum-But• Product and Architectural Vision
Org Coaching
• Scrum-But• Product and Architectural Vision• Product Owner Teams
Org Coaching
• Scrum-But• Product and Architectural Vision• Product Owner Teams• Well groomed backlog
Million Dollar Question
Plan Execute Close
Plan CloseExecute
Plan Execute Close
Commit
Plan Execute Close
Commit
Deliver
Scrum-But
Developers
DevelopersTesters
Developers
Analyst
Testers
Developers
CSMAnalyst
Testers
Product Owner
CSMAnalyst
Testers
Developers
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Project (years)
Release (months) Release (months) Release (months)
I1 I2 I3 I4 I5 I6 I7 I8 I9
Product Owner Teams
Scrum of Scrums
Capability 2
Capability 1
Capability 3
Product Owner Team
Capability 2
Capability 1
Capability 3
Product Owner Team withArchitects
Capability 2
Capability 1
Capability 3
Integration Team
Capability 2
Capability 1
Capability 3
Capability 2
Capability 1
Capability 3
Context
Capability 2
Capability 1
Capability 3
ContextCoordination
Architecture and Design
TeamPO TeamPMO
Guidance
EnterpriseArchitecture
&Epics
SolutionsArchitecture
&Features
DetailedDesign
&Stories
TeamPO TeamPMO
Feedback
EnterpriseArchitecture
&Epics
SolutionsArchitecture
&Features
DetailedDesign
&Stories
I0I1-N
IH
Inc.Construction
Trans.
I0I1-N
IH
Elab.
Inc.Construction
Trans.
I0I1-N
IH
Elab.
Initiate Plan Execute Monitor & Control Close
Grooming the Backlog
Epic
Epic
Epic
Epic
EnterpriseArchitecture
&Epics
Feature
Feature
Feature
Feature
Feature
Feature
Epic
Epic
Epic
Epic
EnterpriseArchitecture
&Epics
SolutionsArchitecture
&Features
Feature
Feature
Feature
Feature
Feature
Feature
Epic
Epic
Epic
Epic
User Story
User Story
User Story
User Story
User Story
User Story
User Story
EnterpriseArchitecture
&Epics
SolutionsArchitecture
&Features
DetailedDesign
&Stories
Conclusion
Conclusion
• Forming and developing teams is critical
Conclusion
• Forming and developing teams is critical• The organization has tremendous impact on
team effectiveness
Conclusion
• Forming and developing teams is critical• The organization has tremendous impact on
team effectiveness• Managers need to understand their impact
Conclusion
• Forming and developing teams is critical• The organization has tremendous impact on
team effectiveness• Managers need to understand their impact• Have to consider the entire delivery system
Thoughts?
mike cottmeyervice-president, pillar technology [email protected]+1.404.312.1471www.pillartechnology.comwww.leadingagile.comtwitter.com/mcottmeyer
Agile Past the TeamAn Experience Report
Presented by: Mike Cottmeyer
www.slideshare.net/mcottmeyer
