CSC/ECE 517 Fall 2011/ch5 6d ny

Agile Landscape

Introduction<ref>http://www.vtt.fi/inf/pdf/publications/2002/P478.pdf</ref>

Agile- denoting “the quality of being agile; readiness for motion; nimbleness, activity, dexterity in motion ” is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It is a framework or frame of mind. A practitioner of Agile can use different methodologies within the framework to “do or be” Agile. Agile is our guiding principles that lay the foundation for building better software. In layman language, Agile methodology means cutting down the big picture into puzzle size bits, fitting them together when the time is right e.g. design, coding and testing bits. So, while there are reasons to support both the waterfall and agile methods, reasons such as better adaption of change, launchable product at the end of each cycle, usage of object oriented paradigms, emphasis on user requirements followed by the latter clarifies why many software and web design firms make the more appropriate choice of employing Agile methodology.

The term “Agile Software Development” was introduced in 2001 by Agile Software Development Manifesto published by a group of software practitioners and consultants. The important aspects of this Manifesto are,

• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaborations over contract negotiation.
• Responding to change over following plan.

Life Cycle<ref>http://www.techjini.com/ourapproach-methodologies.html </ref>

Agile Development Life cycle

Agile Software development processes are based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.Agile processes use feedback,rather than planning, as their primary control mechanism. The feedback is driven by regular tests and releases of the evolving software.

Process

Agile development involves the following steps:

Project Initiation:Set up and justify the project. Determine initial high level requirements.

Project Plan: Plan out the project, everything after Project Initiation, including whether you're going to have the optional phases.

Elaborate Requirements (optional): Very high level requirements are gathered during Project Initiation. These can optionally be expanded during an phase to Elaborate Requirements. Even is the requirements are "elaborated" they are still high level.

Architecture (optional): The Agile approach is generally design for today and refactor tomorrow (at least in XP)..

Release:A Release is a piece of development where the customer gets some new software. Releases can be from 2 weeks to 6 months, but are usually 3 months long. Release have one or more timeboxes.

Time box:A Timebox is 1 – 6 weeks long, but usually 3 – 4 weeks. The most important thing about a timebox is that the delivery date is fixed.

Various kinds of agile techniques

• Extreme Programming(XP)
• Scrum
• Crystal family of Methodologies
• Feature Driven Development
• Rational Unified Process
• Dynamic Systems Development
• Adaptive Software Development
• Open Source Software Development
• Agile Modelling
• Pragmatic Programming

Different Methodologies<ref>http://www.versionone.com/Agile101/Methodologies.asp </ref>

Extreme Programming

ExtremeProgramming is one of many AgileProcesses. It is also known as XP. XP is a disciplined approach to delivering high-quality software quickly and continuously.Extreme Programming(XP) has evolved from the problems caused by long development cycles of traditional development models; it appears to be based on trial and error programming!. It is first started as ‘simply an opportunity to get the job done’ with practices that had been found effective in software development process.

Life cycle<ref>http://www.rajeevmisra.com/software/extreme-programming/ </ref>

The Extreme Programming life cycle consists of the following phases,

• Exploration Phase: In this phase the team performs an architectural spike, during which they experiment with the features to envision the initial architecture.
• Planning Phase: This phase focuses primarily on identifying the most critical user stories and estimating the time required to implement it. A release will have one to many iterations, which are typically 2-to-4 weeks .
• Iteration phase: During this phase; development iteration phase involves iterative testing of the latest versions and eliminating the bugs based on the customer feedback.
• Productionizing Phase: During this phase the code is certified for releases based on the customer approval.

Values

Extreme Programming improves a software project in five essential ways;

• Communication: Extreme Programmers constantly communicate with their customers and fellow programmers
• Simplicity: They keep their design simple and clean.Thereby Teams perform the minimum work needed to meet requirements.
• Feedback: They get feedback by testing their software starting on day one.
• Respect: They deliver the system to the customers as early as possible and implement changes as suggested
• Courage: Every small success deepens their respect for the unique contributions of each and every team member. With this foundation Extreme Programmers are able to courageously respond to changing requirements and technology.

Advantages

• It is more Customer-focused (it’s all about user stories)
• It ensures Quality via frequent testing
• Constant focus on identifying and delivering the critical user stories
• It results in High visibility on project status
• It provides great support for volatile requirements

Disadvantages

Although XP methodology can result in an improved process which is more efficient more predictable more flexible ,it also has weaknesses such as:

• Difficulty coordinating larger teams
• Can result in a never-ending project if not managed properly
• Tendency to not document thoroughly
• Predicting the precise features to be accomplished in a fixed time/budget

