Conclusion Agile Demystified Amadori Courses Agile Demystified 1
- Slides: 22
Conclusion Agile Demystified Amadori Courses: Agile Demystified 1
• In the first half of this course we looked at the detail of the Agile Manifesto • Learning that it is a process • Created by experienced developers to address the real-life problems they were having delivering high quality software in a world of tight deadlines and constantly shifting requirements • Which devolves responsibility for deciding how and when software should be delivered to individual delivery teams working in close proximity to each other • Manages change by releasing smaller releases more frequently Amadori Courses: Agile Demystified 2
Things to remember 1 • Even the authors of the Agile Manifesto never claimed their process was suitable for all projects or all organisations…… • In fact they make clear that only organisations which meet very clear criteria are suitable candidates Amadori Courses: Agile Demystified 3
Amadori Courses: Agile Demystified Things to remember 1 • So there is no shame in not adopting agile methods…. . • It doesn’t mean you are a second rate developer • Or Working for a second rate organisation…… • It simply means that Agile is not the right process for you… 4
Amadori Course 5
Things to remember 3 You are either Agile or you are not…. • That’s not to say that you can’t adopt some of the elements of Agile into your existing process • Just don’t call the result Agile…. • Or expect it to cope with change in the way Agile does Amadori Courses: Agile Demystified 6
Exercise If you haven’t done so already take a few minutes to fill in the Agile Questionnaire for either 1. a project you have been closely involved with recently 2. The organisation you currently work for Amadori Courses: Agile Demystified 7
Review Let’s review your answers Amadori Courses: Agile Demystified 8
Categories • As discussed earlier your responses to each question should fall into 1 of 3 categories • 1. There or Almost There • 2. Possible, but significant work required • 3. Agile probably isn’t for you (at the moment at least) Amadori Courses: Agile Demystified 9
• Your current process is either 1. There or Almost There • Already following agile principles Or • Would require only minor adjustments to become Agile compliant Amadori Courses: Agile Demystified 10
2. Possible, but significant work required • Your current process is not Agile but could be made so with significant investment of time and resources • Whether this investment would pay off in the long run would depend both on 1. How much else of the Agile Manifesto you are able to implement 2. The expected long term payoff from making these additional changes isolation Amadori Courses: Agile Demystified 11
3. Agile probably isn’t for you (for the moment at least) • Your project or organisation is currently setup in such a way that adopting agile processes would involve a fundamental change in the management philosophy of the organisation and its entire approach to delivery • Piecemeal adoption of elements of the Agile Manifesto are also likely to prove unsuccessful unless the overall philosophy of the company changes Amadori Courses: Agile Demystified 12
Overall Assessment Largely Green • Your project/organisation is likely to see significant benefits in the short to medium term from adopting a fully agile process • GO FOR IT !!! You are so close to Agile already it’s hard to think of a good reason not to go Agile • UNLESS there are one or more RED areas in your questionnaire Amadori Courses: Agile Demystified 13
• Even a single Red result may be enough to mean that it is not feasible for that project/organisation to follow agile processes at that moment in time Overall Assessment Red • This is because Red categorisation generally highlights a fundamental incompatibility between the way the whole organisation manages change and the delivery process currently with the devolution of decision making and responsibility advocated by the Agile Manifesto • Unless attempted in a context where there is a willingness to devolve decision making to delivery teams any attempt to implement Agile will almost certainly fail Amadori Courses: Agile Demystified 14
Overall Assessment Mixed Orange/Green • Benefits from adopting agile processes are still possible but will take longer to accrue depending on the type and volume of process changes you are required to make • Review the areas you have marked Orange and focus on fixing these BEFORE attempting to go fully Agile Amadori Courses: Agile Demystified 15
• Mainly Orange Overall Assessment • Attempting to go fully Agile is only recommended if there is a serious long term commitment by the Organisation as a Whole to support the change as the benefits from agile will generally only arise in the medium to long term and follow significant teething problems during the conversion process Amadori Courses: Agile Demystified 16
Benefits of this Approach • Using a questionnaire like this allows an organisation to determine • 1. whether Agile is the right option Now • 2. Whether it is an option for the future • In an objective non emotive fashion Amadori Courses: Agile Demystified 17
Benefits of this Approach • It allows you to discuss your decision even with strong supporters/opponents of Agile without the need to turn the discussions into arguments • It presents a clear roadmap of the areas/issues which must be addressed if you are to successfully adopt Agile • It provides you with detailed examples from your own organisation as to why Agile principles can or cannot be applied. Amadori Courses: Agile Demystified 18
Consequences: 1. You decide to go Agile 1. You should concentrate on fixing any issues or areas which were not Green in the questionnaire and then 2. Ensure that every affected by the change shares your understanding of what Agile really involves 3. Check everyone is clear AND happy about their new role in the revised process 4. I’d recommend that you carry out a pilot agile project first and then apply lessons learnt when you roll out the process more widely Amadori Courses: Agile Demystified 19
Consequences: 2. You decide NOT to go Agile 1. You have a made a decision based on objective evidence and not emotion 2. You have detailed to back up your decision 3. It is now clear why you are NOT adopting Agile and what would need to change within your organisation for a re-evaluation of the decision to be worthwhile Amadori Courses: Agile Demystified 20
Consequences: 3. You decide not to go Agile right NOW 1. The results of the questionnaire provide you with a roadmap 2. This shows you what areas need to be addressed before the organisation can considered READY for Agile 3. At this point the organisation must decide whether it wants to go agile or not Amadori Courses: Agile Demystified 21
And That’s IT !! • Hopefully these sessions have both • Given you a clearer understanding of what AGILE really is • Allowed you to determine in an objective fashion whether or not your organisation is ready to adopt AGILE processes Amadori Courses: Agile Demystified 22
- Amadori report
- Contratto soccida amadori
- Setuid demystified
- Erp demystified
- Erp demystified
- Adrienne porter felt
- Erp demystified
- Conclusión de la contabilidad gubernamental
- Pipeline engineering courses online
- Consortium of independent colleges
- Smmdp courses
- Simad university courses
- Common assessment framework (caf)
- Local guide program
- Wanic courses
- Courses in college
- Security desk genetec
- Genetec video export
- Harvard it academy specified foundational courses
- Mpa subjects in pakistan
- Uncc transfer
- Georgia npdes permit search
- Dartmouth sociology