The document discusses Agile software development and its adoption in enterprises. It defines Agile development as an iterative approach involving working in small 2-week iterations with customer prioritization of requirements. Key benefits of Agile include delivering what customers want, reducing risks through frequent releases, and better alignment between business and IT teams. Successful adoption requires availability of customer representatives, management support, suitable team members and structure, and an Agile coach.

1. Agile Software Development and Enterprise adoption Reg de Silva, Benn Wheeler & Mark Mansour April 2010

2. What is Agile Development? Agile development is an “umbrella” term for several iterative and incremental software development methodologies (i.e. XP, Scrum, Kanban, etc.) Agile: Is customer-centric . Is detailed, rigorous and disciplined . Involves working in small iterations , often two weeks in duration, with concurrent analysis, development and testing. Focuses on empowering people to collaborate and make decisions together quickly and effectively. Represents a cultural shift from traditional development.

3. Waterfall vs Agile Software Development Source: http://www.digitalfocus.com/agile/

4. The key benefits of Agile software development include: Delivers what the customer really wants - customer prioritises and chooses requirements with highest business value each iteration. Risk reduction - working code delivered every iteration with multiple short release phases. Quality - reduced defects due to disciplined practices and constant collaboration between project team members and business partners. ‘ One Team’ - better alignment between the Business and Information Technology. The benefits of Agile

5. Why Agile? Source: http:// www.versionone.com/

6. Some Agile key practices Source: Swan, Brian (uk.builder.com)

7. Agile Adoption for the Enterprise

8. Availability of customer representatives (SME’s) for requirements workshops, daily stand up meetings, iteration planning, clarifications and decision making. Management support – particularly for technology teams new to Agile. Talent and Social Engineering Capable team members with good cultural fit. Common goals and collective project ownership. Willing to try a different approach to software delivery which they are continuously improving. Smaller co-located project teams are more suitable for Agile development projects to allow for effective communication. Agile coach - at least one resource within the project team with extensive Agile experience. Agile critical success factors

9. "significant design decisions that shape a system, where significant is measured by cost of change" -- Grady Booch What is Architecture?

10. last responsible moment Architecture considerations

11. Working software over comprehensive documentation while there is value in comprehensive documentation, we value working software more. Agile Groups value

12. architect is a role Architecture considerations

13. ? ? ? ? ? ? ? ? ? Questions

14. Benn Wheeler [email_address] http:// au.linkedin.com/in/bennwheeler Reginald de Silva [email_address] http://au.linkedin.com/in/regdesilva Mark Mansour [email_address] http:// au.linkedin.com/in/markmansour Contacts

15. Agile software development Using Agile software development – part 1 Using Agile software development – part 2 Using Agile software development – part 3 Agile development - Version One Agile manifesto Agile modeling Behaviour Driven Development definition Behaviour Driven Development Introducing BDD Kano Analysis Parking Lot Diagrams Planning Poker More information…