SlideShare ist ein Scribd-Unternehmen logo
1 von 157
Downloaden Sie, um offline zu lesen
 
Executive Panel Bill Holst,  President & Principal Consulting Software Engineer at Prescient Software Engineering and  Systems Analyst at Colorado Springs Utilities Adam Woods,  Director of Product Development at StoneRiver, Inc.
A Project Methodology Comparison  Waterfall vs. Agile at  Colorado Springs Utilities   Presented by Bill Holst  President and Principal Software Engineer  Prescient Software Engineering, Inc.
Background to Comparison ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Why change horses in the middle of a stream?  (because you can!) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Phase II – The Agile Adventure ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
The Results ,[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
We hit the wall! (c) Prescient Software Engineering, All Rights Reserved
The Results – the Wall! ,[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Project Velocity – this is not your textbook chart! ,[object Object],(c) Prescient Software Engineering, All Rights Reserved
Reforming the Project ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Where We Stand Today ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Conclusions – What’s Next ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],(c) Prescient Software Engineering, All Rights Reserved
Summary   ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
 
StoneRiver Agile Adoption Adam Woods Director of Product Development
Main Challenges Before Agile Adoption ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Early Challenges / Experiences ,[object Object],[object Object],[object Object],[object Object],[object Object]
Middle Maturity Challenges / Experiences ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Advanced Maturity Challenges / Experiences ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]
Some Specific Suggestions ,[object Object],[object Object],[object Object],[object Object]
Summary of Experience ,[object Object],[object Object],[object Object]
Want More Information ,[object Object],[object Object],[object Object],[object Object]
 
Jean Tabaka Certified Scrum Trainer and Agile Fellow 12 Agile Adoption Success Modes
12 Agile Adoption Success Patterns Jean Tabaka, Rally Software www.rallydev.com
 
 
 
 
Agile is not the problem
 
Success
Prepare to change WORLD your
your group
your organization
your company
your customers
Don’t abandon Agile
Knowledge-creating company Expansion not Scarcity Customer Value
3 categories of patterns
“ Getting started” patterns
“ In it”  patterns
“ Sustainability”  patterns
Each pattern has practices
“ Getting started” patterns
A clear and compelling goal #1   http://www.flickr.com/photos/inkybob/122476158
http://www.flickr.com/photos/inkybob/122476158 Be clear about the “Why Agile?”
 
http://www.flickr.com/photos/inkybob/122476158 Crisis or culture of improvement
[object Object],[object Object],[object Object],[object Object]
http://www.flickr.com/photos/inkybob/122476158 Scarcity vs. Expansion
Vision A high level Agile plan has VISION
Engaged executive sponsorship #2
Fully committed to success
Israel Gat – Cutter Consortium Israel Gat – “I want us all to succeed. I will do everything I can for you. Please help me help you.”
Social contract with organization
What’s in it for me? (WIIFM)
“ We will learn and all of us will have better skills as software professionals.”
Planning framework for rollout #3
Create a rollout plan
How will we know if we are successful? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Goal Metric How Reported
Example of Agile Rollout for 500
Use 5 levels of planning
Vision Roadmap Release Iteration Daily High level plan to a daily plan
Rank organizational backlog
Backlog Planned In Progress Complete Rollout Coach helps hire internal coach ARP with leadership to plan next waves Add Rally-developed apps IATs for new teams Release Planning after 3d iteration On-site CSM On-site CSPO T&E consulting
Engage your plan with guidance #4
Find bright spots
 
Bring in experienced mentors
Books are not enough. We need to find others and work with them.
Train everyone in their roles
The team knows what to do
AGILE ORGANIZATION Quarterly Business Cycle (Cross Organizations) Product Cycles (Cross Departments) Team Cycles
Start pilot teams based on rollout plan
Learn and mature  before you scale
“ In it”  patterns
Create strong leadership context #5
Servant leadership
 
Not command and control
 
Support collaboration
Form support councils not status reporting
Coordinate and support teams Multi-Team Program Team-of-Teams  Program Steering Portfolio Mgt & Governance Architecture Council Release Mgt
Create the right team context #6
Team ownership
 
