SlideShare ist ein Scribd-Unternehmen logo
1 von 5
Downloaden Sie, um offline zu lesen
COVER STORY                                   COVER STORY



What is This Thing Called ‘Agile’?


                                                                                   John C Goodpasture

There are new and
challenging ideas in project   Dilbert:   We need 3 more programmers.
management, ideas              Boss:      Use agile programming methods.
especially suited for
                               Dilbert:   Agile programming does not mean doing more work with less
managing dynamically
                                          people.
complex software projects
— projects that put ever       Boss:      Find me some words that do mean that and ask again.
increasing complexity in                                     – Dilbert™ is a creation of Scott Adams
the hands of users and
consumers. ‘Agile’ is the



                               A
umbrella term for what                  gile means small teams, working collectively and
we are talking about. In                collaboratively, to deliver “frequent, incremental releases of
this article, the author                innovative functions and features, developed iteratively and
explores the motivations       by evolutionary builds, prioritized just-in-time for need and
for the Agile Movement         affordability, and produced at the best possible value”.
and the advantages, agile         Frequent, incremental releases mean that several times a year, as
methods have for small         often as the enterprise can absorb change, even every few weeks, an
software projects. Agile is    update to the product base is put into production.
not a silver bullet, but it
                                   ‘Developed iteratively’, means that each build is the product of
has the potential to be
                               revisiting the development cycle repetitively, each cycle addressing
very effective, when
                               some subset of the requirements, and several such cycles making up
requirements are dynamic,
                               the release. ‘Evolutionary’ means that the product is not fully planned
the customer has an
                               in advance; the design features and functions emerge and become
urgent need, and the
                               defined during development cycles; and releases as users have a
deadlines for value delivery
                               chance to evaluate and critique the solution.
are short.
                                   ‘Prioritized just-in-time for need and affordability’ means that the
                               customer has a seat at the table, so as to speak. The customer is allowed
                               to change requirements and set priorities at every release, although
                               constrained within a limit of affordability, specified in the business plan.
                                  And ‘produced at the best possible value’ means that the customer
                               will get a lot for the budget, but the scope may vary a bit from the
                               vision described in the business plan. Requirements are never really
                               frozen or baselined, so the final product may have features and
                               functions, not originally envisioned.

© 2009 John
August 2009 C Goodpasture. All Rights Reserved.                                                         31
What is this Thing Called 'Agile'?


                                                About the Author
    John C Goodpasture, PMP, is a Program Manager, Coach, Author, and Project Consultant specializing in
    technology projects, strategic planning, project office operations. He is authoring a book on Agile Project
    Management that is anticipated for publication at the end of 2009. He blogs at johngoodpasture.blogspot.com.
    The author can be reached at www. sqpegconsulting.com

Many Methodologies Called Agile
The methodologies included under the agile umbrella go by many names: SCRUM, XP, CRYSTAL
Family, EVO, and DSDM.1 And, the others are: Feature-driven Design, Adaptive Software
Development, Lean Development, Team Software Process (TSP) and Personal Software Process (PSP).2
All embrace the Agile Manifesto and the Agile Principles supported by the Agile Alliance.3
    Before these, there were others that had a longer legacy and had set the stage: Spiral, RUP, JAD,
and RAD, to name a few.4 Each in its own way, address the ever-present dilemma in user-dominated
software, to wit: what the customer says they need and want, is constantly uncertain and often
unaffordable, sometimes not even feasible. Indeed, like the classic case of the ‘wicked problem’, the
‘solution often defines the requirements’ – “I’ll know it when I see it”!5
    What agile methods do is, empower small teams to rapidly respond to a changing landscape and
deliver customer value quickly, well within the longer cycles of business and markets. Agile teams
work in small chunks of scope that can be stabilized over relatively short periods, consulting customers
and users as the solution emerges, releasing product increments frequently, and then inviting serious
critique after every release.
Not Plan-Driven
Agile is the antithesis of the plan-driven methods, the main example of many years being the waterfall
method, but more recently ISO 12207, CMM (I),6 Prince 2, and high reliability methods like Clean
Room.7 Unquestionably, plan-driven methodologies have their place. When the requirements are
safety-critical, mission-critical, high reliability, or security critical, the careful structured analysis of
requirements accompanied by strict governance is mandated.
    To say agile methods are not plan-driven does not mean that agile projects are not planned – they
are, but more just-in-time, than the plan-driven sequential methodologies. The top-level agile plan is
in the business case. Detail plans are made by teams as work begins.

1
      XP is the acronym for ‘extreme programing’. EVO stands for the Evolutionary methodology. DSDM is Dynamic
      Systems Development Method.
2
      PSP and TSP are service marks of Carnegie Mellon University.
3
      See http://www.agilealliance.com and http://www.agilemanifesto.org/
4
      Acronyms in this list are RUP for Rational Unified Process, a product of IBM/Rational, RAD for rapid application
      development, JAD for joint application development.
5
      The so-called ‘wicked problem’ is a class of problems that are somewhat circular and for which, the requirements
      cannot be stated, until the solution is in place. These problems are often political, sometimes subjectively social,
      and other times technical. There is a body of knowledge around solving wicked problems. See my blog at
      johngoodpasture.blogspot.com for more information.
6
      CMM (I) is Capability Maturity Model – Integration that puts together software engineering, system engineering,
      and product integration in a coordinated set of practices. CMM (I) is a service mark of Carnegie Mellon University.
7
      TSP, Team Software Process, PSP, Personal Software Process are service marks of Carnegie Mellon University.


32                                                                                                   Projects and Profits
COVER STORY


Do These Methods Work?
The quick-read bottom line on agile methods is that they do work, they do shorten the schedule, and
they do provide a very high quality product (Table 1).8 However, agile is not a silver bullet; it is not
appropriate in all situations, and only works, if the proper environment and management mind-set
are provided to the project.

                                             Table 1: Agile Methodologies
    •   Agile methodologies depart in significant ways from traditional project protocols.
    •   They are most applicable, when requirements are changing, unknown, or unknowable.
    •   They work best in project situations of less than a handful of small teams, typically fewer than 50
        developers.
    •   They work better in-house than through the constraint of a contract; they work better co-located than
        though the cultural translation of a virtual team.
    •   Process-centric methods are better for safety-critical and high-reliability programs.

   Project managers should look seriously at what is happening here. The troublesome shortfalls in
