1. Agile Software Development for IT Pini Cohen Architecture and Infrastructure EVP & Senior Analyst pinicohenstki.blogspot.com
2. Agenda What’s wrong in todays development scenario? Agile Software development What is holding back IT from Agile? Recommendations source: http://www.ynet.co.il/PicServer2/20122005/941342/NY123_wa.jpg
3. Software Development Is Limited By Constraints Quality Schedule Cost Scope Source: The Standish Group 2003 Source: Borland
4. Software Development Is Limited By Constraints Quality Schedule Cost Scope Source: The Standish Group 2003 Source: Borland 4
5. Software Development Is Limited By Constraints Quality Schedule Cost Scope Source: The Standish Group 2003 Source: Borland 5
7. What are the main reasons for software project overruns (budget or schedule)? (November 2008.) Source: cutter
8. Traditional Software Development The traditional development focus is to engineer out defects Good principle Hammer out defects early Defects arise because requirements change Too many communication gaps Design Code Test Deploy Isolated Process 8
9. What is Agility? The ability to… Move quickly Travel light Commit late Act soon Keep aware Respond to change Be good at following a moving target Evolve and adapt to the local environment 9
10. Agile Project Management - Overview 12 9 6 3 12 3 6 9 Code Analysis Code Test Implement Test Analysis Work Effort Time in Months Source: cutter Source: Cutter 10
11. What is holding back Agile in Israeli IT organizations? More responsibility is needed! Why should I develop anything without the end user approval? source: http://www.bombaychamber.com/Microsites/Project%20Website/responsibility.jpg
12. What is holding back Agile in Israeli IT organizations? Rigid organizational structure: design, code, test source: http://www.fhwa.dot.gov/infrastructure/asstmgmt/images/vmtex0404.gif
13. What is holding back Agile in Israeli IT organizations? End users that do not cooperate and feel that more responsibility is needed Why should the IT develop anything without my permission? source: http://www.bombaychamber.com/Microsites/Project%20Website/responsibility.jpg
14. What is holding back Agile in Israeli IT organizations? Lack of information about Agile: “We are already doing agile- we speak with the end users regularly – this is agile development!” The perception that “agile is for startups” (example: Microsoft consulting)
15. What is holding back Agile in Israeli IT organizations? Tried Agile (or think they tried Agile…) and failed
16. What is holding back Agile in Israeli IT organizations? Israeli integrators: want their money “guaranteed” money source: http://howdoiplayguitar.com/wp-content/uploads/2009/08/guaranteed_stamp.jpgstki modifications
17. Summery of what is holding back Agile in Israeli IT organizations? Inertia! Israeli IT shops are about 5 years late in agile adoption source: http://rt492.org/wl/img/inertia.gif
18. What are the main reasons agile methods have made project management more successful? (October 2007.) Source: cutter
19. New Generation of Knowledge Workers Live in virtual worlds Expect immediate results Many open threads Deliver quickly, in small increments Expect personalization Intolerant of disruption In short: very agile! http://www.solutionsiq.com/resources/SIQ-AgileDevelopmentPlatform-Rudd-Young-Agile2008.ppt
20. Agile Software Development Agile Software Development is catching up in Israeli ISV organizations Clients see the benefits of Agile in small-medium projects Large Agile projects (50 people) are more challengeable mainly when there is high interdependencies between the SW modules Agile is demanding more from the developers Large IT integrators will be challenged by innovative integrators that will adopt Agile All CIO’s should consider Agile Software Development as a mean for better business alignment and reducing costs
21. Agile Software Development “Best fit” for first agile project: Total staff of about 6-7 people End users of project that can be approached once in 2-3 weeks Not a new area (business and technology) Bonus: incremental delivery is viable
Comfortable participating in virtual worlds Expect immediate results and feedback Have many open threads and parallel tasks Deliver quickly and in tiny increments Expect personalization and customization Intolerant of workstream disruption In short: very agile!
