#

Agile Method

Requirements Representation

Customer Role

1.

XP

User Stories as both written cards and conversations.

Written cards are not mandatory for implementation and are only considered “promises for conversation”.

Requirements are not supposed to be complete or clearly stated.

User stories are destroyed after implementation is completed.

On-site customer is required to participate in requirements definition, estimation and prioritize.

2

Scrum

User stories are used to represent requirements.

The actual requirements are defied based on the discussion of user stories between software owner and software developers.

Software owner plays the lead role in defining the requirements.

3

FDD

Requirements are represented using UML diagrams.

List of features are used to manage the functional requirements.

Requirements are first represented in a high-level context.

For each modeling area, the requirements are modeled per domain.

After requirements are modeled, it should be peer reviewed.

Not specified.

4.

Lean Software Development

Just-In-Time methodology is applied in requirements gathering.

User stories (cards) are also used by the customer to specify initial requirements and sample screens by the developers.

Developers then provide a time estimate for each card.

Provide input on sample screens and initial user stories.

5.

ASD

Requirements gathering is part of the speculation phase.

Not specified.

6.

Kanban

User stories are used to define each sprint main goal.

Each sprint handles a single user story.

Each story is divided into server-side and client-side task.

Each task is further divided into subtasks.

Not specified.

7.

AUP

Requirement phase consists of the following activities: (1) identifying stakeholders, (2) understanding problem, (3) establishing a basis of estimation, and (4) defining user interface.

User stories are used in the construction phase.

Requirements are presented as Business Use Case Model.

Not specified.

8.

DSDM

Requirements are gathered and prioritized during the feasibility phase.

Not specified.