DSDM is about people, not tools. It is about truly understanding the needs of a business, delivering software solutions that work and delivering them as quickly and as cheaply as possible. The Dynamic Systems Development Method provides a framework of controls and best practice for Rapid Application Development. It was created by a consortium of organisations and it has been proved, since its publication in January 1995, to be extremely effective in delivering maintainable systems which match the needs of the business better than those produced using traditional lifecycles. This book, commissioned by the DSDM Consortium and written by the chairman of the Technical Committee which developed the method, explores the day-to-day realities of implementing the method. It is a practitionerIs guide, dealing with issues such as how to get people from different disciplines to work together as a team, how to gain commitment and how to manage projects within normal business constraints. In this book you will find: practical guidelines on the implementation of key elements of the method such as "timeboxes" and the MOSCOW Rules clear recommendations for the roles and responsibilities of the members of the development team advice on which type of application is most likely to benefit from the method eight lengthy case studies by well-known companies, providing a benchmark against which to assess the suitability of candidate projects numerous examples and anecdotes, enabling the reader to benefit from the authorIs experience putting the method into practice Do you want to cut the development time and increase the fitness-for-use of screen based businessapplications, by orders of magnitude? This book will enable those in organisations which develop or purchase tailored IT systems, to gain a clear understanding of the benefits of the incremental and iterative approach embodied in the DSDM. 0201178893B04062001

Everyone is talking about agility and praising it as THE approach for successful project management. However, many approaches offer hardly any methods for external steering, budgeting, reporting, controlling. Many only cover the development process and leave it to the users to add further parts as needed. This repeatedly leads to the desire for hybrid project management, which combines agile development with project control and planning. However, most hybrid approaches are patchwork. Different philosophies are cobbled together, some of which contradict each other. DSDM® is different here. The method is completely based on agile approaches, but not only covers production, but also offers project planning, project steering and controlling, risk management and reporting with a goal-oriented role and responsibility management. In this booklet, the book author, himself an expert in DSDM® for many years, offers the reader a good overview of the method and shows why many more companies should get to grips with it.

The authors, Dorothy and Ian Tudor of TCC, have created a new version of the 'DSDM Student Workbook' (2002) to reflect the continuing development of the approach. This 2010 edition focuses on the very latest thinking in DSDM. Endorsed by the DSDM Consortium, the new 'DSDM Atern Student Workbook' provides a comprehensive guide to the Atern method,

Deliver bug-free software projects on schedule and within budget Get a clear, complete understanding of how to estimate software costs, schedules, and quality using the real-world information contained in this comprehensive volume. Find out how to choose the correct hardware and software tools, develop an appraisal strategy, deploy tests and prototypes, and produce accurate software cost estimates. Plus, you'll get full coverage of cutting-edge estimating approaches using Java, object-oriented methods, and reusable components. Plan for and execute project-, phase-, and activity-level cost estimations Estimate regression, component, integration, and stress tests Compensate for inaccuracies in data collection, calculation, and analysis Assess software deliverables and data complexity Test design principles and operational characteristics using software prototyping Handle configuration change, research, quality control, and documentation costs "Capers Jones' work offers a unique contribution to the understanding of the economics of software production. It provides deep insights into why our advances in computing are not matched with corresponding improvements in the software that drives it. This book is absolutely required reading for an understanding of the limitations of our technological advances." --Paul A. Strassmann, former CIO of Xerox, the Department of Defense, and NASA

This work is the definitive guide for IT managers and agile practitioners. It elucidates the principles of agile risk management and how these relate to individual projects. Explained in clear and concise terms, this synthesis of project risk management and agile techniques is illustrated using the major methodologies such as XP, Scrum and DSDM. Although the agile community frequently cites risk management, research suggests that risk is often narrowly defined and, at best, implicitly treated, which in turn leads to an inability to make informed decisions concerning risk and reward and a poor understanding of when to engage in risk-related activities. Moreover, the absence of reference to enterprise risk management means that project managers are unable to clearly articulate scope or tailor their projects in line with the wider expectations of the organisation. Yet the agile approach, with its rich toolset of techniques, is very well equipped to effectively and efficiently deal with the risks that arise in projects. Alan Moran addresses the above issues by proposing an agile risk-management process derived from classical risk management but adapted to the circumstances of agile projects. Though his main focus is on the software development process, much of what he describes could be applied to other types of IT projects as well. This book is intended for anyone who is serious about balancing risk and reward in the pursuit of value for their stakeholders, and in particular for those directly involved in agile software development who share a concern for how risk should be managed. Whilst a thorough background in risk management is not presumed, a basic level of familiarity with or exposure to agility is helpful.