![What is Agile Development? ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Agile presentation to Telstra, April 2010
Similar to Agile presentation to Telstra, April 2010 (20)
Recently uploaded
Recently uploaded (20)
Agile presentation to Telstra, April 2010
- 1. Agile Software Development and Enterprise adoption Reg de Silva, Benn Wheeler & Mark Mansour April 2010
- 3. Waterfall vs Agile Software Development Source: http://www.digitalfocus.com/agile/
- 5. Why Agile? Source: http:// www.versionone.com/
- 6. Some Agile key practices Source: Swan, Brian (uk.builder.com)
Editor's Notes
- - adaptive software - ability to change is valued
- * architecture is a role not a job - sometime they are the technical product owner - architecture can be done by senior developers and dev leads * last responsible moment - up front planning is wasteful (lean thinking) - do as much as you need but no more - BUFD doesn't work because you don't know enough - amortize the risk over the lifetime of the project * agile pioneers are architecture friendly - Martin Fowler (Patterns of Enterprise Intergration) - Robert C Martin (UML, C++, PLoP) - Dave Thomas - James O. Coplien
- Sure, I’m taking this a bit out of context, but I’m trying to highlight the value of something actually working… The full quote reads: We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- * architecture is a role not a job - sometime they are the technical product owner - architecture can be done by senior developers and dev leads * last responsible moment - up front planning is wasteful (lean thinking) - do as much as you need but no more - BUFD doesn't work because you don't know enough - amortize the risk over the lifetime of the project * agile pioneers are architecture friendly - Martin Fowler (Patterns of Enterprise Intergration) - Robert C Martin (UML, C++, PLoP) - Dave Thomas - James O. Coplien