 |
|
 |
|
Very soon we will look at The Big Agile Toolkit in six steps.
If you cannot wait to get started just go straight there now. Here is the link:
We understand and support your enthusiasm to get started and to get delivering but we wish to give all
newcomers to agile a swift backgrounder to set the scene.
In a moment we will look at the important topic of welcoming change and run through the agile approach but first we will look at the word agile.
When we think of the word agile we think of nimble, light footed and alert. If we are agile we are quick to respond,
we are flexible and energetic. We are vigilant, prepared and observant.
However in this instance we are also trimmed down, lean and, to provide a mental analogy, like
the meerkats of the Kalahari desert permanently scanning the horizon for danger.
We are keenly aware of risk.
We are ready to challenge, to inspect, to rework, to evolve and to regroup and redirect our efforts if they seem misdirected or if we see and
agree upon a more favoured route. It is these concepts and qualities we will bring to our project work.
It is this that is agile. The word, in this context, was incepted by the Agile Alliance in the Agile Manifesto and there is a little more information about this later.
|
So agile, as we say in the Toolkit, is an ethos. It is a way of thinking and it is a way of working.
The Toolkit embraces this ethos and provides basic steps with checks and balances to ensure the process supports high precision and
accuracy as well as high velocity and enthusiasm. When we describe an agile project we invariably compare and contrast it with waterfall
projects. First of all then, before we get into agile projects we need to describe the waterfall project.
Websites, organisations and company
presentations that wish to promote agile often traditionally begin with the grave topic of waterfall failure as they start to describe waterfall.
We will not do this as all waterfall projects are not all failures and all agile projects are not immediate successes. It is the successful way
you deal with the complexities of a project and how these work positively and negatively inside your organisation that determines failure. It is not
simply the flavour, colour or taste of the method you adopt.
Nevertheless, it is important
that we understand agile and to do that first of all we need to swiftly explore the waterfall project.
|
|
|
|
|
|
|
|
|
|
|
|
Glossary: »
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
|
|
|
|
|
|
|
|
|
|
| | |
| | |
|
 
 SPADE: Successful Pragmatic Agile Delivery Everytime™ |
| Topic: 9 Page: 10/444 Progress: 2.3% |
 | |
|
|
|
|
|
|
|
|
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. |
|
