Agile Software Development from Wikipedia, the Free Encyclopedia It Has Been Suggested That Agile Management Be Merged Into This Article
Total Page：16
File Type：pdf, Size：1020Kb
Agile software development From Wikipedia, the free encyclopedia It has been suggested that Agile management be merged into this article. (Discuss) Proposed since November 2014. Software development process Core activities Requirements Design Construction Testing Debugging Deployment Maintenance Methodologies Waterfall Prototype model Incremental Iterative V-Model Spiral Scrum Cleanroom RAD DSDM UP XP Agile Lean Dual Vee Model TDD BDD FDD DDD MDD Supporting disciplines Configuration management Documentation Software Quality assurance (SQA) Project management User experience Tools Compiler Debugger Profiler GUI designer Modeling IDE Build automation V T E Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement and encourages rapid and flexible response to change. The Agile Manifesto,[1] which first laid out the underlying concepts of Agile development, introduced the term in 2001. Contents [hide] 1 History o 1.1 Predecessors o 1.2 The Agile Manifesto . 1.2.1 Agile principles o 1.3 Evolutions 2 Overview 3 Philosophy o 3.1 Adaptive vs. predictive o 3.2 Iterative vs. Waterfall o 3.3 Code vs. documentation 4 Agile methods o 4.1 Agile practices o 4.2 Method tailoring o 4.3 Comparison with other methods 5 Measuring agility 6 Experience and adoption o 6.1 Surveys o 6.2 Large-scale and distributed Agile o 6.3 Common Agile Pitfalls 7 Criticism 8 Applications Outside of Software Development 9 References 10 Further reading 11 External links History[edit] Predecessors[edit] Incremental software development methods have been traced back to 1957.[2] In 1974, a paper by E. A. Edmonds introduced an adaptive software development process.[3] [4]Concurrently and independently, the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan. In the early 1970s, Tom Gilb started publishing the concepts of Evolutionary Project Management (EVO), which has evolved into Competitive Engineering.[5] During the mid- to late 1970s, Gielan lectured extensively throughout the U.S. on this methodology, its practices, and its benefits. So-called lightweight agile software development methods evolved in the mid-1990s in reaction to the heavyweight waterfall-oriented methods, which critics called heavily regulated, regimented, micromanaged and over-incremental. Proponents of lightweight agile methods contend that they are returning to development practices that were present early in the history of software.[2] Early implementations of agile methods include Rational Unified Process (1994), Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development,Feature Driven Development (1997), and Dynamic Systems Development Method (DSDM) (1995). These are now collectively referred to as agile methodologies, after the Agile Manifesto was published in 2001.[6] The Agile Manifesto[edit] In February 2001, 17 software developers (see below) met at the Snowbird resort in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development:[1] We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan [1] That is, while there is value in the items on the right, we value the items on the left more. Kent Beck James Grenning Robert C. Martin Mike Beedle Jim Highsmith Steve Mellor Arie van Bennekum Andrew Hunt Ken Schwaber Alistair Cockburn Ron Jeffries Jeff Sutherland Ward Cunningham Jon Kern Dave Thomas Martin Fowler Brian Marick © 2001, the above authors. This declaration may be freely copied in any form, but only in its entirety through this notice. The meanings of the manifesto items on the left within the agile software development context are: Individuals and interactions: in agile development, self-organization and motivation are important, as are interactions like co-location and pair programming. Working software: working software will be more useful and welcome than just presenting documents to clients in meetings. Customer collaboration: requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important. Responding to change: agile development is focused on quick responses to change and continuous development.[7] Some of the authors formed the Agile Alliance, a non-profit organization that promotes software development according to the manifesto's values and principles. Introducing the manifesto on behalf of the Agile Alliance, Jim Highsmith said, The Agile movement is not anti-methodology, in fact many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Those who would brand proponents of XP or SCRUM or any of the other Agile Methodologies as "hackers" are ignorant of both the methodologies and the original definition of the term hacker. —Jim Highsmith, History: The Agile Manifesto[8] Agile principles[edit] The Agile Manifesto is based on 12 principles:[9] 1. Customer satisfaction by rapid delivery of useful software 2. Welcome changing requirements, even late in development 3. Working software is delivered frequently (weeks rather than months) 4. Close, daily cooperation between business people and developers 5. Projects are built around motivated individuals, who should be trusted 6. Face-to-face conversation is the best form of communication (co-location) 7. Working software is the principal measure of progress 8. Sustainable development, able to maintain a constant pace 9. Continuous attention to technical excellence and good design 10. Simplicity—the art of maximizing the amount of work not done—is essential 11. Self-organizing teams 12. Regular adaptation to changing circumstances Evolutions[edit] Later, Ken Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Schwaber left the Scrum Alliance in the fall of 2009, and founded Scrum.org. In 2005, a group headed by Alistair Cockburn and Jim Highsmith wrote an addendum of project management principles, the Declaration of Interdependence,[10] to guide software project management according to agile development methods. In 2009, a movement spearheaded by Robert C Martin wrote an extension of software development principles, the Software Craftsmanship Manifesto, to guide agile software development according to professional conduct and mastery. Overview[edit] This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (December 2012) Pair programming, an agile development technique used by XP. Note information radiators in the background. There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project. Iterative, incremental and evolutionary Most agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a cross-functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration.[11] Multiple iterations might be required to release a product or new features. Efficient and face-to-face communication No matter what development disciplines are required, each agile team will contain a customer representative, e.g. Product Owner in Scrum. This person is appointed by stakeholders to act on their behalf[12] and makes a personal commitment to being available for developers to answer mid- iteration questions. At the end of each iteration, stakeholders and the customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment (ROI) and ensuring alignment with customer needs and company goals. In agile software development, an information radiator is a (normally large) physical display located prominently in an office, where passers-by can see it. It presents an up-to-date summary of the status of a software project or other product.[13][14] The name was coined by Alistair Cockburn, and described in his 2002 book Agile Software Development.[14] A build light indicator may be used to inform a team about the current status of their project. Very short feedback loop and adaptation