performance and customer value, made all the more acute by the rapid business cycles in the web
era, caused some industry innovators to look at the whole thing in an entirely different way. From the
product development community, the software engineering community, and the system engineering
community, truly innovative protocols have been devised and put into practice. These procedures,
not only apply project talent differently, but also reorder the intuitive sequence of project events that
has been the mainstay for generations.
The Agile Project Life Cycle
Agile methods are the antithesis of what program and project managers know as the Plan-Driven
Project Development Life Cycle (PD-PDLC) (Table 2). The PD-PDLC is sequential, beginning with
gathering requirements and ending with delivering products. Plan-driven methods are characterized
by the Big Design Up Front (BDUF). The Agile PDLC, Ag-PDLC, is entirely different, as shown in
Table 2.

                                         Table 2: The Agile PDLC, Ag-PDLC

    •   Outcomes are incrementally planned and specified, built iteratively, and delivered in frequent releases
        of limited but valuable capabilities.
    •   Agile projects are governed by a top level business plan that envisions a product goal, business
        milestones, and a level of affordability.
    •   Scope and quality, the budget, and the schedule are framed in the business plan but the details emerge
        as the project progresses.
    •   Value is earned incrementally as outcomes are committed to production.
    •   Customers are allowed to change their mind from one release to the next in order to keep the value
        proposition ever in alignment with business and market realities.

8
        For some metric information on the track record of agile projects, see Appendix E, Empirical Information in:
        Boehm B and Turner R (2004), Balancing Agility and Discipline, Appendix E, Addison-Wesley, New York.


August 2009                                                                                                       33
What is this Thing Called 'Agile'?


     The Ag-PDLC has four distinguishing characteristics that set it apart from the PD-PDLC:
1. Emergent
     The processes and procedures used by the implementation teams emerge from the team’s analysis
     of the requirements and tasks. In effect, teams adapt; process control is achieved empirically by
     observation and reaction, not by defined capabilities with error bounds, as in Six Sigma.9
2. Iterative
     The PDLC is a string of iterations in which, a backlog of requirements is burned-down one
     iteration at a time, until exhausted.
3. Evolutionary
     The product details adapt to the customer needs and wants. The customer is allowed to reset
     priorities, add, delete, and change the backlog, according to market and business need.
4. Incremental
     The outcomes of iterations are packaged for release to production as an increment to the product
     base.
    Note: It takes a combination of the incremental and the evolutionary to really be agile. Some PD-
    PDLCs are incremental, but not evolutionary.
   To maintain alignment of deliveries with the value proposition in the business case, iterations
are relatively short, from about 2-3 weeks in the XP methodology, 30 days in SCRUM, to something
longer, according to circumstances in Crystal and EVO. Releases are made as frequently as the
business can absorb change, but typically, no less frequently than a calendar quarter. There are no
hard and fast rules; each project sets the agenda with the customer.
A Process of Cycles
All agile methodologies are about responsiveness, exercised iteratively. All methods embrace the
concept of repeating nested cycles, although the terminology varies from one method to the next.
   The building block is the standard day, ideally an eight hour stint of value-added activity. Each
day begins with a team review that is time-boxed – that is, limited to a fixed time duration – followed
by development activity, inspection, and ideally ending with the day’s outcome integrated into the
product base.
    Iterations are built up of days. In SCRUM, the iteration is called a sprint; in EVO it is a delivery
cycle. An iteration is a time-boxed duration of a few weeks at most, during which, a selected backlog
of requirements is developed. The requirements are made stable during the iteration. The change to
the product base at the end of the iteration is a product increment.
   Iterations, one or more, build up a release event. A release is a product increment going into
production operations for internal or external use.
9
     Six Sigma is a quality management process in which, a problem analysis protocol is followed by solutions that
     implement error control within approximately three parts in a million. Errors are sensed and corrective information
     is fed back to bring the process within the Six Sigma boundaries.
     Defined process control is a concept of manufacturing, promoted strongly by the work of W. Edwards Deming
     and others in the post World War II era. It presumes definable error limits that are acceptable in the finished
     product, means to measure, and means to correct. See Schawber K (2004), Agile Project Management with SCRUM,
     pp. 2-4, Microsoft Press, Redmond, WA.


34                                                                                                  Projects and Profits
COVER STORY


    Plans are made around rolling waves.10 A wave is a planning horizon, consisting of one or more
releases. The planning horizon, typically not more than a few months, is the distance we can see
ahead with reasonable project level vision.
   Waves are synchronized with business cycles. The normal business cycles are quarterly, annual,
and multi-year, to correspond to tactical results, annual results, and strategic planning, respectively.
Agile Teams
Agile teams are small, self-organized units that are multifunctional and internally redundant. Teams
stay together for the life of the project. In general, teams do not handover their outcomes to other
teams. The outcomes of each team are integrated into production at each release. Teams are coached
by the project manager but otherwise organize themselves for the daily work cycle.
    The work ethic of teams is collaborative in a manner that each member is assisted by others. In the
XP methodology, members program in pairs. Each
member is committed and accountable for his own work
and the success of the team. Projects scale up by adding         The value of agile methods is the
teams. A coordinating body of team leaders meets daily             success that meets frequent,
to coordinate team work.                                       incrementally delivered features and
    Communications within teams is by face-to-face                functions, even in the swirl of
discussions and documentation outside of coding                complex and uncertain requirements
comments is minimized. In a practice called Test-
Driven-Design, XP methodologists document
requirements by using test scripts. If virtual teams are employed, a special effort is made to reduce
communications friction, so that an efficient daily cycle is maintained.
Conclusion
The value of agile methods is the success that meets frequent, incrementally delivered features and
functions, even in the swirl of complex and uncertain requirements.
   Plan-driven methods have their place, particularly on projects of high scale, safety-critical
