Copyright 2008 Scott W. Ambler www.ambysoft.com/surveys/ Agile Practices and Principles Survey 2008 Scott W. Ambler www.ambysoft.com/scottAmbler.html Michael.

Slides:



Advertisements
Similar presentations
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Advertisements

Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
E X treme Programming & Agile Modeling Copyright © 2003 Patrick McDermott UC Berkeley Extension
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Software Development Methodologies 1. A methodology is: A collection of procedures, techniques, principles, and tools that help developers build a computer.
Agile Project Management with Scrum
Agile development By Sam Chamberlain. First a bit of history..
Copyright 2006 Scott W. Ambler Data Quality Survey Results Scott W. Ambler
Copyright 2011 Scott W. Ambler IT Project Success Survey 2011 October 2011 Scott W. Ambler
Agile Architecture? Paul Lund 24 th Nov Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it.
Copyright 2010 Scott W. Ambler Enterprise Architecture Survey Results DDJ State of the IT Union Survey January 2010 Scott W.
Copyright 2011 Scott W. Ambler Agile and Enterprise Architecture March 2011 Survey Results Scott W. Ambler
Agile Methods.
An Agile View of Process
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
How Agile Are You? Larry Apke Agile Expert
Copyright 2006 Scott W. Ambler Agile Survey Results Summary Scott W. Ambler
Copyright 2007 Scott W. Ambler Agile Adoption Survey 2007 Scott W. Ambler
1 Agile Methodology & Programming Ric Holt July 2009.
Software Engineering Modern Approaches
The Agile Primer July 2008 © ThoughtWorks 2008.
Developed by Reneta Barneva, SUNY Fredonia Agile Development.
Chapter 4 Agile Development
AGILE Methodology. AGILE  derived from the word ‘agile manifesto’, also called the Manifesto for Agile Software Development which is a formal proclamation.
OPM: the USAJOBS Product Owner Perspective By Alesia Booth & Richard Cheng.
Copyright 2010 Scott W. Ambler Scrum Certification Survey Scott W. Ambler
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Project Workflow. How do you do it? -Discussion-
Copyright 2010 Scott W. Ambler IT Project Success Survey 2010 May-June 2010 Scott W. Ambler
Copyright 2008 Scott W. Ambler Process Framework Survey 2008 Scott W. Ambler
Copyright 2013 Scott W. Ambler Agile Project Initiation Survey Results Scott W. Ambler
AGILE COTS Václav Pergl We are uncovering better ways of developing software by doing it and helping others do it. Through this work.
1 11/21/2015 ã 2007, Spencer Rugaber Agile Manifesto February, 2001 XP, SCRUM, DSDM, Adaptive Software Development,
Copyright 2009 Scott W. Ambler State of the IT Union Survey September 2009 Scott W. Ambler
Why (or When) Agile Fails Creating high performance software delivery teams.
Copyright 2013 Scott W. Ambler How Agile Are You? Survey Results Scott W. Ambler
Source: Ambysoft 2008 TDD Survey Copyright 2008 Scott W. Ambler Test-Driven Development Survey 2008 Scott W. Ambler.
Copyright 2010 Scott W. Ambler How Agile Are You? Survey Results Scott W. Ambler
- Discussion of Chapter 1 in Martin and Martin.  We are uncovering better ways of developing software by doing it and helping others do it. Through this.
Chapter 3 Agile Development
Copyright 2008 Scott W. Ambler Agile Adoption Survey 2008 Scott W. Ambler
Copyright 2009 Scott W. Ambler DDJ State of the IT Union Survey November 2009 Scott W. Ambler
Copyright 2010 Scott W. Ambler Agile Project Success Survey 2010 April 2010 Scott W. Ambler
Copyright 2010 Scott W. Ambler State of the IT Union July 2010 Survey Results Scott W. Ambler
Copyright 2008 Scott W. Ambler Modeling and Documentation Survey 2008 Scott W. Ambler
Agile Introduction Emerson Murphy-Hill. Agile Manifesto/Alliance XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD February 2001 (Snowbird,
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
Baby Steps to Agility How to Grow Into Agile. A little about me A little about Agile Growing into Agile Questions Goals.
Project Workflow.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Project Management and the yin & yang of
Introduction to Agile Software Development
Principles for Agile Development
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Project Workflow.
Agile Project Initiation Survey 2009
Teaching Agile Methods CSEE&T 2017, Savannah, Georgia
Project Management and the Agile Manifesto
How to Successfully Implement an Agile Project
Rosa María Torres de Paz
Agile Practices Survey 2009
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Chapter 3: Agile Software Processes
Projects, Assignments, and other Assessments
The Current State of Data Management
Agile Development.
Presentation transcript:

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