According to The Code Project Web side the following figure shows what the Project Life-Cycle consists of: The DSDM development process consists of 7 phases. The first one is before the project has officially started. Then there are the project studies, which in this document are considered to be one phase. Then there are three more phases that consist of iterative cycles, which are repeated as necessary to complete the project.
Then there is the post-project phase, where the project is maintained. The project flow may move between the different phases in the directions indicated by the arrows above.The dark blue arrows in the diagram indicate the normal forward direction of project flow. The green arrows indicate directions that may be taken as necessary under normal circumstances. For example, if the team has finished a “Design and Build” iteration, but the system cannot be released until another area’s functionality has been defined and it has been built, the project flow may go back to the “Functional Model” iteration to complete that area. The light red arrow represents a direction that is only taken if the project has been found to not meet the required functionality.According to In the bottom chart is shown the four steps of the DSDM Project Life-cycle in a even more specifically manner. Activity Sub activity Description Study Feasibility Study Stage where the suitability of DSDM is assessed.
Judging by the type of project, organisational and people issues, the decision is made, whether to use DSDM or not. Therefore it will generate a FEASIBILITY REPORT, a FEASIBILITY PROTOTYPE, and a GLOBAL OUTLINE PLAN which includes a DEVELOPMENT PLAN and a RISK LOG.Business StudyStage where the essential characteristics of business and technology are analysed. Approach to organise workshops, where a sufficient number of the customer’s experts are gathered to be able to consider all relevant facets of the system, and to be able to agree on development priorities. In this stage, a PRIORITISED REQUIREMENTS LIST, a BUSINESS AREA DEFINITION, a SYSTEM ARCHITECTURE DEFINITION, and an OUTLINE PROTOTYPING PLAN are developed. Functional Model Iteration Identify functional prototype Determine the functionalities to be implemented in the prototype that results from this iteration.In this sub-stage, a FUNCTIONAL MODEL is developed according to the deliverables result of business study stage.
Agree schedule Agree on how and when to develop these functionalities. Create functional prototype Develop the FUNCTIONAL PROTOTYPE, according to the agreed schedule and FUNCTIONAL MODEL. Review functional prototype Check correctness of the developed prototype. This can be done via testing by end-user and/or reviewing documentation. The deliverable is a FUNCTIONAL PROTOTYPING REVIEW DOCUMENT.
Design and Build Iteration Identify design prototypeIdentify functional and non-functional requirements that need to be in the tested system. And based on these identifications, an IMPLEMENTATION STRATEGY is involved. If there is a TEST RECORD from the previous iteration, then it will be also used to determine the IMPLEMENTATION STRATEGY. Agree schedule Agree on how and when to realise these requirements. Create design prototype Create a system (DESIGN PROTOTYPE) that can safely be handed to end-users for daily use, also for testing purposes. Review design prototype Check the correctness of the designed system.Again testing and reviewing are the main techniques used.
An USER DOCUMENTATION and a TEST RECORD will be developed. Implementation Implementation User approval and guidelines End users approve the tested system (APPROVAL) for implementation and guidelines with respect to the implementation and use of the system are created. Train users Train future end user in the use of the system. TRAINED USER POPULATION is the deliverable of this sub-stage. Implement Implement the tested system at the location of the end users, called as DELIVERED SYSTEM. Review businessReview the impact of the implemented system on the business, a central issue will be whether the system meets the goals set at the beginning of the project. Depending on this the project goes to the next stage, the post-project or loops back to one of the preceding stages for further development.
This review is will be documented in a PROJECT REVIEW DOCUMENT According to Wikipedia. http://en. wikipedia. org/wiki/Dynamic_Systems_Development_Method#Critical_Success_Factors_of_DSDM Methodology.
In order for DSDM to be a success, a number of prerequisites need to be realised.First, there needs to be interactivity between the project team, future end users and higher management. This addresses well known failures of IS development projects due to lack of top management motivation and/or user involvement. The second prerequisite for DSDM projects is that the project can be decomposed in to smaller parts enabling the use of an iterative approach.
According to http://www. selectbs. com/adt/process-maturity/what-is-dsdm.
Within DSDM a number of factors are identified as being of great importance to ensure successful projects.Factor 1: First there is the acceptance of DSDM by senior management and other employees. This ensures that the different actors of the project are motivated from the start and remain involved throughout the project. Factor 2: The second factor follows directly from this and that is the commitment of management to ensure end-user involvement. The prototyping approach requires a strong and dedicated involvement by end user to test and judge the functional prototypes.
Factor 3: Then there is the project team.This team has to be composed of skillful members that form a stable union. An important issue is the empowerment of the project team. This means that the team (or one or more of its members) has to possess the power and possibility to make important decisions regarding the project without having to write formal proposals to higher management, which can be very time-consuming. In order for the project team to be able to run a successful project, they also need the right technology to conduct the project. This means a development environment, project management tools, etc.