requirements, mission-critical objectives, and many contract situations. However, they are decidedly
not appropriate in a dynamic requirement environment, not appropriate to fast and incremental
delivery, and are very cost inefficient on smaller projects.
   The sweet spot for agile projects is teams of less than 50 developers, where there is high value
placed collaborative work ethics and personal commitment and accountability for success.
   At the end of the day, we say that agile is: Small teams, working collectively and collaboratively,
with this mission:
     To deliver “frequent, incremental releases of innovative functions and features,
     developed iteratively and by evolutionary builds,
     prioritized just-in-time for need and affordability,
     and produced at the best possible value”.
                                                                                Reference # 17M-2009-08-06-01
10
     Goodpasture J (2007), “A Risk Perspective: Rolling Wave Planning is a Bet”, Projects and Profits, December,
     pp. 48-53.


August 2009                                                                                                  35

Weitere ähnliche Inhalte

Was ist angesagt?

Business Case for Agile - Time for ROI Check
Business Case for Agile - Time for ROI CheckBusiness Case for Agile - Time for ROI Check
Business Case for Agile - Time for ROI CheckTathagat Varma
 
Intro to Agile and Lean Software Development
Intro to Agile and Lean Software DevelopmentIntro to Agile and Lean Software Development
Intro to Agile and Lean Software DevelopmentAleksejs Truhans
 
The BA role in Agile Development
The BA role in Agile Development The BA role in Agile Development
The BA role in Agile Development Agileee
 
The Business Analyst’s Critical Role in Agile Projects
The Business Analyst’s Critical Role in Agile ProjectsThe Business Analyst’s Critical Role in Agile Projects
The Business Analyst’s Critical Role in Agile ProjectsTechWell
 
Communicating agile project status to executive managers
Communicating agile project status to executive managersCommunicating agile project status to executive managers
Communicating agile project status to executive managersAgileDad
 
Lean Software Development Alan Shalloway
Lean Software Development   Alan ShallowayLean Software Development   Alan Shalloway
Lean Software Development Alan ShallowayValtech UK
 
Dollars and Dates are Killing Agile
Dollars and Dates are Killing AgileDollars and Dates are Killing Agile
Dollars and Dates are Killing AgileRally Software
 
Building an Agile framework that fits your organisation
Building an Agile framework that fits your organisationBuilding an Agile framework that fits your organisation
Building an Agile framework that fits your organisationKurt Solarte
 
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-i
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iPMI-ACP Lesson 01 Nugget 2 Agile Methodologies-i
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iThanh Nguyen
 
Agile Values, Principles and Practices
Agile Values, Principles and PracticesAgile Values, Principles and Practices
Agile Values, Principles and Practicesjackcrews
 
Benefits of Agile Software Development for Senior Management
Benefits of Agile Software Development for Senior ManagementBenefits of Agile Software Development for Senior Management
Benefits of Agile Software Development for Senior ManagementDavid Updike
 
Value Driven Development by Dave Thomas
Value Driven Development by Dave Thomas Value Driven Development by Dave Thomas
Value Driven Development by Dave Thomas Naresh Jain
 
Business Value of Agile Methods: Using Return on Investment
Business Value of Agile Methods: Using Return on InvestmentBusiness Value of Agile Methods: Using Return on Investment
Business Value of Agile Methods: Using Return on InvestmentDavid Rico
 
12 principles for Agile Development
12 principles for Agile Development 12 principles for Agile Development
12 principles for Agile Development Julien Henzelin
 
Agile Software Development - Making Programming Fun Again
Agile Software Development - Making Programming Fun AgainAgile Software Development - Making Programming Fun Again
Agile Software Development - Making Programming Fun AgainCalen Legaspi
 
Understanding the Business Case for Agile
Understanding the Business Case for AgileUnderstanding the Business Case for Agile
Understanding the Business Case for AgileSeapine Software
 
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...David Rico
 

Was ist angesagt? (20)

Business Case for Agile - Time for ROI Check
Business Case for Agile - Time for ROI CheckBusiness Case for Agile - Time for ROI Check
Business Case for Agile - Time for ROI Check
 
Agile Webinar: Managing Distributed Teams
Agile Webinar: Managing Distributed TeamsAgile Webinar: Managing Distributed Teams
Agile Webinar: Managing Distributed Teams
 
Intro to Agile and Lean Software Development
Intro to Agile and Lean Software DevelopmentIntro to Agile and Lean Software Development
Intro to Agile and Lean Software Development
 
The BA role in Agile Development
The BA role in Agile Development The BA role in Agile Development
The BA role in Agile Development
 
The Business Analyst’s Critical Role in Agile Projects
The Business Analyst’s Critical Role in Agile ProjectsThe Business Analyst’s Critical Role in Agile Projects
The Business Analyst’s Critical Role in Agile Projects
 
Communicating agile project status to executive managers
Communicating agile project status to executive managersCommunicating agile project status to executive managers
Communicating agile project status to executive managers
 
Lean Software Development Alan Shalloway
Lean Software Development   Alan ShallowayLean Software Development   Alan Shalloway
Lean Software Development Alan Shalloway
 
Dollars and Dates are Killing Agile
Dollars and Dates are Killing AgileDollars and Dates are Killing Agile
Dollars and Dates are Killing Agile
 
Agile development
Agile developmentAgile development
Agile development
 
Building an Agile framework that fits your organisation
Building an Agile framework that fits your organisationBuilding an Agile framework that fits your organisation
Building an Agile framework that fits your organisation
 
IIIT Guest Talk 0512
IIIT Guest Talk 0512IIIT Guest Talk 0512
IIIT Guest Talk 0512
 
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-i
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-iPMI-ACP Lesson 01 Nugget 2 Agile Methodologies-i
PMI-ACP Lesson 01 Nugget 2 Agile Methodologies-i
 
Agile Values, Principles and Practices
Agile Values, Principles and PracticesAgile Values, Principles and Practices
Agile Values, Principles and Practices
 