Scrum

Scrum Development is a lightweight management framework with broad applicability for managing and controlling iterative and incremental projects of all types. Ken Schwaber, Mike Beedle, Jeff Sutherland and others have contributed significantly to the evolution of Scrum over the last decade. Over the last couple of years in particular, Scrum has garnered increasing popularity in the software community due to its simplicity, proven productivity, and ability to act as a wrapper for various engineering practices promoted by other agile methodologies.

Life Cycle <ref>http://planmanup.blogspot.com/2010/08/software-development-methodology.html</ref>

Agile Scrum Life Cycle

Characteristics:

Scrum is a process skeleton that contains sets of practices and predefined roles. The main roles in Scrum are:

1.the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager.

2.the “Product Owner”, who represents the stakeholders and the business.

3.the “Team”, a cross-functional group who do the actual analysis, design, implementation, testing, etc.

Advantages

• It helps in saving time and money.
• Fast moving, cutting edge developments can be quickly coded and tested as the bugs can be easily fixed.
• Short sprints and constant feedbacks results in easier way to cope with the changes.
• Daily meeting helps in evaluating individual productivity. Thereby enhances the productivity of each of the team members.
• It is easier to deliver a quality product in a scheduled time.

Disadvantages

• Decision-making is entirely in the hands of the teams. And if the team members are not committed, the project will either never complete or fail.
• It is good for small, fast moving projects as it works well only with small team.
• Absence of any of the team member during development can have huge inverse effect on the project development.

Crystal family of Methodologies<ref>http://altnetpedia.com/Crystal.ashx </ref>

Crystal methods are considered and described as “lightweight methodologies”. The Crystal family of methodologies views software development as a "cooperative game of invention and communication, with a primary goal of delivering working useful software and a secondary goal of setting up the next game". Crystal promotes early, frequent delivery of working software, high user involvement, adaptability, and the removal of bureaucracy or distractions. Alistair Cockburn, the originator of Crystal, has released a book, “Crystal Clear: A Human-Powered Methodology for Small Teams”.

Crystal Family

Crystal is actually comprised of a family of methodologies,whose unique characteristics are driven by several factors such as team size, system criticality, and project priorities. And they are,

• Crystal Clear
• Crystal Yellow
• Crystal Orange
• Crystal Orange Web
• Crystal Red
• Crystal Maroon
• Crystal Diamond
• Crystal Sapphire

Crystal Clear is the lightest methodology in the family, suitable for co-located teams of up to 10 people. It is a lower-discipline methodology than XP (1st edition) but also requires some documentation.This Crystal family addresses the realization that each project may require a slightly tailored set of policies, practices, and processes in order to meet the project’s unique

Characteristics

Crystal has seven core properties:

• Frequent Delivery
• Reflective Improvement
• Osmotic Communication
• Personal Safety
• Focus
• Expert Users
• Automated Tests
• Configuration Management
• Frequent Integration.

Feature Driven Development<ref>http://questpond.blog.com/2010/11/16/agile-development-part-2-2/ </ref>

Feature Driven Development is a model-driven, short-iteration process . It is one of a number of Agile methodsfor developing software and forms part of the Agile Alliance. FDD was originally developed and articulated by Jeff De Luca, with contributions by M.A. Rajashima, Lim Bak Wee, Paul Szego, Jon Kern and Stephen Palmer. The first incarnations of FDD occured as a result of collaboration between De Luca and OOD thought leader Peter Coad. It begins with establishing an overall model shape. Then it continues with a series of two-week "design by feature, build by feature" iterations. The features are small, "useful in the eyes of the client" results. FDD designs the rest of the development process around feature delivery using its best eight practices.

FDD Life cycle

Life cycle

A typical life cycle of a Feature Driven Development can be represented as in the diagram.

Characteristics

The eight bets practices of FDD are as follows,

• Domain Object Modeling
• Developing by Feature
• Component/Class Ownership
• Feature Teams
• Inspections
• Configuration Management
• Regular Builds
• Visibility of progress and results

FDD recommends specific programmer practices such as "Regular Builds" and "Component/Class Ownership". FDD's proponents claim that it scales more straightforwardly than other approaches, and is better suited to larger teams. Unlike other agile approaches, FDD describes specific, very short phases of work which are to be accomplished separately per feature. These inc

Advantages

