Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 Agile and Independent Testing  Agile and Independent Testing   The Project Time   The Project Time

Manage   »   Quality   »   Agile and Achievement


All projects are based on the things that we deliver and, because we seek early and regular benefits, we deliver things early and regularly. We will deliver some assessment deliverables early on in the project and at regular periods throughout the project. These outputs, we call shipments. Once we have completed all the shipments, we have emerged and completed our delivery and we then complete the project. Benefits realisation is finally conducted to ensure the proposed benefits of the project are achieved, reviewed and confirmed as done.

All projects are based on the things that we deliver and all projects must deliver output that people can recognise. If your project is to rebuild St Pauls Cathedral, then you must at the very least deliver a dome-like structure within the city of London. This basic sense of recognition of useable output is fundamental to all projects.

Your business must be able to recognise the output you create and be able to identify it, in this scenario they seek to identify the output as St Pauls Cathedral. Therefore, you need to know how they are going to do that. It is important to know what specific qualities your business wants to see before they agree to and recognise delivery. Let us have a look at that.

We know from the outset the objectives of our project and undertaking. To achieve those objectives, we must deliver certain assessment deliverables. From these, we can determine the important requirements for our project. So, for example, the objective of our project might be to deliver a content management system so that we can maintain our online e-commerce website. The content management system demands that we deliver certain assessment deliverables. These might include a security system. This is to ensure that only certain individuals are allowed to use the content management system and report any security violations.


The project will be much more complex than this. However, for now, we will concentrate on the security elements of our content management system.

So, the assessment deliverable is working security for our content management system. We need, first of all, to define the acceptance criteria for our content management system security. This might be, for example, that we will accept only the valid user ID and password combinations, of those people on the authorised users list, will be allowed access. Security violations will be reported by high priority e-mail to the system administrator. A security violation will occur if an incorrect user ID and password combination is entered. The I.P. address of the machine will be logged on the violations database, along with the user ID, password, date and time of the violation.

Assessment Deliverables



So we have our objective for the project. We have the description of our assessment deliverables. Furthermore, we have acceptance criteria for our assessment deliverables. Once we deliver our assessment deliverables and satisfy our acceptance criteria, we have delivered our shipment. So now we will plan our shipment.

Normally, project managers at this point would start to decompose the tasks involved in delivering the various elements of this shipment. They would look at a detail requirement specification and maybe the detailed system design specifications. From this, they will start to build up the various taxing role to deliver this outcome. They would then start to map this against a larger project plan, maybe using project management planning software.

Elsewhere in the Toolkit, we look in a lot more detail at the project management and planning activities. For now let us begin with another one of the important resources we are charged to manage: the Project Time.

Buffer



 Agile and Independent Testing     Agile and Independent Testing   The Project Time    The Project Time



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
Agile and Achievement






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 96  Page: 123/444  Progress: 27.7%
 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 (http://www.bigagiletoolkit.com/) 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.