Team commitment
Team success and growth not heroes
 
Embrace Agile team habits #7
Adopt Agile ceremonies
[object Object],[object Object],[object Object],[object Object],[object Object],Incremental Delivery of Customer Value Product Backlog Release Backlog Iterations 1-4 Weeks Daily Meetings Product Increment Releases 1-4 Months
Build feature by feature
GUI Business Logic Database SLICES VERTICAL Story 1 Story 2
Use fast feedback loops
Continuous, fast feedback through the Agile ceremonies Inform next iteration through feedback from this iteration Iterations 1-4 Weeks Daily Meetings Releases 1-4 Months
Vision Roadmap Release Iteration Daily Inform the Vision from the daily plan
Pull testing forward
STORY ONE Task Estimate Owner Code the UI 6 Brenda Code the middle tier 8 Yi Create and automate tests 4 Alan
Invest in a robust infrastructure
 
Ensure code is always releasable
 
Measure the right things #8
Definition of Done
Sample Definition  of Done
Readiness of the product backlog
Readiness of the product increments
“ Watch the  work product not the worker” -- Don Reinertsen
Flow of value
FLOW of VALUE Customer’s Pull Value Agile
Create a culture of continuous learning #9
Retrospect with teams regularly
 
Retrospect the organization regularly
 
Create knowledge flow up and down
Create knowledge across the organization
 
 
“ Sustainability”  patterns
Prepare to scale #10
Architect for change
 
Support organizational growth
 
 
Employ passionate change agents
 
Be patient and repeat patterns #11
It takes time!
AGILE Alignment Corporate Level Departmental Level Team Level Personal Level
Revisit your compelling goal
[object Object],[object Object],[object Object]
Revisit the strength of your sponsorship
Israel Gat – Cutter Consortium Israel Gat – “I want us all to succeed. I will do everything I can for you. Please help me help you.”
Continually improve your organizational backlog
Backlog Planned In Progress Complete Rollout Coach helps hire internal coach ARP with leadership to plan next waves Add Rally-developed apps IATs for new teams Release Planning after 3d iteration On-site CSM On-site CSPO T&E consulting
Apply these patterns to your context! #12
Prepare to inspect and adapt!
Wrap up our story
Agile is not the problem
 
Success
 
Start where you are
A clear and compelling goal #1   http://www.flickr.com/photos/inkybob/122476158
Apply these patterns to your context! #12
Knowledge-creating company Expansion not Scarcity Customer Value
A story of Agile success
 
Prepare to change WORLD your
12 Success Patterns for Agile Adoption Jean Tabaka, Rally Software www.rallydev.com
 

Weitere ähnliche Inhalte

Was ist angesagt?

Introducing Agile Scrum XP and Kanban
Introducing Agile Scrum XP and KanbanIntroducing Agile Scrum XP and Kanban
Introducing Agile Scrum XP and KanbanDimitri Ponomareff
 
Agile Resourcing
Agile ResourcingAgile Resourcing
Agile ResourcingCprime
 
Agile Methodologies and Scrum
Agile Methodologies and ScrumAgile Methodologies and Scrum
Agile Methodologies and ScrumScrum Turkey
 
DevOps Approach (Point of View by Ravi Tadwalkar)
DevOps Approach (Point of View by Ravi Tadwalkar)DevOps Approach (Point of View by Ravi Tadwalkar)
DevOps Approach (Point of View by Ravi Tadwalkar)Ravi Tadwalkar
 
Agile101 - What Agile Is and What Agile Is Not
Agile101 - What Agile Is and What Agile Is NotAgile101 - What Agile Is and What Agile Is Not
Agile101 - What Agile Is and What Agile Is NotDerek Huether
 
Deloitte lean agile state of the nation
Deloitte lean   agile state of the nationDeloitte lean   agile state of the nation
Deloitte lean agile state of the nationAlexis Hui
 
High Quality Software Development with Agile and Scrum
High Quality Software Development with Agile and ScrumHigh Quality Software Development with Agile and Scrum
High Quality Software Development with Agile and ScrumLemi Orhan Ergin
 
Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development OverviewStewart Rogers
 