• As FDD involves in development of an already thought of an product , rather than examining the market and seeing what the consumer could benefit from.
• By using FDD the business sticks solely to what they are good at; they develop goods that fall under an area that they have both experience and knowledge in, creating something that should be, by all accounts, one of the best in its field.
• The smaller companies benefit a lot by employing this methodology as they dont have to spend money of technical manpower.

Disadvanatages

• There may be no demand for your product, hence the business will struggle to make money.
• It requires a lot of background research on market product before developing.

Adaptive Software Development<ref>http://www.adaptivesd.com/articles/messy.htm </ref>

Adaptive Software Development is a software development process that grew out of rapid application development work by Jim Highsmith and Sam Bayer.ASD focuses mainly on the problems in developing complex,large systems. ASD embodies the principle that continuous adaptation of the process to the work at hand is the normal state of affairs. ASD eveolved as the software developer started to revise their management practices. ASD replaces the traditional waterfall cycle with a repeating series of speculate, collaborate, and learn cycles.

Life Cycle

• Speculate:

In complex environments, planning is a paradox. "Planning," whether it is applied to overall product specifications or detail project management tasks, is too deterministic a word. It carries too much historical baggage. "Speculate" is offered as a replacement. When we speculate, it's not that we don't define a mission to the best of our ability. So let's be honest, postulate a general idea of where we are going, and put mechanisms in place to adapt

• Collaborate:

Managing in a complex environment is scary as hell -- it is also a blast. If we can't predict (plan), then we can't control in the traditional management sense. If we can't control, then a significant set of current management practices is no longer operable, or more specifically, only operable for those parts of the development process that are predictable. Collaboration, in this context, portrays a balance between managing the doing (the main thrust of traditional management) and creating and maintaining the collaborative environment needed for emergence. As projects become increasingly complex, the balance swings much more toward the latter.

• Learn:

Collaborative activities build products. Learning activities expose those products to a variety of stakeholders to ascertain value. Customer focus groups, technical reviews, beta testing, and postmortems are all practices that expose results to scrutiny.

Dynamic Systems Development

Dynamic Systems Development Model, dating back to 1994, grew out of the need to provide an industry standard project delivery framework for what was referred to as Rapid Application Development (RAD) at the time. While RAD was extremely popular in the early 1990’s, the RAD approach to software delivery evolved in a fairly unstructured manner. As a result, the DSDM Consortium was created and convened in 1994 with the goal of devising and promoting a common industry framework for rapid software delivery. Since 1994, the DSDM methodology has evolved and matured to provide a comprehensive foundation for planning, managing, executing, and scaling Agile and iterative software development projects.

DSDM Life cycle

Life Cycle

The diagram depicts the life cycle of the DSDM Methodology as shown.

Characteristics

DSDM is based on nine key principles that primarily revolve around business needs/value, active user involvement, empowered teams, frequent delivery, integrated testing, and stakeholder collaboration. DSDM specifically calls out “fitness for business purpose” as the primary criteria for delivery and acceptance of a system, focusing on the useful 80% of the system that can be deployed in 20% of the time. Requirements are baselined at a high level early in the project. Rework is built into the process, and all development changes must be reversible. Requirements are planned and delivered in short, fixed-length time-boxes, also referred to as iterations, and requirements for DSDM projects are prioritized using MoSCoW Rules:

M – Must have requirements

S – Should have if at all possible

C – Could have but not critical

W - Won’t have this time, but potentially later

All critical work must be completed in a DSDM project. It is also important that not every requirement in a project or time-box is considered critical. Within each time-box, less critical items are included so that if necessary, they can be removed to keep from impacting higher priority requirements on the schedule.The DSDM project framework is independent of, and can be implemented in conjunction with, other iterative methodologies such as Extreme Programming and the Rational Unified Process.

Other Methodologies

Rational Unified Process

Rational Unified Processwas developed by Philippe Kruchten,Ivar Jacobsen and others at Rational Corporation to complement UML(Unified Modelling language),an industry-standard software modeling method.

RUP is an iterative approach for object-orieneted systems, and it strongly embraces use cases for modeling requirements and building the foundation for a system.RUP is inclined towards object-oriented development. The lifespan of a RUP project is divided into four phases named Inception,Elaboration,Construction and Transition.These phases are split into iterations,each having a purpose of producing a demonstrable piece of software.The duration of an iteration may vary from two weeks or less up to six months.

Open Source Software Development

