Agile Development

By: WAJAHAT ALI

Sequence
What is Agile Development
Agile SDLC
The Agile Unified Process (AUP)
Agile Up Phases
Agile Up Disciplines
Incremental releases over time
Improve Productivity
Philosophies of the AUP
Conclusion
What is Agile Software Development?
An iterative and incremental (evolutionary)
approach to software development which is
performed in a highly collaborative manner by
self-organizing teams within an effective
framework that produces high quality software in
a cost effective and timely manner  which meets
the changing needs of its stakeholders.
Detailed Agile SDLC
Improve Productivity
The approach applies agile techniques include
Test Driven Development (TDD)
Model Driven Development (MDD)
Agile Change Management, and
Database Refactoring
to improve your productivity.
The Agile Unified Process (AUP)
The Agile Unified Process (AUP)
Agile Up Phases
The serial nature of Agile UP is captured in its four phases :
Inception. The goal is to identify the initial scope of the
project, a potential architecture for your system, and to
obtain initial project funding and stakeholder acceptance.
Elaboration.  The goal is to prove the architecture of the
system.
Construction.  The goal is to build working software on a
regular, incremental basis which meets the highest-priority
needs of your project stakeholders.
Transition.  The goal is to validate and deploy your system
into your production environment.
Agile Up Disciplines
Disciplines are performed in an iterative manner, defining the activities which development team members perform
to build, validate, and deliver working software which meets the needs of their stakeholders. The disciplines are:
Model.  The goal of this discipline is to understand the business of the organization, the problem domain being
addressed by the project, and to identify a viable solution to address the problem domain.
Implementation.  The goal of this discipline is to transform your model(s) into executable code and to perform a
basic level of testing, in particular unit testing.
Test.  The goal of this discipline is to perform an objective evaluation to ensure quality. This includes finding
defects, validating that the system works as designed, and verifying that the requirements are met.
Deployment.  The goal of this discipline is to plan for the delivery of the system and to execute the plan to make
the system available to end users.
Configuration Management.  The goal of this discipline is to manage access to your project artifacts. This
includes not only tracking artifact versions over time but also controlling and managing changes to them.
Project Management.  The goal of this discipline is to direct the activities that takes place on the project. This
includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people
and systems outside the scope of the project to be sure that it is delivered on time and within budget.
Environment. The goal of this discipline is to support the rest of the effort by ensuring that the proper process,
guidance (standards and guidelines), and tools (hardware, software, etc.) are available for the team as needed.
Incremental releases over time
Philosophies of the AUP
Your staff knows what they're doing.  People aren't going to read detailed process
documentation, but they will want some high-level guidance and/or training from
time to time.  The AUP product provides links to many of the details, if you're
interested, but doesn't force them upon you.
Simplicity.  Everything is described concisely using a handful of pages, not thousands
of them.
Agility.  The Agile UP conforms to the values and principles of the Agile Alliance.
Focus on high-value activities.  The focus is on the activities which actually count,
not every possible thing that could happen to you on a project.
Tool independence.  You can use any toolset that you want with the Agile UP.  My
suggestion is that you use the tools which are best suited for the job, which are often
simple tools or even open source tools.

You'll want to tailor this product to meet your own needs.  The AUP product is
easily tailorable via any common HTML editing tool.  You don't need to purchase a
special tool, or take a course, to tailor the AUP.
Conclusion
Active Stakeholder Participation
Agile Model Driven Development (AMDD)
Big Design Up Front (BDUF)
Big Requirements Up Front (BRUF)
Code Inspections
Continuous Integration
Independent Parallel Testing
Model With Others
Model/Documentation Reviews
Pair Programming
Test Driven Design (TDD)
Traditional Acceptance and System Testing