Upload
sally-elatta
View
6.127
Download
0
Embed Size (px)
DESCRIPTION
This was a webinar I offered to discuss real world reasons behind Agile adoption failure and the success factors for avoiding them. You can watch the video of the webinar here:
Citation preview
Presenter: Sally Elatta
1
Top Reasons Agile Adoption Fails
and How to Avoid Them!
copyright © Sally Elatta 2010
About Sally
221
• Sally Elatta• Leading Agile Transformation Coach and Trainer
• Background: Java/.Net Software Architect
• Certified Scrum Practitioner & ScrumMaster
• Certified IBM, Sun, Microsoft Professional
• Taught over 1000+ and helped coach over 20+ teams
I am simply a transformer. Someone who is really passionate about transforming individuals, teams and organizations to doing what they do better. I value instilling soft skills and leadershipqualities in the people I coach. I believe in Servant Leadership as the way to lead change and create a culture of empowered teams, as opposed to Command and Control.
copyright © Sally Elatta 2010
The manifesto’s shared value statement:“We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
Individuals & interactions Over Processes & Tools
Working Software Over Comprehensive Documentation
Customer Collaboration Over Contract Negotiation
Responding to Change Over Following a Plan
“That is, while there is value in the items on the right, we value the items on the left more.”
3
copyright © Sally Elatta 2010
Project Management Principles
(Release Planning, Sprint and Iteration Planning, Daily Scrum,
Sprint Demo and Retrospective ..etc)
Engineering Principles(TDD, Continuous Integration,
Refactoring ..etc)
4
copyright © Sally Elatta 2010
Agile Characteristics Product Backlog
Test Driven Development Business / IT as One Team5
copyright © Sally Elatta 2010
Product Owner
thinks of New Idea
Product Backlog
Sprint Backlog
Features/Stories Small Stories
Each story is broken down into tasks. Each team member signs up for tasks and provides estimates of effort.
Tasks
Spri
nt
1Sp
rin
t 2
Spri
nt
3Sp
rin
t 4
Spri
nt
N
Each Iteration is 1 – 4 weeks in length. Multiple iterations make up a Release.
Work Breakdown Process
6
copyright © Sally Elatta 2010
Sample Backlog
7
copyright © Sally Elatta 2010
How to Avoid Agile Failure!
ProcessManagementProduct OwnerTeam
8
copyright © Sally Elatta 2010
Process Success Factors
Please .. Try a successful Agile recipe first before
customizing it!
Do understand the motivation behind a specific practice
before dropping it.
Do start with a Pilot, prove success, inspect and adapt,
then adopt at scale. (avoid too big, too fast)
Do have a thought out adoption rollout plan.
Avoid the ‘Checklist Agile’ adoption by also
transforming soft skills and leadership.
Avoid WAGILE!
9
copyright © Sally Elatta 2010
Process Success Factors ..
Develop new incentives that recognize team delivery
instead of individual delivery.
Do go through Release Planning and Iteration 0.
Do use expert coaches to help through initial phases.
Do pre-planning on iteration ahead of the other.
Do understand what is ‘Just Enough’ documentation.
Do factor in dependency and proof of concept stories
upfront during release planning.
Do breakdown stories to the right size.
10
copyright © Sally Elatta 2010
Process Success Factors ..
Develop new incentives that recognize team delivery
instead of individual delivery.
Do go through Release Planning and Iteration 0.
Do use expert coaches to help through initial phases.
Do pre-planning on iteration ahead of the other.
Do understand what is ‘Just Enough’ documentation.
Do factor in dependency and proof of concept stories
upfront during release planning.
Do breakdown stories to the right size.
Do solve the organizational impediments Agile
exposes.
11
copyright © Sally Elatta 2010
copyright © Sally Elatta 2010
Management Success Factors
Management ‘genuine’ buy-in to giving Agile a
chance.
Converting from ‘Command and Control’ to
‘Servant Leadership’.
Trust the team to self-manage, but provide
leadership.
Control resource shifting and multi-tasking.
Structure the teams so they can get a story
‘done’, reduce dependencies.
13
copyright © Sally Elatta 2010
Management Success Factors ..
Celebrate success, even small wins, and show
confidence.
Support the Agile practices yourself. Agile
requires discipline at all levels.
Support new ScrumMasters and watch against
reverting to form.
Avoid Agile Team burn-out!
Remove impediments quickly. Don’t be one
14
copyright © Sally Elatta 2010
Product Owner Success Factors
Educate the business side early (not just IT)
on Agile, get their buy-in.
Help the Product Owner develop a realistic
plan/schedule for team collaboration.
The right Product Owner should lead with a
strong vision and passion for success.
She/he should be Knowledgeable,
Empowered and Engaged with the team.
Manages and controls scope changes.
Not the ScrumMaster. 15
copyright © Sally Elatta 2010
Product Owner Success Factors ..
Manages stakeholder expectations and solicits
feedback. Invites them to demos/reviews.
Focus team on top priority stories.
Provides early and frequent testing feedback to
the team.
Encourages, supports and motivates the team to
continuously improve and deliver the right product.
Keeps an eye on the vision ahead.
Collaborates with the team to develop a release
plan that meets the vision.
16
copyright © Sally Elatta 2010
Team Success Factors
Team is trained and ‘genuinely’ interested in
giving the new processes a chance.
Team members represent cross-functional
roles that collaborate daily to get stories ‘Done’.
Team is empowered and engaged. They sign
up for tasks, provide realistic estimates, make
realistic iteration commitments.
Members create their team norms, define
‘Done’, have mutual accountability.
17
copyright © Sally Elatta 2010
Team Success Factors ..
Developers deliver small testable code every
day.
Team is co-located as much as possible.
Team measures progress in terms of story
points accepted by product owner.
Team tracks tasks and progress visibly.
Team members provide input to continuously
improve processes.
Team members care about quality and focus
on ways to reduce defects. 18
copyright © Sally Elatta 2010 19
copyright © Sally Elatta 2010
copyright © Sally Elatta 2010
How We Can Help
20
Real World Workshops
• Management and Business Overview of Agile/Lean
• Real World Agile and Scrum team training + Project Jump Start
• Effective Facilitation & Requirements Gathering
• Servant Leadership
• Agile Project Estimating and Planning
• Engineering Best Practices
• … More!
Real World Coaching
• Agile Project Jump Start Coaching
• Leadership Coaching
• Full Time ScrumMasters
• Troubled Project Assessment & Recovery
• Enterprise Transformation Roadmap Development and Execution
copyright © Sally Elatta 2010
Real World Agile and Scrum
•
21
copyright © Sally Elatta 2010
Evaluations for Real World Agile
22
copyright © Sally Elatta 2010
Servant Leadership
•
23
copyright © Sally Elatta 2010
Evaluations for Servant
Leadership
24
copyright © Sally Elatta 2010
Effective Facilitation
•
25
copyright © Sally Elatta 2010
Evaluations for Facilitation
26
copyright © Sally Elatta 2010
Requirements Gathering
•
27
copyright © Sally Elatta 2010
Contact Us
United States
402 212-3211
Web
www.AgileTransformation.com
www.AgileTraining.com
29