Dynamic Software Development Method (DSDM) works with 8 principles basically abiding by its philosophy. The ultimate goal is the completed and successful project.
- Business requirements are the main focus
- Timely delivery
- Collaborate
- High Quality Standards
- Incremental approach in developing the software
- Develop iteratively
- Communicate continuously and clearly
- Good control on the overall process.
DSDM follows the 4 processes to achieve the project objective abiding by its philosophy throughout.
- Feasibility
- Foundations
- Evolutionary developments
Including the pre-project and the post project there are totally 6 phases in a project life cycle. Feasibility gives a nod on whether we should continue with the project. The time spent in this phase should be just enough to prove that the project is worth carrying out. The team comes up with strong foundation on the requirement understanding, design approach. And the development begins. DSDM makes sure that it is making use of some of the best methodologies like time boxing, iterative development and MoSCow approach to deliver the same. The deployment phase does the review, deploy, and assemble etc. to make the deliverable a working model. There will be rework based on the review comments and the deployment issues.
The practices used by DSDM to achieve its goals are:
Workshops: Facilitated workshop enables people to interact more resulting in more collaboration. The decisions are taken quickly and the team works to achieve the agreed upon goal. This is a very rapid way of decision making taking the consent from all the stake holders thus empowering the team in the process.
MoSCoW: it is a prioritization approach to manage priorities. The letters stand for:
- Must Have(Minimum Usable SubseT (MUST) )
- Should Have
- Could Have
- Won’t Have this time
The business requirements should be broken down to the above 4 types and prioritization should be done accordingly.
Iterative Development: The development is segregated into multiple cycles where each cycle begins with a discussion of what requirements need to go in that cycle. It is a collaborative approach where each requirement is discussed on how it would be designed, developed and taken to completion.
Modelling techniques: This provides a visual representation of the requirements. They provide an early insight on whether the requirements will suffice the business needs. This can be achieved by using prototypes, mock-ups, network diagrams, process diagrams etc.
Time boxing: A fixed timeframe in which the objective has to be met. The objective might be a small set of the entire business requirements for that timeframe. The focus is on developing a small set of products incrementally. This can vary from 2 weeks to 4 weeks in general or this could be just a day activity also. Time box comprises of 3 major steps
- Investigation – Confirming on all the requirements deliverable by this time box.
- Refinement – Implementing the requirements on agreed priorities.
- Consolidation- Making sure the products pass the agreed acceptance criteria.
Time boxing works in collaboration with MoSCoW approach.
Communicating clearly and regularly is a key factor in a project’s success. DSDM provides lot of importance to effective communication skills and builds more trust into the team.
- What are Scrum roles and why it’s needed? - August 12, 2017
- Stakeholder Analysis – Is it required? - July 28, 2017
- Project Manager – An integrator, how? - July 28, 2017
- Different PMI Certifications – Which one to choose? - July 28, 2017
- What is the importance of Change Management in Project Management? - June 23, 2017
- What’s important to know to build a career in Agile? - June 23, 2017
- Agile Basics, Manifesto & Principles - June 23, 2017
- Scrum – Is it mandatory to learn in today’s IT market? - June 2, 2017
A concise discussion of the 8 DSDM principles. I have read a number of online post about this subject and I’ve found this post easy to understand.