1 / 12

Measuring Agility

Measuring Agility. How Agile Are You ? Larry Apke Agile Expert www.agile-doctor.com larry@agile-doctor.com. “Nokia” Scrum Test – History. There were a number of grassroots Agile scrum implementations at Nokia Networks (merger between Nokia and Siemens) mid-2000s.

tad
Télécharger la présentation

Measuring Agility

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Measuring Agility How Agile Are You? Larry Apke Agile Expert www.agile-doctor.com larry@agile-doctor.com

  2. “Nokia” Scrum Test – History • There were a number of grassroots Agile scrum implementations at Nokia Networks (merger between Nokia and Siemens) mid-2000s. • A small agile coaching team was formed to support these grassroots movements. • As part of their coaching they needed to determine a way to “rate” teams adoption of Scrum methodology. • The Nokia test was not really a test, it was called "you are not iterative when“. • A slide deck on some of the questions made it to Jeff Sutherland who used it to create “The Nokia Test”.

  3. “Nokia” Scrum Test – Why? • When the coaching team visited some “scrum teams” it was fairly obvious that they were not doing scrum • "we do iterative development, our last iteration was planned to be one year long, but it actually took two!“ • "we do scrum, we are now in our 6th planning sprint". • The coaching group needed to have a baseline to know which groups to help and what help they needed • This test measures how well teams do the ceremony of Scrum

  4. “Nokia” Scrum Test – What? • 11 multiple choice questions – Iterations, Testing, Agile Specification, Product Owner, Product Backlog, Estimates, Sprint Burndown Chart, Velocity, Releases Planned Based on Velocity, Team Disruption and Team. • For Example, Testing • No dedicated testers on team • Unit tested • Feature tested • Feature tested as soon as completed • Software passes acceptance testing • Software is deployed

  5. “Nokia” Scrum Test – How I Use? • Give a copy of the test to team members. • Allow them time to fill out and return. • Allow them to remain anonymous or choose not to complete. • After a few days, calculate the scores and share with the team. • Actual results.

  6. “Nokia” Scrum Test – Links • History - http://blog.odd-e.com/basvodde/2011/02/history-of-nokia-test.html • Jeff Sutherland Nokia Test Site http://scrum.jeffsutherland.com/2009/07/nokia-test-online.html • Scrum But … Test http://antoine.vernois.net/scrumbut/

  7. Agile Principles • In 2001 the founders of Agile created two things – a manifesto and 12 principles. • Therefore, if we wish to be Agile we must embody the dictates outlined in the manifesto and 12 principles. • The team is given a survey that has the 12 principles and is asked to rate who well the team embodies these principles. • The “Nokia scrum test” measure ceremony, this measures overall goals.

  8. Agile Principles • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

  9. Agile Principles • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

  10. Agile Principles • I give survey to my team members. • This is my report card for my job as scrum master. • Actual Results

  11. Other Agile Measurements Links • Measuring Agile in the Enterprise: 5 Success Factors for Large-Scale Agile Adoption – Michelle Mah’s Presentation on Benefits of Agile Adoption http://www.infoq.com/presentations/5-Success-Factors-Michael-Mah • How Agile Are You? (Take This 42 Point Test) http://www.allaboutagile.com/how-agile-are-you-take-this-42-point-test/ • Agile Karlskronatest http://www.piratson.se/archive/Agile_Karlskrona_Test.html • DACS ROI Dashboard http://www.thedacs.com/databases/roi/

  12. Questions

More Related