Copyright 2008 Scott W. Ambler Agile Practices and Principles Survey 2008 Scott W. Ambler Michael Vizdos

Copyright 2008 Scott W. Ambler How To Use These Slides I have provided these slides, and the raw data behind them, so that others can use them in their own work. You may reuse all, or a part of, this slide deck as long as you provide a clear reference to the source. The suggested reference is: Results from Scott Ambler and Michael Vizdos’s July 2008 Agile Practices and Principles Survey posted at Some slides have notes

Copyright 2008 Scott W. Ambler About the Survey July 2008 Message sent out to several agile Yahoo groups mailing lists (extremeprogramming, agilemodeling, agiledatabases, scrumdevelopment, testdrivendevelopment) Data, summary, and slides downloadable from respondents: –36.9% were developers, 36.9% were in management –42% had years IT experience, 17.3% had 21+ years –31.3% worked in orgs of people –57.3% worked in North America, 22.7% in Europe, 7.2% in Asia

Copyright 2008 Scott W. Ambler Project Management Practices Iteration planning (3.54) Daily Scrum Meeting (3.29) Prioritized worklist (3.08) High-level release planning (2.19) Retrospectives (1.84) One Product Owner (1.55) Burndown chart (1.51) Potentially Shippable Software (1.51) Status Reports (1.15) Story Board with Task Breakdowns (0.83)

Copyright 2008 Scott W. Ambler Development Practices Coding Standards (2.30) Collective Code Ownership (1.97) Continuous integration (1.94) Database standards (1.86) UI standards (1.65) Pair programming (-1.34)

Copyright 2008 Scott W. Ambler Quality Practices Code Refactoring (1.79) UI Testing (1.54) Automated Developer Testing (1.08) TDD (-0.08) UI Refactoring (-0.22) Database refactoring (-0.31) Automated Acceptance Testing (-0.87) Database regression testing (-1.03) Executable Specs (-1.43)

Copyright 2008 Scott W. Ambler Modeling Practices Active Stakeholder Participation (1.95) Requirements Envisioning (1.50) Architecture Envisioning (1.31) Documentation as Requirement (0.49) Model Storming (-0.84)

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software 2.Our agile project teams welcome new or changing requirements, even just before delivery 3.Project Stakeholders work closely with our agile teams and are readily available 4.At regular intervals our agile teams demonstrate potentially shippable software to their stakeholders

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.We build agile teams around motivated individuals 2.Our agile teams are provided with the env. and support that they need to succeed 3.Our agile teams are trusted to get the job done 4.Our agile teams are self organizing

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.Working software is the primary measure of progress for our agile teams 2.Our agile teams are allowed to work at a sustainable pace 3.Our agile teams identify what done means at the beginning of each iteration 4.Our agile teams only take credit for work that is actually done at the end of each iteration

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.Our agile teams give continuous attention to technical excellence and good design 2.Simplicity, the art of maximizing the amount of work not done, works well in practice for our agile teams 3.We do some initial architecture modeling at the beginning of agile projects to get going in the right technical direction 4.The architecture and design details emerges over time on our agile projects

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.We do some initial requirements modeling at the beginning of agile projects for scoping and planning purposes 2.The requirements details emerge over time on our agile projects 3.Our agile teams have an understanding of the correct balance of documentation or other artifacts for delivery

Copyright 2008 Scott W. Ambler How well do you agree with the statements… 1.At regular intervals the team reflects on how to become more effective in future iterations 2.The team actually adjusts its behavior in the next iteration by focusing on the highest priority items

Copyright 2008 Scott W. Ambler Effectiveness of Communication Strategies (bigger the number the better) Within TeamWith Stakeholders Face to face (F2F) F2F at Whiteboard Detailed Documentation Overview documentation Overview diagrams Online chat Teleconference calls Videoconferencing