Succeeding with Agile
Succeeding with AgileSucceeding with Agile
Succeeding with AgileMike Cohn
 
Agile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation SlidesAgile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation SlidesSlideTeam
 
Exec Leadership workshop
Exec Leadership workshopExec Leadership workshop
Exec Leadership workshopRavi Tadwalkar
 
A Gentle Introduction To Agile
A Gentle Introduction To AgileA Gentle Introduction To Agile
A Gentle Introduction To AgileMichael Sahota
 
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...WiMLDSMontreal
 
Scaling Agile and Scrum (cPrime/Angela Johnson)
Scaling Agile and Scrum (cPrime/Angela Johnson)Scaling Agile and Scrum (cPrime/Angela Johnson)
Scaling Agile and Scrum (cPrime/Angela Johnson)Cprime
 
Assessing Your Agility: Introducing the Comparative Agility Assessment
Assessing Your Agility: Introducing the Comparative Agility AssessmentAssessing Your Agility: Introducing the Comparative Agility Assessment
Assessing Your Agility: Introducing the Comparative Agility AssessmentMike Cohn
 
Business Value of Agile Testing: Using TDD, CI, CD, & DevOps
Business Value of Agile Testing: Using TDD, CI, CD, & DevOpsBusiness Value of Agile Testing: Using TDD, CI, CD, & DevOps
Business Value of Agile Testing: Using TDD, CI, CD, & DevOpsDavid Rico
 
Agile lean workshop for managers & exec leadership
Agile lean workshop for managers & exec leadershipAgile lean workshop for managers & exec leadership
Agile lean workshop for managers & exec leadershipRavi Tadwalkar
 
Kin2020- flow based product development- an experience report
Kin2020-  flow based product development- an experience reportKin2020-  flow based product development- an experience report
Kin2020- flow based product development- an experience reportRavi Tadwalkar
 
Meetup#2 SAFe Patrick & Maxence
Meetup#2 SAFe Patrick & MaxenceMeetup#2 SAFe Patrick & Maxence
Meetup#2 SAFe Patrick & MaxenceAlexandre Boutin
 

Was ist angesagt? (20)

Introducing Agile Scrum XP and Kanban
Introducing Agile Scrum XP and KanbanIntroducing Agile Scrum XP and Kanban
Introducing Agile Scrum XP and Kanban
 
Agile Resourcing
Agile ResourcingAgile Resourcing
Agile Resourcing
 
Agile Methodologies and Scrum
Agile Methodologies and ScrumAgile Methodologies and Scrum
Agile Methodologies and Scrum
 
DevOps Approach (Point of View by Ravi Tadwalkar)
DevOps Approach (Point of View by Ravi Tadwalkar)DevOps Approach (Point of View by Ravi Tadwalkar)
DevOps Approach (Point of View by Ravi Tadwalkar)
 
Agile101 - What Agile Is and What Agile Is Not
Agile101 - What Agile Is and What Agile Is NotAgile101 - What Agile Is and What Agile Is Not
Agile101 - What Agile Is and What Agile Is Not
 
Deloitte lean agile state of the nation
Deloitte lean   agile state of the nationDeloitte lean   agile state of the nation
Deloitte lean agile state of the nation
 
High Quality Software Development with Agile and Scrum
High Quality Software Development with Agile and ScrumHigh Quality Software Development with Agile and Scrum
High Quality Software Development with Agile and Scrum
 
Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development Overview
 
Succeeding with Agile
Succeeding with AgileSucceeding with Agile
Succeeding with Agile
 
Agile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation SlidesAgile Delivery Powerpoint Presentation Slides
Agile Delivery Powerpoint Presentation Slides
 
Exec Leadership workshop
Exec Leadership workshopExec Leadership workshop
Exec Leadership workshop
 
A Gentle Introduction To Agile
A Gentle Introduction To AgileA Gentle Introduction To Agile
A Gentle Introduction To Agile
 
Journey of Agile
Journey of AgileJourney of Agile
Journey of Agile
 
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...
The Agile methodology - Delivering new ways of working, by Sandra Frechette, ...
 