Benefits of Agile Software Development for Senior Management
Benefits of Agile Software Development for Senior ManagementBenefits of Agile Software Development for Senior Management
Benefits of Agile Software Development for Senior Management
 
Value Driven Development by Dave Thomas
Value Driven Development by Dave Thomas Value Driven Development by Dave Thomas
Value Driven Development by Dave Thomas
 
Business Value of Agile Methods: Using Return on Investment
Business Value of Agile Methods: Using Return on InvestmentBusiness Value of Agile Methods: Using Return on Investment
Business Value of Agile Methods: Using Return on Investment
 
12 principles for Agile Development
12 principles for Agile Development 12 principles for Agile Development
12 principles for Agile Development
 
Agile Software Development - Making Programming Fun Again
Agile Software Development - Making Programming Fun AgainAgile Software Development - Making Programming Fun Again
Agile Software Development - Making Programming Fun Again
 
Understanding the Business Case for Agile
Understanding the Business Case for AgileUnderstanding the Business Case for Agile
Understanding the Business Case for Agile
 
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...
Lean & Agile Enterprise Frameworks: For Managing Large U.S. Government Cloud ...
 

Ähnlich wie What is this thing called Agile?

Agile intro resources
Agile intro resourcesAgile intro resources
Agile intro resourcesAnwar Sadat
 
Agile Software Development The Business of Innovation.pdf
Agile Software Development  The Business of Innovation.pdfAgile Software Development  The Business of Innovation.pdf
Agile Software Development The Business of Innovation.pdfEmily Smith
 
HanoiScrum: Agile co-exists with Waterfall
 HanoiScrum: Agile co-exists with Waterfall HanoiScrum: Agile co-exists with Waterfall
HanoiScrum: Agile co-exists with WaterfallVu Hung Nguyen
 
Agile presentation adriana feb 2012
Agile presentation adriana feb 2012Agile presentation adriana feb 2012
Agile presentation adriana feb 2012Adriana Beal
 
Scrum Framework Explained
Scrum Framework ExplainedScrum Framework Explained
Scrum Framework ExplainedNacho Montoya
 
Project Requriement Management Vs Agile software development
Project Requriement Management Vs  Agile software developmentProject Requriement Management Vs  Agile software development
Project Requriement Management Vs Agile software developmentbizpresenter
 
AGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxAGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxVardha Mago
 
Business Analyst As Product Owner
Business Analyst As Product OwnerBusiness Analyst As Product Owner
Business Analyst As Product OwnerCraig Brown
 
Agile Project management
Agile Project managementAgile Project management
Agile Project managementPraveen Sidola
 
Introduction to the Agile Methods
Introduction to the Agile MethodsIntroduction to the Agile Methods
Introduction to the Agile Methodssoftwareacademy
 
Week_03-Agile Developmnet.ppt
Week_03-Agile Developmnet.pptWeek_03-Agile Developmnet.ppt
Week_03-Agile Developmnet.pptRedHeart11
 

Ähnlich wie What is this thing called Agile? (20)

Agile pm v2
Agile pm v2Agile pm v2
Agile pm v2
 
Agile approach
Agile approachAgile approach
Agile approach
 
Agile intro resources
Agile intro resourcesAgile intro resources
Agile intro resources
 
Agile Software Development The Business of Innovation.pdf
Agile Software Development  The Business of Innovation.pdfAgile Software Development  The Business of Innovation.pdf
Agile Software Development The Business of Innovation.pdf
 
HanoiScrum: Agile co-exists with Waterfall
 HanoiScrum: Agile co-exists with Waterfall HanoiScrum: Agile co-exists with Waterfall
HanoiScrum: Agile co-exists with Waterfall
 
Agile presentation adriana feb 2012
Agile presentation adriana feb 2012Agile presentation adriana feb 2012
Agile presentation adriana feb 2012
 
Scrum Framework Explained
Scrum Framework ExplainedScrum Framework Explained
Scrum Framework Explained
 
Agile Methodologies & Key Principles
Agile Methodologies & Key Principles Agile Methodologies & Key Principles
Agile Methodologies & Key Principles
 
7.agila model
7.agila model7.agila model
7.agila model
 
Agile Development Models
Agile Development ModelsAgile Development Models
Agile Development Models
 
Agile vs Len Methodology
Agile vs Len MethodologyAgile vs Len Methodology
Agile vs Len Methodology
 
Project Requriement Management Vs Agile software development
Project Requriement Management Vs  Agile software developmentProject Requriement Management Vs  Agile software development
Project Requriement Management Vs Agile software development
 
Chapter 5
Chapter 5Chapter 5
Chapter 5
 
AGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docxAGILE PROJECT MANAGEMENT NOTES.docx
AGILE PROJECT MANAGEMENT NOTES.docx
 
Business Analyst As Product Owner
Business Analyst As Product OwnerBusiness Analyst As Product Owner
Business Analyst As Product Owner
 
Importance of Adaptive Planning in Agile
Importance of Adaptive Planning in AgileImportance of Adaptive Planning in Agile
Importance of Adaptive Planning in Agile
 
Agile Project management
Agile Project managementAgile Project management
Agile Project management
 
Introduction to the Agile Methods
Introduction to the Agile MethodsIntroduction to the Agile Methods
Introduction to the Agile Methods
 
7 Myths of Agile Development
7 Myths of Agile Development7 Myths of Agile Development
7 Myths of Agile Development
 
Week_03-Agile Developmnet.ppt
Week_03-Agile Developmnet.pptWeek_03-Agile Developmnet.ppt
Week_03-Agile Developmnet.ppt
 

Mehr von John Goodpasture

Five tools for managing projects
Five tools for managing projectsFive tools for managing projects
Five tools for managing projectsJohn Goodpasture
 
Risk management short course
Risk management short courseRisk management short course
Risk management short courseJohn Goodpasture
 
Agile earned value exercise
Agile earned value exerciseAgile earned value exercise
Agile earned value exerciseJohn Goodpasture
 
