# data[].attributes.body
DSDM!
1) The development team is relatively small. Two programmers, two system analysts.
2) Time scale is fixed
3) The cost of the project is estimated to be 1mil.
4) It is a new and thoroughly scoped project. The systems analysts have limited capabilities in this area and other expert help may be needed.
5)

There will only be one increment required of the DSDM project.  However, it is thought that requirements can be prioritised, although these have not yet been specified fully.

# data[].attributes.headline
DSDM would be suitable for this Project.

# data[].attributes.subject
DSDM would be suitable for this Project.

# data[].attributes.body
1. Cost and time set (1 million pounds, 4 months).
2. The culture of the organisation is suitable for DSDM as one of the executive comitee is a DSDM trained.
3. Flexible to changes as reacting to a competitor action.
4.  Clear ownership of the company.
5. People are empowered.
6. A new project, which hasnt been done before.
7. features can be prioritise.

# data[].attributes.body
1- Fixed time, within three months, needs to have MUST features ,
2- Only one increment, but requirements can be prioritised,

MoSCoW approach
3- developers allocated nearly 80% of time which is against 80/20 approach
4- the current system is traditional but will be completely replaced by Agile system
5- Budget of 1M making it a fixed estimate cost

# data[].attributes.body
The business imperative for Rally is to have an efficient customer service operation for orders and enquiries up and running well before Parts4Cars opens, which is within three months - a very strict time-frame. Therefore, considering, the philosophy behind DSDM is to collaborate to converge on the best possible solution, in an agreed timescale, according to business priorities, DSDM would be a good approach.