Open source software development is the process by which open source software (or similar software whose source code is publicly available) is developed. These are software products “available with its [source code and under an open source license to study, change, and improve its design”. Examples of popular open source software products are Mozilla Firefox, Google Chrome etc..

OSS in many ways follows the same lines of thought and practices as other agile methods. For example, the OSS development process starts with early and frequent releases, and it lacks many of the traditional mechanisms used for coordinating software development with plans, system level designs and defined process.

Typically, an OSS project consists of the following visible phases:

• Problem discovery
• Finding volunteers
• Solution identification
• Code development and testing
• Code change review
• Code commit and documentation
• Release management

Agile Modelling

Agile Modeling is a practice-based methodology for modeling and documentation of software-based systems. It is intended to be a collection of values, principles, and practices for Modeling software that can be applied on a software development project in a more flexible manner than traditional Modeling methods. Agile Modeling is a supplement to other Agile methodologies such as:

Extreme Programming

Rational Unified Process

Scrum

Comparision

How widely these methodologies are used<ref>http://www.forrester.com/imagesV2/uplmisc/NN_AppDev2.pdf </ref>

Agile project management has entered the mainstream – incremental delivery is now common and (should be) expected for any new software development project. But,it still is in its naive stages in terms of the acceptance of the evolution in ideology that it demands.

For small scale projects, averages of 58% of agile techniques are used when developing software. So for example if the respondent was using XP on a small scale project, 7 out of 12 XP techniques would be followed while the other 5 would either be changed or ignored to fit the project constraints and needs. Fewer respondents are following agile techniques for medium and large scale projects, as trends show that weighted average of 34% and 22% respectively of the techniques were implemented in the projects. As the development of software increases, there is a corresponding decrease in the number of agile techniques used. Furthermore, respondents tend to use heavyweight methods when the increase of project size, complexity, team, architecture, scope, and risks occur.

Forrester’s Business Technographics® September 2006 North American And European Enterprise Software Survey indicates that 17% of North American and European enterprises currently use Agile processes and that another 29% are aware of them.Forrester believes that Agile adoption is actually higher than reported in this study. Based on the interactions with enterprise IT organizations, Forrester estimates that very few large enterprises use Agile for most of their projects.

A recent survey conducted by Dr. Dobb’s Journal shows 41 percent of development projects have now adopted agile methodology, and agile techniques are being used on 65 percent of such projects.This is shown in the diagram.

In retrospect,when is agile method not adopted? It primarily comes down to the people. If the people involved aren't interested in the kind of intense collaboration that agile working requires, then it's going to be a big struggle to get them to work with it. Thus, agile cannot be imposed onto people.

Evidence to support the effectiveness of Agile Development<ref>http://www.agilemodeling.com/essays/proof.htm </ref>

Adopting and then tailoring a software process to meet your team’s needs is an important and difficult decision, one that is critical to your project’s success. There are a myriad of choices. So it is important to determine whether an agile development methodology works effectively within your environment. There is growing survey evidence that agile works better than traditional.One of them is summarized in Figure 2.

Above is the DDJ 2007 Project Success Survey that showed that when people define success in their own terms, Agile projects had a 72% success rate, compared with 63% for traditional and 43% for offshoring.

Craig Larman,in his book Agile and Iterative Development: A Manager's Guide makes a very good argument that proof exists that shows that many of the common practices within agile software development do in fact work, practices such as incremental delivery and iterative approaches which embrace change. He also cites evidence which shows that serial approaches to development, larger projects, and longer release cycles lead to greater incidences project failure.

Effectiveness of agile methodology can be proved with feedback cycle which indicated the time in which response is obtained. Agile techniques are found to have very short feedback cycles, often on the order of minutes or hours whereas traditional techniques, such as reviews, inspections, and big requirements up front (BRUF) have feedback cycles on the order of weeks or months, making them riskier and on average more expensive.

From the surveys and the present organizational scenario, people's experience with agile software development can be observed to be very positive, and that adopting agile strategies appears to be very low-risk in practice.

Conclusion

To conclude, agile software development stresses rapid iterations, small and frequent releases, and evolving requirements facilitated by direct user involvement in the development process. This development isn’t managerial free-for-all. It requires discipline and adherence to processes, even when those processes are not burdensome. When it comes to methodologies, each project is differentand and there is no one-size-fits-all solution. Agile development is being adopted in the enterprise world widely and it is not long before agile would be part of the thinking process rather than a strategy.

See also

• Agile Software Development

• Waterfall cycle

• Agile Software Development Manifesto

• ExtremeProgramming

• Scrum Development

• Feature Driven Development

• Adaptive Software Development

• Dynamic Systems Development Model

• Rational Unified Process

• Open source software development

• Agile Modeling

External Links

• Extreme Programming

References

<references/>