Agile 103 - the three big questions
Agile 103  - the three big questionsAgile 103  - the three big questions
Agile 103 - the three big questionsJohn Goodpasture
 
Agile for project managers - a sailing analogy-UPDATE
Agile for project managers  - a sailing analogy-UPDATEAgile for project managers  - a sailing analogy-UPDATE
Agile for project managers - a sailing analogy-UPDATEJohn Goodpasture
 
Dynamic Systems Development, DSDM
Dynamic Systems Development, DSDMDynamic Systems Development, DSDM
Dynamic Systems Development, DSDMJohn Goodpasture
 
Agile for project managers - A presentation for PMI
Agile for project managers  - A presentation for PMIAgile for project managers  - A presentation for PMI
Agile for project managers - A presentation for PMIJohn Goodpasture
 
Five risk management rules for the project manager
Five risk management rules for the project managerFive risk management rules for the project manager
Five risk management rules for the project managerJohn Goodpasture
 
Building Your Personal Brand
Building Your Personal BrandBuilding Your Personal Brand
Building Your Personal BrandJohn Goodpasture
 
Portfolio management and agile: a look at risk and value
Portfolio management and agile: a look at risk and valuePortfolio management and agile: a look at risk and value
Portfolio management and agile: a look at risk and valueJohn Goodpasture
 
Project examples for sampling and the law of large numbers
Project examples for sampling and the law of large numbersProject examples for sampling and the law of large numbers
Project examples for sampling and the law of large numbersJohn Goodpasture
 
Agile for project managers - a sailing analogy
Agile for project managers  - a sailing analogyAgile for project managers  - a sailing analogy
Agile for project managers - a sailing analogyJohn Goodpasture
 
Risk management with virtual teams
Risk management with virtual teamsRisk management with virtual teams
Risk management with virtual teamsJohn Goodpasture
 
Bayes Theorem and Inference Reasoning for Project Managers
Bayes Theorem and Inference Reasoning for Project ManagersBayes Theorem and Inference Reasoning for Project Managers
Bayes Theorem and Inference Reasoning for Project ManagersJohn Goodpasture
 
Adding quantitative risk analysis your Swiss Army Knife
Adding quantitative risk analysis your Swiss Army KnifeAdding quantitative risk analysis your Swiss Army Knife
Adding quantitative risk analysis your Swiss Army KnifeJohn Goodpasture
 
Business value and kano chart
Business value and kano chartBusiness value and kano chart
Business value and kano chartJohn Goodpasture
 
Agile for Business Analysts
Agile for Business AnalystsAgile for Business Analysts
Agile for Business AnalystsJohn Goodpasture
 

Mehr von John Goodpasture (20)

Five tools for managing projects
Five tools for managing projectsFive tools for managing projects
Five tools for managing projects
 
Risk management short course
Risk management short courseRisk management short course
Risk management short course
 
Agile in the waterfall
Agile in the waterfall Agile in the waterfall
Agile in the waterfall
 
RFP template
RFP templateRFP template
RFP template
 
Agile earned value exercise
Agile earned value exerciseAgile earned value exercise
Agile earned value exercise
 
Agile 103 - the three big questions
Agile 103  - the three big questionsAgile 103  - the three big questions
Agile 103 - the three big questions
 
Agile for project managers - a sailing analogy-UPDATE
Agile for project managers  - a sailing analogy-UPDATEAgile for project managers  - a sailing analogy-UPDATE
Agile for project managers - a sailing analogy-UPDATE
 
Feature driven design FDD
Feature driven design FDDFeature driven design FDD
Feature driven design FDD
 
Dynamic Systems Development, DSDM
Dynamic Systems Development, DSDMDynamic Systems Development, DSDM
Dynamic Systems Development, DSDM
 
Agile for project managers - A presentation for PMI
Agile for project managers  - A presentation for PMIAgile for project managers  - A presentation for PMI
Agile for project managers - A presentation for PMI
 
Five risk management rules for the project manager
Five risk management rules for the project managerFive risk management rules for the project manager
Five risk management rules for the project manager
 
Building Your Personal Brand
Building Your Personal BrandBuilding Your Personal Brand
Building Your Personal Brand
 
Portfolio management and agile: a look at risk and value
Portfolio management and agile: a look at risk and valuePortfolio management and agile: a look at risk and value
Portfolio management and agile: a look at risk and value
 
Project examples for sampling and the law of large numbers
Project examples for sampling and the law of large numbersProject examples for sampling and the law of large numbers
Project examples for sampling and the law of large numbers
 
Agile for project managers - a sailing analogy
Agile for project managers  - a sailing analogyAgile for project managers  - a sailing analogy
Agile for project managers - a sailing analogy
 
Risk management with virtual teams
Risk management with virtual teamsRisk management with virtual teams
Risk management with virtual teams
 
Bayes Theorem and Inference Reasoning for Project Managers
Bayes Theorem and Inference Reasoning for Project ManagersBayes Theorem and Inference Reasoning for Project Managers
Bayes Theorem and Inference Reasoning for Project Managers
 
Adding quantitative risk analysis your Swiss Army Knife
Adding quantitative risk analysis your Swiss Army KnifeAdding quantitative risk analysis your Swiss Army Knife
Adding quantitative risk analysis your Swiss Army Knife
 
Business value and kano chart
Business value and kano chartBusiness value and kano chart
Business value and kano chart
 
Agile for Business Analysts
Agile for Business AnalystsAgile for Business Analysts
Agile for Business Analysts
 

Kürzlich hochgeladen

Intellectual Property Licensing Examples
Intellectual Property Licensing ExamplesIntellectual Property Licensing Examples
Intellectual Property Licensing Examplesamberjiles31
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access
 
Anyhr.io | Presentation HR&Recruiting agency
Anyhr.io | Presentation HR&Recruiting agencyAnyhr.io | Presentation HR&Recruiting agency
Anyhr.io | Presentation HR&Recruiting agencyHanna Klim
 
