Wednesday, June 25, 2008


Scrum : In rugby, ‘scrum’ (related to “scrimmage”) is the term for a huddled mass of players engaged with each other to get a job done. In software development, the job is to put out a release. Scrum for software development came out of the rapid prototyping community because prototypers wanted a methodology that would support an environment in which the requirements were not only incomplete at the start, but also could change rapidly during development. Unlike XP, Scrum methodology includes both managerial and development processes.

Tuesday, June 24, 2008


Two agile software development methodologies :

The most widely used methodologies based on the agile philosophy are XP and Scrum.

These differ in articulars but share the iterative approach described above.

XP :

XP stands for extreme programming. It concentrates on the development rather than managerial aspects of software projects. XP was designed so that organizations would be free to adopt all or part of the methodology.

XP development :

XP projects start with a release planning phase, followed by several iterations, each of which concludes with user acceptance testing. When the product has enough features to satisfy users, the team terminates iteration and releases the software.

Agile methodologies embrace iterations. Small teams work together with stakeholders to define quick prototypes, proof of concepts, or other visual means to describe the problem to be solved. The team defines the requirements for the iteration, develops the code, and defines and runs integrated test scripts, and the users verify the results.

Verification occurs much earlier in the development process than it would with waterfall, allowing stakeholders to fine-tune requirements while they’re still relatively easy to change.

WHAT IS AGILE?

Agile is about being open about what we’re capable of doing, and then doing it
– Kent Beck


Value System :
• People
• Collaboration
• Honesty
• Trust


Attitude :
Thinking guided by principles and reflected in behaviour


Simple Framework for dealing with change :
• Self-organisation
• Visibility
• Inspection
• Adaptation


Adaptive Ecosystem :
Tightly couples self-organising Team to a Product Owner