The most widely used agile process, originally proposed by Kent Beck
XP Planning
• Begins with the creation of “user stories”
• Agile team assesses each story and assigns a cost
• Stories are grouped to for a deliverable increment
• A commitment is made on delivery date
• After the first increment “project velocity” is used to help define subsequent delivery dates for other increments
XP Design
• Follows the KISS (Keep it Simple, Stupid) principle
• Encourage the use of CRC cards (Class Responsibility Collaboration)
• For difficult design problems, suggests the creation of “spike solutions”—a design prototype (A Working Model)
• Encourages “refactoring”—an iterative refinement of the internal program design
XP Coding
• Recommends the construction of a unit test for a store before coding commences
• Encourages “pair programming”
XP Testing
• All unit tests are executed daily
• “Acceptance tests” are defined by the customer and executed to assess customer visible functionality
Agile Model:
It has rapid and adaptive response to change.
Effective communication in structure and attitudes among all team members.
Drawing the customer into the team. Eliminate “us and them” attitude Planning in an uncertain world has its limits and plan must be flexible.
Eliminate all but the most essential work products and keep them lean.
Emphasize an incremental delivery strategy as opposed to intermediate products that gets working software to the customer as rapidly as feasible.
A well-designed agile process may “flatten” the cost of change curve by coupling incremental delivery with agile practices such as continuous unit testing and pair programming. Thus, team can accommodate changes late in the software project without dramatic cost and time impact. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Agility Principles:
1. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
2. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
3. Business people and developers must work together daily throughout the project.
4. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
5. The most efficient and effective method of conveying information to and within a development team is face–to–face conversation.
6. Working software is the primary measure of progress.
7. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
8. Continuous attention to technical excellence and good design enhances agility.
9. Simplicity – the art of maximizing the amount of work not done – is essential.
10.The best architectures, requirements, and designs emerge from self–organizing teams.
11. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
I hope this article is useful to you, plz follow the next volume for more information.
please post your doubts in the comment box.
You can write to me at codingallrounders@gmail.com
Subscribe by Email
Follow Updates Articles from This Blog via Email
No Comments