Agile Process

The follwoing are agile process/methods used also part of the agile alliance.

•XP [Extreme Programming].

1.This is founded and initiated by Kent beck, who was the “project Manager” for the “Payroll inventory system” during the “CCC” project.
2.Kent brought in Ron Jefferies as Agile coach to take the project to completion.
3.Here whole team’s works as one team in delivering the customer specific project. Customer decides what user story and process of taking out to the door.
4.XP teams put a simple system into production early, and update it frequently on a very short cycle.
5.It is governed by the 12 principles [some of them are mentioned as below].

Some of the principles of XP

->Pair Programming.
->40-hour Week.
->On-site Customer.
->Daily builds
->Planning Game
->Small Releases
->Collective Ownership
->Continuous Integration [ Like Daily Builds]
->Coding Standards


1.This is also agile process, where in it, will have pre-defined work scheduling, time lines and work breakdown [on the basis of the User stories].
2. SCRUM keyword is taken from RUGBY game.
3. It was initially developed by Ken Schwaber and Jeff Sutherland later collaboration done by Mike Beedle
4. SCRUM provide “project Management framework” that focuses on the development
->“15 minute team meeting for co-ordination and integration
-> The work is defined mostly monthly or quarterly or” specific time duration”. And also this is reviewed in same period.


Test driven development: In this is process the “development is centered on the “testing of the work.

For example, if somebody is writing “printing/display function”, In TDD , the first dummy test case is written to start with and then “coding is done”
We may not have any take-away for this article. But “if you are cooking something”, you have to eat-it-too.

•Lean Development:

Bob Charette’s Lean development is based on the restructuring of the Japanese automobile industry of 1980’s.

The development or “production” is based on “MacDonald’s” or “DELL model of the work /shipping.

Process is changed at runtime, without too much process centric changes and protocols.

This is something like “Build against order”. If there is problem exists in the current development this will be taken as separte activity. The main activity/flow is not changed.

Japan auto market revolutionized and also used “parallel processing” kind of activities, to speed-up the car production and increase in revenues.


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s