Scaling Agile and Scrum (cPrime/Angela Johnson)
Scaling Agile and Scrum (cPrime/Angela Johnson)Scaling Agile and Scrum (cPrime/Angela Johnson)
Scaling Agile and Scrum (cPrime/Angela Johnson)
 
Assessing Your Agility: Introducing the Comparative Agility Assessment
Assessing Your Agility: Introducing the Comparative Agility AssessmentAssessing Your Agility: Introducing the Comparative Agility Assessment
Assessing Your Agility: Introducing the Comparative Agility Assessment
 
Business Value of Agile Testing: Using TDD, CI, CD, & DevOps
Business Value of Agile Testing: Using TDD, CI, CD, & DevOpsBusiness Value of Agile Testing: Using TDD, CI, CD, & DevOps
Business Value of Agile Testing: Using TDD, CI, CD, & DevOps
 
Agile lean workshop for managers & exec leadership
Agile lean workshop for managers & exec leadershipAgile lean workshop for managers & exec leadership
Agile lean workshop for managers & exec leadership
 
Kin2020- flow based product development- an experience report
Kin2020-  flow based product development- an experience reportKin2020-  flow based product development- an experience report
Kin2020- flow based product development- an experience report
 
Meetup#2 SAFe Patrick & Maxence
Meetup#2 SAFe Patrick & MaxenceMeetup#2 SAFe Patrick & Maxence
Meetup#2 SAFe Patrick & Maxence
 

Ähnlich wie Agile Cafe Boulder - Panelist and keynote slides

Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...Agile Montréal
 
Best Practices When Moving To Agile Project Management
Best Practices When Moving To Agile Project ManagementBest Practices When Moving To Agile Project Management
Best Practices When Moving To Agile Project ManagementRobert McGeachy
 
From Agile Teams to Agile organizations
From Agile Teams to Agile organizationsFrom Agile Teams to Agile organizations
From Agile Teams to Agile organizationsSteve Mercier
 
Agile Pmi 102108 Final
Agile Pmi 102108 FinalAgile Pmi 102108 Final
Agile Pmi 102108 Finalbmcglin
 
Agile Comes to You (Mironov, Bellevue)
Agile Comes to You (Mironov, Bellevue)Agile Comes to You (Mironov, Bellevue)
Agile Comes to You (Mironov, Bellevue)Enthiosys Inc
 
The Agile Readiness Assessment Tool Essay
The Agile Readiness Assessment Tool EssayThe Agile Readiness Assessment Tool Essay
The Agile Readiness Assessment Tool EssayHeidi Owens
 
Why Agile? Why Now? IPMA Forum 2009
Why Agile? Why Now?   IPMA Forum 2009Why Agile? Why Now?   IPMA Forum 2009
Why Agile? Why Now? IPMA Forum 2009skipangel
 
Agile Methods: Fact or Fiction
Agile Methods: Fact or FictionAgile Methods: Fact or Fiction
Agile Methods: Fact or FictionMatt Ganis
 
Robert Mc Geachy Common Pitfalls Agile
Robert Mc Geachy Common Pitfalls AgileRobert Mc Geachy Common Pitfalls Agile
Robert Mc Geachy Common Pitfalls AgileRobert McGeachy
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overviewguestb4c770
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development OverviewMark Kovacevich
 
The Agile Methods Comparison by the Agile PrepCast
The Agile Methods Comparison by the Agile PrepCastThe Agile Methods Comparison by the Agile PrepCast
The Agile Methods Comparison by the Agile PrepCastOSP International LLC
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process IntroductionNguyen Hai
 

Ähnlich wie Agile Cafe Boulder - Panelist and keynote slides (20)

Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
Agile Project Management: From Agile Teams to Agile Organizations - Steve Mer...
 
Best Practices When Moving To Agile Project Management
Best Practices When Moving To Agile Project ManagementBest Practices When Moving To Agile Project Management
Best Practices When Moving To Agile Project Management
 
From Agile Teams to Agile organizations
From Agile Teams to Agile organizationsFrom Agile Teams to Agile organizations
From Agile Teams to Agile organizations
 
