We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8
Agile Process Models
• Extreme Programming • Adaptive Software Development • Dynamic Systems Development Method • Scrum • Crystal • Feature Driven Development • Agile Modelling Extreme Programming
• Most widely used Agile process, Originally proposed by Kent Back
• Uses an Object oriented approach as its preferred development paradigm • Defines 4 framework activities - Planning - Design - Coding - Testing XP-Planning • Begins with the creation of a set of stories( called user stories) • Each Story is written by user and placed on an index card • The customer assigns a value(i,e a priority) to the story • Agile team assesses each story and assigns a cost • Stories are grouped 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 simple principle • Encourages the use of CRC (class, responsibility, collaborator) cards • For difficult design problems, suggests the creation of “Spike Solutions”- a design prototype • Encourages “ Refactoring”- an iterative refinement of the internal program design • Design occurs both before and after coding commences XP- Coding • Recommends the construction of a series of unit tests for each of the stories before coding commences • Encourages “ Pair programming” -Mechanism for real time problem solving and real time quality assurance -Keeps the developer focused on the problem at the hand
• Needs continuous integration with other portions(stories) of the s/w, which
provides a smoke testing environment XP- Testing • Unit tests should be implemented using a framework to make testing automated. This encourages a regression testing strategy. • Integration and validation testing can occur on a daily basis • Acceptance tests, also called customer tests, are specified by the customer and executed to assess customer visible functionality • Acceptance tests are derived from user stories Extreme programming Project