Company Profile and SWOT Analysis Product List.pdf
Company Profile and SWOT Analysis Product List.pdfCompany Profile and SWOT Analysis Product List.pdf
Company Profile and SWOT Analysis Product List.pdfRobertPhillips265023
 
MC Heights construction company in Jhang
MC Heights construction company in JhangMC Heights construction company in Jhang
MC Heights construction company in Jhangmcgroupjeya
 
Entrepreneurship and individuals workshop
Entrepreneurship and individuals workshopEntrepreneurship and individuals workshop
Entrepreneurship and individuals workshopP&CO
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access
 
PDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfPDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfHajeJanKamps
 
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHelene Heckrotte
 
Six Sigma Improvement Process: Transforming Processes, Elevating Performance
Six Sigma Improvement Process: Transforming Processes, Elevating PerformanceSix Sigma Improvement Process: Transforming Processes, Elevating Performance
Six Sigma Improvement Process: Transforming Processes, Elevating PerformanceOperational Excellence Consulting
 
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdf
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdfTalent Management research intelligence_13 paradigm shifts_20 March 2024.pdf
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdfCharles Cotter, PhD
 
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלי
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלימיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלי
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגליBen Shushan & Co. C.P.A (Isr.)
 
Cracking the ‘Business Process Outsourcing’ Code Main.pptx
Cracking the ‘Business Process Outsourcing’ Code Main.pptxCracking the ‘Business Process Outsourcing’ Code Main.pptx
Cracking the ‘Business Process Outsourcing’ Code Main.pptxWorkforce Group
 
Human Resource Management Chapter 9: Performance Management and Appraisal
Human Resource Management Chapter 9: Performance Management and AppraisalHuman Resource Management Chapter 9: Performance Management and Appraisal
Human Resource Management Chapter 9: Performance Management and Appraisalgomezdominic3
 
Fabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsFabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsWristbands Ireland
 
To Create Your Own Wig Online To Create Your Own Wig Online
To Create Your Own Wig Online  To Create Your Own Wig OnlineTo Create Your Own Wig Online  To Create Your Own Wig Online
To Create Your Own Wig Online To Create Your Own Wig Onlinelng ths
 
7movierulz.uk
7movierulz.uk7movierulz.uk
7movierulz.ukaroemirsr
 

Kürzlich hochgeladen (20)

WAM Corporate Presentation Mar 25 2024.pdf
WAM Corporate Presentation Mar 25 2024.pdfWAM Corporate Presentation Mar 25 2024.pdf
WAM Corporate Presentation Mar 25 2024.pdf
 
Intellectual Property Licensing Examples
Intellectual Property Licensing ExamplesIntellectual Property Licensing Examples
Intellectual Property Licensing Examples
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024
 
Anyhr.io | Presentation HR&Recruiting agency
Anyhr.io | Presentation HR&Recruiting agencyAnyhr.io | Presentation HR&Recruiting agency
Anyhr.io | Presentation HR&Recruiting agency
 
Company Profile and SWOT Analysis Product List.pdf
Company Profile and SWOT Analysis Product List.pdfCompany Profile and SWOT Analysis Product List.pdf
Company Profile and SWOT Analysis Product List.pdf
 
MC Heights construction company in Jhang
MC Heights construction company in JhangMC Heights construction company in Jhang
MC Heights construction company in Jhang
 
Entrepreneurship and individuals workshop
Entrepreneurship and individuals workshopEntrepreneurship and individuals workshop
Entrepreneurship and individuals workshop
 
Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024Borderless Access - Global Panel book-unlock 2024
Borderless Access - Global Panel book-unlock 2024
 
PDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdfPDT 88 - 4 million seed - Seed - Protecto.pdf
PDT 88 - 4 million seed - Seed - Protecto.pdf
 
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptxHELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
HELENE HECKROTTE'S PROFESSIONAL PORTFOLIO.pptx
 
Six Sigma Improvement Process: Transforming Processes, Elevating Performance
Six Sigma Improvement Process: Transforming Processes, Elevating PerformanceSix Sigma Improvement Process: Transforming Processes, Elevating Performance
Six Sigma Improvement Process: Transforming Processes, Elevating Performance
 
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdf
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdfTalent Management research intelligence_13 paradigm shifts_20 March 2024.pdf
Talent Management research intelligence_13 paradigm shifts_20 March 2024.pdf
 
Sixth Sense Media Portfolio (Eng Ver) PDF
Sixth Sense Media Portfolio (Eng Ver) PDFSixth Sense Media Portfolio (Eng Ver) PDF
Sixth Sense Media Portfolio (Eng Ver) PDF
 
Deira Dubai Call Girls +971552825767 Call Girls In Downtown Dubai
Deira Dubai Call Girls +971552825767 Call Girls In Downtown DubaiDeira Dubai Call Girls +971552825767 Call Girls In Downtown Dubai
Deira Dubai Call Girls +971552825767 Call Girls In Downtown Dubai
 
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלי
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלימיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלי
מיסוי רילוקיישן לפורטוגל- היבטי מיסוי ישראלי ופורטוגלי
 
Cracking the ‘Business Process Outsourcing’ Code Main.pptx
Cracking the ‘Business Process Outsourcing’ Code Main.pptxCracking the ‘Business Process Outsourcing’ Code Main.pptx
Cracking the ‘Business Process Outsourcing’ Code Main.pptx
 
Human Resource Management Chapter 9: Performance Management and Appraisal
Human Resource Management Chapter 9: Performance Management and AppraisalHuman Resource Management Chapter 9: Performance Management and Appraisal
Human Resource Management Chapter 9: Performance Management and Appraisal
 
Fabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and FestivalsFabric RFID Wristbands in Ireland for Events and Festivals
Fabric RFID Wristbands in Ireland for Events and Festivals
 
To Create Your Own Wig Online To Create Your Own Wig Online
To Create Your Own Wig Online  To Create Your Own Wig OnlineTo Create Your Own Wig Online  To Create Your Own Wig Online
To Create Your Own Wig Online To Create Your Own Wig Online
 
7movierulz.uk
7movierulz.uk7movierulz.uk
7movierulz.uk
 

