Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Issues  Issues   Constraints   Constraints

Techniques   »   Risk Management   »   Dependencies

A dependency is often used in relation to one projects reliance on another project inside a programme. So the project will only be able to deliver a certain result if particular outcomes have already been successfully delivered by another project. Typically this can occur where a technical live environment or new technical architecture is designed, developed, installed and tested but requires a particular solution from a project to demonstrate it. Where you have such scenarios on your project, you document them in the dependency section of your RAID and review them periodically after your Daily Forum.

The dependencies are often task related. So one task cannot be started before another has ended or one task cannot be end before another has ended. In the Toolkit we are not task managing, this is old school. We are managing by timebox and by deliverables. We expect a team to deliver certain agreed and pre estimated output within an agreed fixed timescale. If you have specific dependencies inside a timebox – this timebox was defined at the delivery planning workshop with this dependency in mind.

Document it in the dependency section of your RAID and review it periodically after your Daily Forum. We find that project dependencies do not need reviewing as regularly as the issues and risks but you will need to determine such frequencies by your experiences on your project.


 Issues     Issues   Constraints    Constraints

Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z

#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
Topic: 367  Page: 322/444  Progress: 72.5%
 About    |    Author 
Follow @BigAgileToolkit

This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL ( and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.