Agile Methodologies - Project Management with SCRUM
Agile Methodologies - Project Management with SCRUMAgile Methodologies - Project Management with SCRUM
Agile Methodologies - Project Management with SCRUM
 
Agile Pmi 102108 Final
Agile Pmi 102108 FinalAgile Pmi 102108 Final
Agile Pmi 102108 Final
 
Agile Comes to You (Mironov, Bellevue)
Agile Comes to You (Mironov, Bellevue)Agile Comes to You (Mironov, Bellevue)
Agile Comes to You (Mironov, Bellevue)
 
The Agile Readiness Assessment Tool Essay
The Agile Readiness Assessment Tool EssayThe Agile Readiness Assessment Tool Essay
The Agile Readiness Assessment Tool Essay
 
Why Agile? Why Now? IPMA Forum 2009
Why Agile? Why Now?   IPMA Forum 2009Why Agile? Why Now?   IPMA Forum 2009
Why Agile? Why Now? IPMA Forum 2009
 
Agile webinar pack (2)
Agile webinar pack (2)Agile webinar pack (2)
Agile webinar pack (2)
 
Agile Methods: Fact or Fiction
Agile Methods: Fact or FictionAgile Methods: Fact or Fiction
Agile Methods: Fact or Fiction
 
Agile at scale
Agile at scaleAgile at scale
Agile at scale
 
Robert Mc Geachy Common Pitfalls Agile
Robert Mc Geachy Common Pitfalls AgileRobert Mc Geachy Common Pitfalls Agile
Robert Mc Geachy Common Pitfalls Agile
 
Outsourcing With Agile
Outsourcing With AgileOutsourcing With Agile
Outsourcing With Agile
 
Agile Testing
Agile Testing Agile Testing
Agile Testing
 
The Agile Pretender
The Agile PretenderThe Agile Pretender
The Agile Pretender
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overview
 
Agile Development Overview
Agile Development OverviewAgile Development Overview
Agile Development Overview
 
The Agile Methods Comparison by the Agile PrepCast
The Agile Methods Comparison by the Agile PrepCastThe Agile Methods Comparison by the Agile PrepCast
The Agile Methods Comparison by the Agile PrepCast
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process Introduction
 
Psp Tsp Agile 3 1 En
Psp Tsp Agile 3 1 EnPsp Tsp Agile 3 1 En
Psp Tsp Agile 3 1 En
 

Agile Cafe Boulder - Panelist and keynote slides

