PART A Introduction to DSDM Atern DSDM (Dynamic System Development Method) was launched in 1995 This is a method that focuses primarily on the management of Agile projects DSDM Atern is currently the latest version DSDM operates primarily in the corporate environment and always demonstrates the ability to work efficiently and in addition to the company's processes As a member of Agile methods, the goal of DSDM is to provide time and budget projects while being flexible enough to meet changing needs This is the reason DSDM is suitable for use in TOG because requirements can vary flexibly at any time along the development stages of TOG The Structure of an Atern Project Atern is an independent vendor approach, realizing many projects fail due to human issues rather than technology Atern's goal is to help people work together effectively to achieve their goals Atern is also independent of the tools and techniques that allow it to be used in any business and technical environment without the need to link the business to a particular vendor Atern is an agile project delivery framework that delivers the right solution for every problem Appropriate business solutions are delivered because: The project team and stakeholders focus on business results Timely delivery guarantees an early return on investment Everyone involved in the project work together to provide optimal solutions Work is prioritized according to the business needs and ability of the user to accommodate changes in the agreed upon time Atern does not compromise on quality ie the solution is not designed too high or low In addition, Atern harnesses the experience and creativity of users It uses repetitive lifecycle to develop the most appropriate solution to meet the goals of the project By dividing the project and creating a timetable, each project has clear results, the control is done by the Project Manager and the team members There are seven stages for an Atern project: figure Phase Pre-project Feasibility Foundations Exploration Engineering Deployment Post project Key resbonsibilities Start the project, agree with the Terms of Reference for the job it a short phase to assess the viability and the outline business case (justification) Key phase for ensuring the project is understood and defined well enough so that the scope can be baselined at a high level and the technology components and standards agreed, before the development activity begins Iterative development phase during which teams expand on the high level requirements to demonstrate the functionality Iterative development phase where the solution is engineered to be deployable for release For each Increment (set of timeboxes) of the project the solution is made available Assesses the accrued benefits this method is very convenient in easy in the organization for fit to the equivalent Some example sample provide below below: Figure 2: illustrates iterative development with the solution evolving over a number of ExplorationEngineering cycles before Deployment of an increment Figure 3: completes all Exploration activities prior to commencing the Engineering activities The timeboxed Iterative Development occurs within the stage as opposed to the previous and following example This approach is not to be confused with a traditional waterfall approach Figure : combines Exploration and Engineering work to deliver fully engineering subsets of the end product in a single pass Figure 4: describes a case with two engagement teams A team focused on exploration and a technical group In this example, the Exploration team can provide prototypes of the solution to the Engineering team who then develops solutions for Deployment Atern Principles Well-understood principles are better guides than detailed process procedures In Atern principles are used to provide guidance throughout the project.Atern has eight underlying principles and the complete framework can be directly derived from these The principles are based on best practice in its truest sense They define "the way things are done" Breaking one of these principles can lead to failure, as these are the basic building blocks for Atern, and bind together all the other elements of Atern Principal Description Focus on the Business Need Deliver what the business needs when it needs it The true business priorities must be understood with a sound business case Deliver on Time Timeboxes are planned in advance and the timeframe set The dates never change; features are varied depending on business priorities, in order to achieve the deadline Collaborate Teams work in a spirit of active co-operation and commitment Collaboration encourages Never Compromise on Quality Build Incrementally from Firm Foundations Develop Iteratively Communicate Continuously and Clearly Demonstrate Control understanding, speed and shared ownership The teams must be empowered and include the business representatives A solution has to be "good enough" The level of quality is set at the outset Projects must test early and continuously and review constantly Increments allow the business to take advantage of work before the final product is complete, encouraging stakeholder confidence and feedback This is based on doing just enough upfront analysis to proceed and accepting that detail emerges later Accept that work is not always right first time Use Timeboxes to allow for change yet continuously confirm that the solution is the right one Use facilitated workshops, daily standups, modeling, prototyping, presentations and encourage informal face-to-face communication The team needs to be proactive when monitoring and controlling progress in line with Foundations Phase They need to constantly evaluate the project viability based on the business objectives Unlike other methods, Atern repairs Time, Cost and Quality in the early stages of the project Prevention, in the form of lower priority features, ensures that the timely delivery of a viable solution can be achieved by protecting the Minimum Set that can be used and reducing or delaying Lower priority, if necessary, in accordance with MoSCoW rules ... the end product in a single pass Figure 4: describes a case with two engagement teams A team focused on exploration and a technical group In this example, the Exploration team can provide prototypes... change; features are varied depending on business priorities, in order to achieve the deadline Collaborate Teams work in a spirit of active co-operation and commitment Collaboration encourages... occurs within the stage as opposed to the previous and following example This approach is not to be confused with a traditional waterfall approach Figure : combines Exploration and Engineering work