* Check for https://dsdm.org for further information.
Life Cycle of DSDM
Dynamic system development methods framework is developed in five phases: Feasibility Study, Business Study, Functional Model Iteration, Design and Build, and Implementation Phase; of which the first two phases are sequential in nature and the last three are incremental and iterative. The time interval also called as a time box is planned well before the game. Generally time boxes are from few days to few weeks.
Life Cycle of DSDM - Feasibility Study
The scope of feasibility study is to gather required details about whether the feasible solution exists or not. Detailed analysis is performed in later phases. Generally in practice, management conducts a workshop which includes stakeholders, developers, testers and all necessary interested parties. The scope of the workshop is to have a high level walkthrough of the project requirements. Feasibility reports, prototype, outline plan and risk logs can result from this phase. Feasibility reports is a high level report which enables the project steering committee to decide on project future, and any necessity for further feasibility study. Feasibility prototyping is a methodology of developing a prototype as proof of concept. High level planning and risk logs are also developed in this phase.
Life Cycle of DSDM - Business Study
This phase results in defining business area definition, prioritize requirements, system architecture definition and development plan. Business area definition provides high level information of business processes, interested parties, and other dependent variables which supports the proposed solutions. Development plan contains a high level plan about the project and subsequent increments. Functional and technical architecture is illustrated in the form of System Architecture Definition. The architecture defines the coherence of hardware, software and other effecting components. This definition helps in understanding the technical architecture to be used , describe the target platform, and outline description of the software architecture.
Life Cycle of DSDM - Functional Model Iteration
This phase produces functional models,, non functional requirements, implementation plan, time box plan, and functional model review record. The functional model defines the solution that includes both documents and functional prototype. Non functional requirements are obtained during workshop sessions between developers and ambassador users. Functional model review record captures the feedback on all part of the functional model. Implementation plan has details about current system increments and time box plan provides a recommend process schedule for a given time box.
Life Cycle of DSDM - Design and Build Iteration
This phase primarily engineer the system in order to satisfy user requirements. Tested product is the major outcome of this phase. Design and build iteration consist of four activities.
Identify the requirements of the module
Plan and commit to the requirement.
Develop the module, and
Validate the functionality of the module.
Life Cycle of DSDM - Implementation Phase
This phase covers the transition from the development environment to operational environment. The major objective of this phase is to place the tested system in the users working environment and train the individuals. Future development requirements are also framed in this phase. Incremental review document is used for illustrating planning activities for subsequent increments.
Life Cycle of DSDM – Key Players
There are different team players playing an effective role while practicing DSDM. Stake holders include executive sponsors, Ambassador user, Advisor user, visionary, project manager, coordinator, Team leaders, developers, testers, scribe, and facilitators. Executive sponsors are a high level designation who is committed to the project. He is the one who owns the system and responsible for it. Ambassador user is responsible providing key inputs to business requirements and design sessions. Visionary is responsible for driving vision of the project. Advisor user is responsible for providing information on request. Scribe is a stake holder role who is responsible for recording, managing and assisting with necessary documentation..
What is Crystal Clear?
Crystal clear is a project management methodology which belongs to crystal family. This methodology suits for small projects. Crystal clear recommends small incremental developments, deliveries over documentation, Involvement of end client, automated regression, and knowledge sharing workshops. An incremental development cycle generally varies between 2-3 months. Crystal clear methodology recommends annotated use case/ feature description. Crystal clear methodology recommends using case tools like compiler, version system, discussion boards and different management systems. Crystal clear methodology key players include programmers, sponsor, designer programmer, and users.
What is Crystal Orange?
Crystal Orange is a project management methodology which belongs to crystal family. This methodology suits for medium size projects. It contains 10-40 team members. The project team is divided into multiple cross functional teams. Crystal clear recommends small incremental developments, deliveries over documentation, Involvement of end client, automated regression, and knowledge sharing workshops. An incremental development cycle generally varies between 3-4 months. Crystal orange methodology recommends status reports and mock-up based design. Crystal orange methodology recommends using case tools like versioning, testing, programming and project tracking. Crystal orange methodology key players include UI programmers, DBA, architect, testers, design mentor, and users.
What is Adaptive Software Development?
Adaptive Software Development was developed by James A Highsmith. Adaptive software development focuses on developing large systems using incremental and iterative structure. Adaptive Software Development is carried out in three phases: Speculate, Collaborate and Learn. Project initiation and adaptive cycle planning is performed as part of Speculate, concurrent engineering is performed as part of Collaborate, Quality review and release is performed as part of Learning process. Adaptive Software development methodology is mission driven, Component based, Iterative, and risk driven. ASD team includes executive sponsors, participants, facilitator, scribe, developers, testers, and project manager.
What is Open Source Development?
Open source development methodology is software development methodology that harnesses the power of distributed peer review and process transparency. This development methodology inspired lot of software developers and resulted in various qualitative open source software. The OSS paradigm suggests the free source code distribution. A general OSD life cycles includes: Identifying a problem, finding volunteers, Identifying game plan, development, and testing. Different repository sites like SourceForge*, Freshmeat* etc helps a lot while implementing OSS. A typical OSD includes project leader, volunteer, tracker, observers and maintainers.
* https://sourceforge.net
* https://freshmeat.net
Bibliography
agilemanifesto. (n.d.). Agile manifesto. Retrieved december 2009, from Agile manifesto: https://agilemanifesto.org
Beck, K. (1999). Embracing Change with Extreme Programming. IEEE Computer 32(10) , 70-77.
Beck, K. (1999). Extreme Programming explained: Embrace change. Addison-Wesley.
DSDM-Consortium. (n.d.). DSDM. Retrieved December 2009, from DSDM: https://dsdm.org
extremeprogramming.org. (n.d.). extremeprogramming.org. Retrieved December 2009, from extremeprogramming.org: https://www.extremeprogramming.org/
Gorakavi, P. (2009). Build your project using Agile. asapm .
Gorakavi, P. (2009). Build your project using Scrum. asapm .
Kruchten, P. (1996). A Rational Development Process. Crosstalk , 11-16.
Kruchten, P. (2000). The Rational unified process: an Introduction. Addison - Wesley.
Palmer, S., & Felsing, J. (2002). A practical guide to feature driven development. Upper Saddle River: Prentice-Hall.
Takeuchi, & Nonaka. (1986). The New Product Development Game. Harvard Business Review , 137-146.
Thank you for reading books on BookFrom.Net Share this book with friends