 |
|
It is evident from the agile project community that quite a bit of nerdy or adolescent activity is in operation and quite often promoted. Go to any significant agile conference or event and you will see what we mean. In the privacy of your project rooms, this is great fun and cool.
As we say, in the privacy of your project rooms, this is fun and cool. At this juncture, it is wise to mention however that such behaviours in much less welcoming environments may not be greeted with such warm appreciation. We do project work for many large banks and various government departments. In these often frolic free environments any behaviour that is or could be labelled flippant or frivolous is treated with very swift response and censure, often with financially painful consequences for a delivery partner. It is thus why we refer to the topic of continuous integration build status notification. Let us begin with some of our observations.
|
|
|
|
|
|
|
|
|
|
|
|
Glossary: »
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
»
|
|
|
|
|
|
|
|
|
|
| | |
| | |
|
 
 SPADE: Successful Pragmatic Agile Delivery Everytime™ |
| Topic: 317 Page: 269/444 Progress: 60.6% |
 | |
|
|
|
|
|
|
|
|
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. |
|
