RAD & the Dynamic Systems Development Method

Lecture Contents Rapid Application Development Dynamic Systems Development Method How DSDM Differs for the Manager Conclusions Further Reading

Rapid Application Development relatively new fashion in SD began late 80s / early 90s familiar triggers frustration with project timescales problems with early freeze in requirements continuing poor involvement of users

some elements of RAD already familiar iterative + incremental prototyping heavy use of new tools 4GLs VB, Delphi, etc

strong user involvement often includes JAD Joint Applications Development pioneered at IBM in late 70s uses group sessions with users to define objectives establish requirements develop / approve design

Timeboxing new to SD projects timebox = absolute time frame within which a deliverable must be achieved

RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD

 product-based, not activity-based unfinished products must be delivered on time: deliver what you can in the time but it must work !

timebox can apply to whole projects or to components at either level, it focusses developers minds and improves manager / client confidence timeboxes are built into project schedule very early and not ( usually ) changed early RAD was reactive fragmented sometimes little more than hype ( e.g. VB = RAD )

Dynamic Systems Development Method Attempt to develop industry-standard RAD method Consortium first met in Jan 1994 Founding members include IBM ICL LBMS British Airways

The consortiums mission: to develop and continuously evolve a public domain method for RAD the published manual includes framework for all project activities the method has 4 phases: feasibility functional prototype iteration design prototype iteration implementation

RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD

(From DSDM homepages) Method is built on 9 fundamental principles active user involvement teams are empowered focus on frequent product delivery fitness for business purpose is essential criterion for acceptance iterative and incremental development reversability of all changes requirements baselined at high level testing integrated throughout life-cycle collaborative and cooperative approach Framework also covers: project management team structures user involvement skills and responsibilities estimating risk assessment change control
RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD

 configuration management testing QA software procurement method tailoring 2nd version of method based on real-world experience Early Adopters projects critical in refining the method: Boston Globe production tracking system Lloyds Bank Insurance quotations system Fujitsu Europe repairs management system Post Office licensing system Consortium also provides education and certification at various levels: DSDM aware DSDM practitioner DSDM project manager How DSDM Differs for the Manager

Analysis & Design techniques... not prescriptive... any diagram, any paradigm predetermine core models for that project A&D set for developers minimum for maintenance (code + ???) maintain nothing else Project Selection... appropriate projects have: functionality visible at interface all users clearly identified limited computational complexity if large, easily split into increments real time constraint flexibility in requirements BT maxim: can use some of DSDM all of the time, all of DSDM some of the time

Planning timeboxes... keep short (2-6 weeks optimal)

RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD

prioritise requirements - MoSCoW Must have... Should have... Could have... Want to have...

checkpoints

split box:

investigation

O C

refinement O

consolidation

set objectives (after Stapleton)

Manager Role... greater logistical challenge analysis to design very fast no room for slip all facilities must be ready when needed little emphasis on change control overall planning, timeboxing control the scope within box, change made easy no contingency accounted for by requirements priorities not scheduled Gantt chart of little use

RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD

Project Roles... IT / IS staff undifferentiated usual levels are developer / senior developer not programmer / analyst extra roles: Technical co-ordinator controls system architecture, config mgt, etc. May be crossteam. User roles - ambassador user, visionary, advisors communications: short sharp daily meetings BA rule: no-one allowed to say I am doing... - must say instead I have done... Culture change required, through education Project Boards workload may increase immensely! Conclusions RAD represents an attempt to speed SD by the use of incremental + iterative prototyping timeboxing strong user participation, e.g. through JAD Early attempts at RAD were confused and fragmented The DSDM Consortium has since 1994 offered an evolving public domain standard for RAD The DSDM method covers all aspects of SD management from training to procurement

Organisation impact...

RAD & THE DYNAMIC SYSTEMS DEVELOPMENT METHOD