CSC/ECE 517 Fall 2009/wiki3 11 j8

The most popular Agile methodology is Extreme Programming (XP). However, there are many other agile process models that have been proposed and used in industry, such as--Compare these methodologies, telling how they are different from XP, and assessing their strengths and weaknesses.

Extreme Programming

Frequent small releases (Every week or two) Complete iteration (Every 1 - 3 weeks) User stories are written Code unit tests first Pair programming Emphasis on CRC crds during designs

http://www.extremeprogramming.org

Adaptive Software Development (ASD)

Strong emphasis on Dynamic programming languages speculate, collaborate, and learn cycles. http://en.wikipedia.org/wiki/Adaptive_Software_Development

Scrum

Places emphasis on different roles (Chicken/Pig)

  ScrumMaster
  Product Owner
  Team
  Stakeholders

Daily scrum meetings Sprint review (at end) sprint retrospective (at end) Spring planning meeting (at begining) frequent stackholder meetings

Items Product Backlog Sprint Backlog

two to four week 'sprints'

Dynamic Systems Development Method (DSDM)

Project lifestyle: feasibility study, business study, functional model iteration, design and build iteration, and implementation.

http://en.wikipedia.org/wiki/Dynamic_Systems_Development_Method

Crystal

3 priorities [ safety (in project outcome), efficiency, habitability (developers can live with crystal)]

http://martinfowler.com/articles/newMethodology.html#Crystal

Feature Drive Development (FDD)

model-driven short-iteration process composed of 5 activities.

Activities:

  Develop Overall Model - Walkthroughs of different models are done and presented for peer review.  
  Build Feature List - The result of the modeling stage is used to gather a list of features.  Domain is split into subject areas which contain business activities.  Max feature time is two weeks.
Plan by Feature - development plan from feature list
Design by Feature - A set of features that can be done in two weeks is sselected.  The design is done at the class level.
Build by features - each of the selected features is built.  Unit tests and code inspecition a must.  

Milestones

Six milestones per feature that are completed sequentially.  Percentage of each milestone is kept track o.