What is this thing called Agile?

  • 1. COVER STORY COVER STORY What is This Thing Called ‘Agile’? John C Goodpasture There are new and challenging ideas in project Dilbert: We need 3 more programmers. management, ideas Boss: Use agile programming methods. especially suited for Dilbert: Agile programming does not mean doing more work with less managing dynamically people. complex software projects — projects that put ever Boss: Find me some words that do mean that and ask again. increasing complexity in – Dilbert™ is a creation of Scott Adams the hands of users and consumers. ‘Agile’ is the A umbrella term for what gile means small teams, working collectively and we are talking about. In collaboratively, to deliver “frequent, incremental releases of this article, the author innovative functions and features, developed iteratively and explores the motivations by evolutionary builds, prioritized just-in-time for need and for the Agile Movement affordability, and produced at the best possible value”. and the advantages, agile Frequent, incremental releases mean that several times a year, as methods have for small often as the enterprise can absorb change, even every few weeks, an software projects. Agile is update to the product base is put into production. not a silver bullet, but it ‘Developed iteratively’, means that each build is the product of has the potential to be revisiting the development cycle repetitively, each cycle addressing very effective, when some subset of the requirements, and several such cycles making up requirements are dynamic, the release. ‘Evolutionary’ means that the product is not fully planned the customer has an in advance; the design features and functions emerge and become urgent need, and the defined during development cycles; and releases as users have a deadlines for value delivery chance to evaluate and critique the solution. are short. ‘Prioritized just-in-time for need and affordability’ means that the customer has a seat at the table, so as to speak. The customer is allowed to change requirements and set priorities at every release, although constrained within a limit of affordability, specified in the business plan. And ‘produced at the best possible value’ means that the customer will get a lot for the budget, but the scope may vary a bit from the vision described in the business plan. Requirements are never really frozen or baselined, so the final product may have features and functions, not originally envisioned. © 2009 John August 2009 C Goodpasture. All Rights Reserved. 31
  • 2. What is this Thing Called 'Agile'? About the Author John C Goodpasture, PMP, is a Program Manager, Coach, Author, and Project Consultant specializing in technology projects, strategic planning, project office operations. He is authoring a book on Agile Project Management that is anticipated for publication at the end of 2009. He blogs at johngoodpasture.blogspot.com. The author can be reached at www. sqpegconsulting.com Many Methodologies Called Agile The methodologies included under the agile umbrella go by many names: SCRUM, XP, CRYSTAL Family, EVO, and DSDM.1 And, the others are: Feature-driven Design, Adaptive Software Development, Lean Development, Team Software Process (TSP) and Personal Software Process (PSP).2 All embrace the Agile Manifesto and the Agile Principles supported by the Agile Alliance.3 Before these, there were others that had a longer legacy and had set the stage: Spiral, RUP, JAD, and RAD, to name a few.4 Each in its own way, address the ever-present dilemma in user-dominated software, to wit: what the customer says they need and want, is constantly uncertain and often unaffordable, sometimes not even feasible. Indeed, like the classic case of the ‘wicked problem’, the ‘solution often defines the requirements’ – “I’ll know it when I see it”!5 What agile methods do is, empower small teams to rapidly respond to a changing landscape and deliver customer value quickly, well within the longer cycles of business and markets. Agile teams work in small chunks of scope that can be stabilized over relatively short periods, consulting customers and users as the solution emerges, releasing product increments frequently, and then inviting serious critique after every release. Not Plan-Driven Agile is the antithesis of the plan-driven methods, the main example of many years being the waterfall method, but more recently ISO 12207, CMM (I),6 Prince 2, and high reliability methods like Clean Room.7 Unquestionably, plan-driven methodologies have their place. When the requirements are safety-critical, mission-critical, high reliability, or security critical, the careful structured analysis of requirements accompanied by strict governance is mandated. To say agile methods are not plan-driven does not mean that agile projects are not planned – they are, but more just-in-time, than the plan-driven sequential methodologies. The top-level agile plan is in the business case. Detail plans are made by teams as work begins. 1 XP is the acronym for ‘extreme programing’. EVO stands for the Evolutionary methodology. DSDM is Dynamic Systems Development Method. 2 PSP and TSP are service marks of Carnegie Mellon University. 3 See http://www.agilealliance.com and http://www.agilemanifesto.org/ 4 Acronyms in this list are RUP for Rational Unified Process, a product of IBM/Rational, RAD for rapid application development, JAD for joint application development. 5 The so-called ‘wicked problem’ is a class of problems that are somewhat circular and for which, the requirements cannot be stated, until the solution is in place. These problems are often political, sometimes subjectively social, and other times technical. There is a body of knowledge around solving wicked problems. See my blog at johngoodpasture.blogspot.com for more information. 6 CMM (I) is Capability Maturity Model – Integration that puts together software engineering, system engineering, and product integration in a coordinated set of practices. CMM (I) is a service mark of Carnegie Mellon University. 7 TSP, Team Software Process, PSP, Personal Software Process are service marks of Carnegie Mellon University. 32 Projects and Profits
  • 3. COVER STORY Do These Methods Work? The quick-read bottom line on agile methods is that they do work, they do shorten the schedule, and they do provide a very high quality product (Table 1).8 However, agile is not a silver bullet; it is not appropriate in all situations, and only works, if the proper environment and management mind-set are provided to the project. Table 1: Agile Methodologies • Agile methodologies depart in significant ways from traditional project protocols. • They are most applicable, when requirements are changing, unknown, or unknowable. • They work best in project situations of less than a handful of small teams, typically fewer than 50 developers. • They work better in-house than through the constraint of a contract; they work better co-located than though the cultural translation of a virtual team. • Process-centric methods are better for safety-critical and high-reliability programs. Project managers should look seriously at what is happening here. The troublesome shortfalls in performance and customer value, made all the more acute by the rapid business cycles in the web era, caused some industry innovators to look at the whole thing in an entirely different way. From the product development community, the software engineering community, and the system engineering community, truly innovative protocols have been devised and put into practice. These procedures, not only apply project talent differently, but also reorder the intuitive sequence of project events that has been the mainstay for generations. The Agile Project Life Cycle Agile methods are the antithesis of what program and project managers know as the Plan-Driven Project Development Life Cycle (PD-PDLC) (Table 2). The PD-PDLC is sequential, beginning with gathering requirements and ending with delivering products. Plan-driven methods are characterized by the Big Design Up Front (BDUF). The Agile PDLC, Ag-PDLC, is entirely different, as shown in Table 2. Table 2: The Agile PDLC, Ag-PDLC • Outcomes are incrementally planned and specified, built iteratively, and delivered in frequent releases of limited but valuable capabilities. • Agile projects are governed by a top level business plan that envisions a product goal, business milestones, and a level of affordability. • Scope and quality, the budget, and the schedule are framed in the business plan but the details emerge as the project progresses. • Value is earned incrementally as outcomes are committed to production. • Customers are allowed to change their mind from one release to the next in order to keep the value proposition ever in alignment with business and market realities. 8 For some metric information on the track record of agile projects, see Appendix E, Empirical Information in: Boehm B and Turner R (2004), Balancing Agility and Discipline, Appendix E, Addison-Wesley, New York. August 2009 33
  • 4. What is this Thing Called 'Agile'? The Ag-PDLC has four distinguishing characteristics that set it apart from the PD-PDLC: 1. Emergent The processes and procedures used by the implementation teams emerge from the team’s analysis of the requirements and tasks. In effect, teams adapt; process control is achieved empirically by observation and reaction, not by defined capabilities with error bounds, as in Six Sigma.9 2. Iterative The PDLC is a string of iterations in which, a backlog of requirements is burned-down one iteration at a time, until exhausted. 3. Evolutionary The product details adapt to the customer needs and wants. The customer is allowed to reset priorities, add, delete, and change the backlog, according to market and business need. 4. Incremental The outcomes of iterations are packaged for release to production as an increment to the product base. Note: It takes a combination of the incremental and the evolutionary to really be agile. Some PD- PDLCs are incremental, but not evolutionary. To maintain alignment of deliveries with the value proposition in the business case, iterations are relatively short, from about 2-3 weeks in the XP methodology, 30 days in SCRUM, to something longer, according to circumstances in Crystal and EVO. Releases are made as frequently as the business can absorb change, but typically, no less frequently than a calendar quarter. There are no hard and fast rules; each project sets the agenda with the customer. A Process of Cycles All agile methodologies are about responsiveness, exercised iteratively. All methods embrace the concept of repeating nested cycles, although the terminology varies from one method to the next. The building block is the standard day, ideally an eight hour stint of value-added activity. Each day begins with a team review that is time-boxed – that is, limited to a fixed time duration – followed by development activity, inspection, and ideally ending with the day’s outcome integrated into the product base. Iterations are built up of days. In SCRUM, the iteration is called a sprint; in EVO it is a delivery cycle. An iteration is a time-boxed duration of a few weeks at most, during which, a selected backlog of requirements is developed. The requirements are made stable during the iteration. The change to the product base at the end of the iteration is a product increment. Iterations, one or more, build up a release event. A release is a product increment going into production operations for internal or external use. 9 Six Sigma is a quality management process in which, a problem analysis protocol is followed by solutions that implement error control within approximately three parts in a million. Errors are sensed and corrective information is fed back to bring the process within the Six Sigma boundaries. Defined process control is a concept of manufacturing, promoted strongly by the work of W. Edwards Deming and others in the post World War II era. It presumes definable error limits that are acceptable in the finished product, means to measure, and means to correct. See Schawber K (2004), Agile Project Management with SCRUM, pp. 2-4, Microsoft Press, Redmond, WA. 34 Projects and Profits
  • 5. COVER STORY Plans are made around rolling waves.10 A wave is a planning horizon, consisting of one or more releases. The planning horizon, typically not more than a few months, is the distance we can see ahead with reasonable project level vision. Waves are synchronized with business cycles. The normal business cycles are quarterly, annual, and multi-year, to correspond to tactical results, annual results, and strategic planning, respectively. Agile Teams Agile teams are small, self-organized units that are multifunctional and internally redundant. Teams stay together for the life of the project. In general, teams do not handover their outcomes to other teams. The outcomes of each team are integrated into production at each release. Teams are coached by the project manager but otherwise organize themselves for the daily work cycle. The work ethic of teams is collaborative in a manner that each member is assisted by others. In the XP methodology, members program in pairs. Each member is committed and accountable for his own work and the success of the team. Projects scale up by adding The value of agile methods is the teams. A coordinating body of team leaders meets daily success that meets frequent, to coordinate team work. incrementally delivered features and Communications within teams is by face-to-face functions, even in the swirl of discussions and documentation outside of coding complex and uncertain requirements comments is minimized. In a practice called Test- Driven-Design, XP methodologists document requirements by using test scripts. If virtual teams are employed, a special effort is made to reduce communications friction, so that an efficient daily cycle is maintained. Conclusion The value of agile methods is the success that meets frequent, incrementally delivered features and functions, even in the swirl of complex and uncertain requirements. Plan-driven methods have their place, particularly on projects of high scale, safety-critical requirements, mission-critical objectives, and many contract situations. However, they are decidedly not appropriate in a dynamic requirement environment, not appropriate to fast and incremental delivery, and are very cost inefficient on smaller projects. The sweet spot for agile projects is teams of less than 50 developers, where there is high value placed collaborative work ethics and personal commitment and accountability for success. At the end of the day, we say that agile is: Small teams, working collectively and collaboratively, with this mission: To deliver “frequent, incremental releases of innovative functions and features, developed iteratively and by evolutionary builds, prioritized just-in-time for need and affordability, and produced at the best possible value”. Reference # 17M-2009-08-06-01 10 Goodpasture J (2007), “A Risk Perspective: Rolling Wave Planning is a Bet”, Projects and Profits, December, pp. 48-53. August 2009 35