Hinweis der Redaktion

  1. Two major phases to Colorado Springs Utilities (CSU) Energy Distribution Design presented opportunity for a back to back comparison of waterfall and Agile First phase was electric distribution design using traditional waterfall and fixed price contract with Autodesk Consulting Second phase was gas distribution design with Agile approach and time and materials – CSU assumed the project risk Phases were nearly equal in scope and technology Both phases used a two weeks requirements gathering session to define the logic for the capture of material on the design and the actual ordering in the work management system.
  2. Phase I – project was successful but we saw long lag times between requirements gathering and acceptance testing, resulting in a lot of rework Test cases written prior to code development, but were often wrong – lots of rework; our field engineers wrote all the test cases Code matched our logic from requirements but sometimes logic was incorrect – more rework Lots of churn in the project – some portions of the solution are uneven from a user perspective but workable (the spec was met) Had a disparate tool set – Excel and Word for requirements, Enterprise Architect for requirements and test cases, Mantis for defects Bob Buchan, CSU Project Manger, Tim Benedict, FE Manager, Jason Kagel, Spatial Network Solutions (main development group for Autodesk) and I met to discuss a better, more efficient approach for the second phase. We wanted a more robust solution that relied less on Autodesk Consulting for system changes.
  3. Met with Autodesk Consulting and restructured contract to be T&M Hand picked the project team with 3 half-time field engineers, 2 full time developers from SNS, a ½ QA person from SNS, one system analyst and architect from CSU, scrum master – Jason from SNS, and a product owner from CSU Hired an Agile coach from Rally, Christopher Avery, to come in and “ground” the team at the beginning of the project; [I was a skeptic, no use cases! How can this possibly work?] Christopher returned at the end of first iteration to help us through the initial “we suck” blues Established a lot of special collaboration tools to deal with distributed team (St. Louis, San Francisco, 3 locations in Colorado Springs) Rally software Nefsis Conferencing and HD video cameras Livemeeting and Webex Two conference call lines Google Docs for all project documentation Special storage closet for our “stuff”
  4. We had delivered our first release for review – it was very successful but… Logic was confusing, engineers were writing test cases for what they thought the results should be, and the code didn’t necessarily match either We stopped half-way through the 7 th iteration and decided to regroup; Team was discouraged
  5. Spent one iteration with only the field engineers, analyst, and product owner to completely rewrite logic to take advantage of Compatible Unit structures available in our Maximo work management system Logic dropped by a factor of almost 4 in complexity Next iteration, all code was rewritten and all test cases re-crafted We were on a roll! Being Agile made this possible In another iteration, we learned from on of the Maximo consultants that it wasn’t necessary to have separate logic for labor and non-labor jobs We did it again – code rewrite, threw ½ our test cases away! The team had transformed itself into Agile evangelists!
  6. First production release scheduled for week of February 7 th; this is approximately a month and a half early Costs are about 30% under budget Over 500 defects less than the electric phase A lot less code was written due to the redesign of the logic. Solution is now data driven, so changes can be made without any code changes Test case coverage is more thorough as the electric effort; test cases are higher quality Without the mid-course correction we would have been in a “change-order Hell’ cycle” now – probably without any idea of when the software could be installed; we could have risked a “shelf-ware” situation Process improvement on the material ordering side is immense – there are lots of pieces and parts to a gas design which makes the estimation and material ordering very time consuming and problematic Users love the software – even I can design a gas network!
  7. Gas design software has an amazing usability factor – it works the way it should from the user perspective (this is one of the ‘ilities’ that is hard to measure but you know when you have it!) Project has a lot of visibility within CSU – huge interest in Agile Rally has provided scrum training for 18 folks Rally has provided Agile training for an infrastructure team which is kicking off an new upgrade project Electric field engineers want a follow-up project to rework some of the “klutzy” parts of the initial system Minimal project management expense from Autodesk (a couple hours of administrative cost) Project metrics are amazing! – they tell a great management story 69% fewer defects 30% lower project cost (this is the fixed price fudge factor) 50% less code 4x reduction in logic complexity 20% less test cases, but better test coverage
  8. StoneRiver Date
  9. StoneRiver Date
  10. StoneRiver Date
  11. StoneRiver Date
  12. StoneRiver Date
  13. StoneRiver Date
  14. StoneRiver Date
  15. I wrote this article based on all the bad practices or lack of practices I had seen by organizations who claimed that they were Agile. They weren’t Agile! AND they wanted to blame Agile for their problems
  16. So, I dug around to learn some more about how Agile was failing. This can be dirty work, digging into many organizations large and small about their ability to adopt Agile.. What I discovered, is that……………
  17. !!!
  18. What I discovered is that there are BEAUTIFUL of how to adopt Agile, patterns of practices that the way I have seen organizations Adopt Agile and not slip into those failure practices
  19. There are beautiful patterns we can embrace that lead to success. This success with Agile is vital be on the top in the 21 st century global economy.
  20. Be prepared to make big changes! Invest to win. These patterns are a fundamental shift in how we work. But, we have no choice. To be sustainable, we have to be prepared to change our world. And in return for the hard work, we discover that we we change our world in a way that rewardds us and brings great benefits! 2009 Servant Leadership Jean Tabaka - Rally Software
  21. So don’t abandon Agile as I have seen these other organizations do! They believed Agile was the problem their adoption was the problem. And so they never really derived the great benefits available. They are just GIVING UP!!!!! Today, I want you to consider truly believing in these patterns and their practices. If you are willing to do so, I believe there are wonderful benefits for you and your teams and your customers.
  22. BENEFITS YOU WILL DERIVE Servant Leadership Jean Tabaka - Rally Software 2009
  23. 3 categories of success patterns
  24. 3 categories of success patterns
  25. We don’t just do Agile because it is cool to say, or that we are just tired of Waterfall. We have to have a reason.
  26. Really what is driving YOUR organization to do Agile? 12 Agile Adoption Failure Modes Jean Tabaka - Rally Software 2009
  27. Are you in a crisis? Or are you in a culture in your company that is always lookiing for ways to improve. Or do you want to be a company that gets out of being reactive to crisis and instead DRIVE the market by constantly improving, constantly being innovative. Think of some of the companies Mary mentioned yesterday: Amazon, Google, Tandberg. They were workiing out of a culture of improvement and innovation.
  28. When you are working out of crisis, it is be cause you have fallen behind in the market place and you need to catch up. You are losing and so you are working out of a sense of scarcity. Agile helps us move to working out of a goal or expansion. There is so much to do, so many great ideas, how can we bring our great idea to market faster!?
  29. That means you really have a vision for where you want to go, and how you’ll know you have been successful. Rally, every year, we evaluate our goal. When we started, there were very few Agile project management tools. Agile was new! Waterfall and Rational Unified Process were MUCH more popular and widely used. Did we choose to go into those markets and grab scarce resources? NO! We choose to go into a market where we beileived there was great opportunity. This is what Apple has done with each of its products. It has set a high level vision and it has set it out of a sense of the expansive market that lies out there.
  30. Our second patter in the “Getting Started” patterns. It’s no good having a great vision if you don’t have an engaged executive sponsor, someone who is prepared to defend your move to Agile to the rest of the company. Again, Agile isn’t easy and a lot of companies will say GREAT! Do Agile but I expect you to be successful RIGHT away. When you learned to ride a bike, it would be like your parent saying, “Great! When you hop on that bike, I want you to be able to ride immediately and perfectly! Otherwise, you have to go back to walking everywhere because it is just too hard.” No we need someone who will help us learn and be successful.
  31. I worked with Israel at BMC in 2005. He had worked with Rally before rolling out Agile. When he moved to a much larger company and was responsible for rolling out a very complex product set, he knew that there was only one thing he could do. The product line was in a crisis mode and he needed to save it. So he asked his group of 500 people to have faith in him, to be willing to dramatically change their world.
  32. He called this his Agile Social contract. A good Engaged Executive sponsor creates a social contract with their employees. Their leadership is about want to help their employees and to help them understand why it is valuable to adopt AGILE and to do the hard work
  33. In your Agile social contract, you are able to help your employees understand “What’s In It for me?” Why should I do this? Why can’t I just keep doing things the way I always did. Leave me alone! The Executive sponsor has an ability to hold the vision for the group and to help them understand either the crisis or the opportunity for innovation and expansion that is out there for them if they are willing stick with him or her to adopt Agile. And when they are part of a team that is successful at Agile: -- intrinsic reward -- professional growth -- sustainable software development that doesn’t demand that you give your life away. This has been important to us at our company and is something we coach executives about all the time when we talk with them about adopting Agile
  34. Our 3 rd “Getting Started” pattern is to create a “Planning framework for rollout” How can we build more opportunity of success into our Agile adoption while we are getting started.
  35. I’ve discovered that it is vital to create a rollout plan. You and your team need to have some ability to look out beyond today or tomorrow and say, “”How are we going to do this?” We have a hundred teams. Let’s just start right now…EVERYBODY
  36. The large insurance company I worked with. We have been working with eBay in the United States and India. It has been important for the executive team to create a plan for what they will do with Agile. For each business goal that you have, what will you measure to see if you are being successful (number of teams at a certain level of expertise?
  37. What this really looks like is not so much steps as overlapping waves. One of the early decisions you make is about how far you want to go and how fast. how far – not all the way agile? a program? how fast – how much learning? how much appetite for change?
  38. For each “wave” or “release”, what teams will we target. What are the goals for each release. What support/training will we provide. After each “release”, run a retrospective to identify what about the rollout is going well, what’s not going well, what adjustments should we make. After each release, plan the next release. Update roadmap as needed.
  39. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  40. What other companies have been doing this successfully? Help your organization learn about these success stories?
  41. Books are not enough alone. It is so valuable to find others who have done this and know what the practices are that bring success and what the practices are that invite failure.
  42. I have seen too many organizations not invest enough in training for EVERYONE. What does the team need to learn that is new? What will the Scrum Master do that is different? How will the business engage differently? How will managers act more in service to the team?
  43. 3/4/09 - 3/5/09 Implementing Agile Teams Rally Software
  44. Learn from a few teams and then apply your successes from there.
  45. We’ve developed a framework that reflects what we’ve seen be successful in large-scale agile rollouts. FPI Steps reflect that it is iterative and incremental. Also reflects failure modes we’ve seen—like trying to scale “amateur” agile, or staying at the team level but never putting together the structures that support scale.
  46. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  47. Agile Scales by Replicating number of x-functional teams. We don’t increase Agile team size! Agile improves collaboration across all roles with greater transparency into work in progress, quality, readiness and costs.
  48. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  49. Pairing in success, pairing in learning and improving
  50. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  51. Pairing in success, pairing in learning and improving
  52. As we launch new teams (expansion), we continue to pay attention to maturity Ag teams, so that teams don’t get frustrated and so that we introduce the discipline to help teams deliver consistently.
  53. Pairing in success, pairing in learning and improving
  54. Pairing in success, pairing in learning and improving
  55. As we launch new teams (expansion), we continue to pay attention to maturity Ag teams, so that teams don’t get frustrated and so that we introduce the discipline to help teams deliver consistently.
  56. Pairing in success, pairing in learning and improving
  57. Pairing in success, pairing in learning and improving
  58. --Communication support -- collaboration support -- configuration management -- automated testing environment -- continuous integration -- high visibility -- transparency in everything!!! Agile, Lean and the PMO Better Software 2009 Jean Tabaka - Rally Software
  59. Pairing in success, pairing in learning and improving
  60. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  61. Pairing in success, pairing in learning and improving
  62. Certified ScrumMaster Training V15.5- JET3 Certified ScrumMaster training - v14.13 © 2007 - Rally Software Development Corp
  63. Pairing in success, pairing in learning and improving
  64. Pairing in success, pairing in learning and improving
  65. Not the Worker
  66. Pairing in success, pairing in learning and improving
  67. 3/4/09 - 3/5/09 Implementing Agile Teams Rally Software
  68. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  69. Pairing in success, pairing in learning and improving
  70. Pairing in success, pairing in learning and improving
  71. Pairing in success, pairing in learning and improving
  72. Pairing in success, pairing in learning and improving
  73. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  74. Pairing in success, pairing in learning and improving
  75. Pairing in success, pairing in learning and improving
  76. Corporate Planning meeting in 2007. Grown a little since 2006, still using Rockefeller, Gazelles, and Rocks. Added some facilitation, me 
  77. Pairing in success, pairing in learning and improving
  78. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  79. Pairing in success, pairing in learning and improving
  80. 3/4/09 - 3/5/09 Implementing Agile Teams Rally Software
  81. Pairing in success, pairing in learning and improving
  82. Pairing in success, pairing in learning and improving
  83. Pairing in success, pairing in learning and improving
  84. For each “wave” or “release”, what teams will we target. What are the goals for each release. What support/training will we provide. After each “release”, run a retrospective to identify what about the rollout is going well, what’s not going well, what adjustments should we make. After each release, plan the next release. Update roadmap as needed.
  85. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  86. Pairing in success, pairing in learning and improving
  87. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  88. There are beautiful patterns we can embrace that lead to success
  89. YOU have an opportunity to take what I’ve presented here today and apply it in your life RIGHT NOW. 12 Agile Adoption Failure Modes Jean Tabaka - Rally Software 2009
  90. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  91. Patterns of success, beautiful patterns will bring you success, be on the top in the 21 st century global economy
  92. BENEFITS YOU WILL DERIVE Servant Leadership Jean Tabaka - Rally Software 2009
  93. Be prepared to make big changes! Invest to win. These patterns are a fundamental shift in how we work. But, we have no choice. To be sustainable, we have to be prepared to change our world. 2009 Servant Leadership Jean Tabaka - Rally Software