How Agile Are You


Published on

How do we measure the level of our agile adoption?

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

How Agile Are You

  1. 1. HOW AGILE ARE YOU Silviu-Horea Eigel Software Engineer
  2. 2. Too Agile • Everybody is doing agile
  3. 3. State of agile • In the past companies hired consultants to introduce agile • Now companies hire consultants to fix agile • "Rescuing Scrum teams keeps me in business"
  4. 4. Practices • Teams are: • working in short cycles • planning frequently • but not in shared workspaces • don't use good engineering practices • don't deliver releasable software • don't finish stories by the end of each Sprint • don't work in cross-functional teams • don't have on-site customers • don't emphasize high-bandwidth communication
  5. 5. The reward, not the method • Quick wins • Rotten teeth
  6. 6. Scrum misapplied • Has a set of principles • But a small set of practices • Which don’t enforce enough the principles • No engineering practices
  7. 7. ScrumBut • Many organizations in the world are adopting Scrum, and many of those are adapting Scrum • Unfortunately, many organizations change Scrum to accommodate the inadequacies or dysfunctions instead of solving them. Ken Schwaber • <We use Scrum, but> <we have these unique circumstances> <so we have had to modify Scrum so it works here>
  8. 8. Indicators of healthy agile • Can you meet the stakeholders? • Can you run regression test suite? • Do you have working software? • Is source code of high quality and under SC? • Team takes responsibility for their work and automate as much as possible?
  9. 9. ScrumBut and Nokia test • ScrumBut - Revenue up 0-35%, scores 7 or less • Pretty Good Scrum - Revenue up 150% - 200% • Good Scrum - Revenue up 300% • Great Scrum - Annual revenue up 400%!
  10. 10. Question 1 - Iterations a) No iterations b) Iterations > 6 weeks c) Variable length < 6 weeks d) Fixed iteration length 6 weeks e) Fixed iteration length 5 weeks f) Fixed iteration 4 weeks or less
  11. 11. Question 2 - Testing a) No dedicated QA b) Unit tested c) Feature tested d) Features tested as soon as completed e) Software passes acceptance testing f) Software is deployed
  12. 12. Question 3 - Agile Specification a) No requirements b) Big requirements documents c) Poor user stories d) Good requirements e) Good user stories f) Just enough, just in time specifications g) Good user stories tied to specifications as needed
  13. 13. Question 4 - Product Owner a) No Product Owner b) Product Owner who doesn’t understand Scrum c) Product Owner who disrupts team d) Product Owner not involved with team e) Product owner with clear product backlog estimated by team before Sprint Planning meeting (READY) f) Product owner with release roadmap with dates based on team velocity g) Product owner who motivates team
  14. 14. Question 5 - Product Backlog a) No Product Backlog b) Multiple Product Backlogs c) Single Product Backlog d) Product Backlog clearly specified and prioritized by ROI before Sprint Planning (READY) e) Product Owner has release plan based on Product Backlog f) Product Owner can measure ROI based on real revenue, cost per story point, or other metrics
  15. 15. Question 6 - Estimates a) Product Backlog not estimated b) Estimates not produced by team c) Estimates not produced by planning poker d) Estimates produced by planning poker by team e) Estimate error < 10%
  16. 16. Question 7 - Burndown Chart a) No burndown chart b) Burndown chart not updated by team c) Burndown chart in hours/days not accounting for work in progress (partial tasks burn down) d) Burndown chart only burns down when task is done (TrackDone pattern) e) Burndown only burns down when story is done f) Team knows velocity g) Product Owner release plans based on known velocity
  17. 17. Question 8 - Team Disruption a) Manager or Project Leader disrupts team b) Product Owner disrupts team c) Managers, Project Leaders or Team leaders assigning tasks d) Have Project Leader and Scrum roles e) No one disrupting team, only Scrum roles
  18. 18. Question 9 - Team a) Tasks assigned to individuals during Sprint Planning b) Team members do not have any overlap in their area of expertise c) No emergent leadership - one or more team members designated as a directive authority d) Team does not have the necessary competency e) Team commits collectively to Sprint goal and backlog f) Team members collectively fight impediments during the sprint g) Team is in hyper productive state