HAPPY BOOKSGIVING
Use code BOOKSGIVING during checkout to save 40%-55% on books and eBooks. Shop now.
Register your product to gain access to bonus material or receive a coupon.
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:Do you want to cut the development time and increase the fitness-for-use of screen based business applications, 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.
A Human Being Is Not Equivalent to a Tool: Working with the Dynamic Systems Development Method
Introduction.
Background.
Some definitions.
A bit of history.
Overview of the method.
Why is DSDM more rapid than the waterfall?
About this book.
I. THE METHOD.
1. DSDM process overview.Introduction.
The feasibility study.
The business study.
Functional model iteration.
Design and build iteration.
Implementation.
Key points.
2. The underlying principles.Key points.
3. The process in action.When to use DSDM.
The reality of iteration and incremental delivery.
Analysis and design techniques.
Key points.
4. Time versus functionality.Fitting quarts into pint pots.
Timeboxes.
MoSCow rules.
Controlling timebox activity.
To timebox or not?
The disaster scenario.
Key points.
5. The RAD project manager in action.What is different?
Planning a DSDM project.
The project roles.
Project structures.
Monitoring progress.
Workload.
Key points.
6. Impact on the organization.Making decisions.
User involvement.
Better communication.
Joint application design (JAD) workshops.
Training users.
Key points.
7. Never mind the quality?'Good enough' software.
Building in quality.
Testing.
DSDM and TicklT.
New procedures for old.
The capability maturity model.
Key points.
8. The RAD professional.