Agile Software Development and Enterprise adoption Reg de Silva, Benn Wheeler & Mark Mansour April 2010
What is Agile Development? <ul><li>Agile development  is an “umbrella” term for several iterative and incremental software...
Waterfall vs Agile Software Development Source: http://www.digitalfocus.com/agile/
<ul><li>The key benefits of Agile software development include: </li></ul><ul><li>Delivers what the customer  really wants...
Why  Agile?   Source: http:// www.versionone.com/
Some Agile key practices Source: Swan, Brian (uk.builder.com)
<ul><li>Agile Adoption  </li></ul><ul><li>for the Enterprise </li></ul>
<ul><ul><li>Availability of customer representatives  (SME’s) for requirements workshops, daily stand up meetings, iterati...
<ul><li>&quot;significant design decisions that shape a system, where significant is measured by cost of change&quot;  </l...
<ul><ul><li>last responsible  moment </li></ul></ul>Architecture considerations
<ul><ul><li>Working software over comprehensive documentation </li></ul></ul><ul><ul><li>while there is value in comprehen...
<ul><ul><li>architect is a role </li></ul></ul>Architecture considerations
<ul><li>? </li></ul>? ? ? ? ? ? ? ? Questions
<ul><li>Benn Wheeler </li></ul><ul><li>[email_address] </li></ul><ul><li>http:// au.linkedin.com/in/bennwheeler </li></ul>...
<ul><li>Agile software development </li></ul><ul><li>Using Agile software development – part 1  </li></ul><ul><li>Using Ag...
Upcoming SlideShare
Loading in...5
×

Agile presentation to Telstra, April 2010

1,541

Published on

Telstra Solution Architecture Community of Practice (April 29th 2010)

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,541
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • - 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&apos;t work because you don&apos;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&apos;t work because you don&apos;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
  • Agile presentation to Telstra, April 2010

    1. 1. Agile Software Development and Enterprise adoption Reg de Silva, Benn Wheeler & Mark Mansour April 2010
    2. 2. What is Agile Development? <ul><li>Agile development is an “umbrella” term for several iterative and incremental software development methodologies (i.e. XP, Scrum, Kanban, etc.) </li></ul><ul><li>Agile: </li></ul><ul><ul><li>Is customer-centric . </li></ul></ul><ul><ul><li>Is detailed, rigorous and disciplined . </li></ul></ul><ul><ul><li>Involves working in small iterations , often two weeks in duration, with concurrent analysis, development and testing. </li></ul></ul><ul><ul><li>Focuses on empowering people to collaborate and make decisions together quickly and effectively. </li></ul></ul><ul><ul><li>Represents a cultural shift from traditional development. </li></ul></ul>
    3. 3. Waterfall vs Agile Software Development Source: http://www.digitalfocus.com/agile/
    4. 4. <ul><li>The key benefits of Agile software development include: </li></ul><ul><li>Delivers what the customer really wants - customer prioritises and chooses requirements with highest business value each iteration. </li></ul><ul><li>Risk reduction - working code delivered every iteration with multiple short release phases. </li></ul><ul><li>Quality - reduced defects due to disciplined practices and constant collaboration between project team members and business partners. </li></ul><ul><li>‘ One Team’ - better alignment between the Business and Information Technology. </li></ul>The benefits of Agile
    5. 5. Why Agile? Source: http:// www.versionone.com/
    6. 6. Some Agile key practices Source: Swan, Brian (uk.builder.com)
    7. 7. <ul><li>Agile Adoption </li></ul><ul><li>for the Enterprise </li></ul>
    8. 8. <ul><ul><li>Availability of customer representatives (SME’s) for requirements workshops, daily stand up meetings, iteration planning, clarifications and decision making. </li></ul></ul><ul><ul><li>Management support – particularly for technology teams new to Agile. </li></ul></ul><ul><ul><li>Talent and Social Engineering </li></ul></ul><ul><ul><ul><li>Capable team members with good cultural fit. </li></ul></ul></ul><ul><ul><ul><li>Common goals and collective project ownership. </li></ul></ul></ul><ul><ul><ul><li>Willing to try a different approach to software delivery which they are continuously improving. </li></ul></ul></ul><ul><ul><ul><li>Smaller co-located project teams are more suitable for Agile development projects to allow for effective communication. </li></ul></ul></ul><ul><ul><li>Agile coach - at least one resource within the project team with extensive Agile experience. </li></ul></ul>Agile critical success factors
    9. 9. <ul><li>&quot;significant design decisions that shape a system, where significant is measured by cost of change&quot; </li></ul><ul><li>-- Grady Booch </li></ul>What is Architecture?
    10. 10. <ul><ul><li>last responsible moment </li></ul></ul>Architecture considerations
    11. 11. <ul><ul><li>Working software over comprehensive documentation </li></ul></ul><ul><ul><li>while there is value in comprehensive documentation, we value working software more. </li></ul></ul>Agile Groups value
    12. 12. <ul><ul><li>architect is a role </li></ul></ul>Architecture considerations
    13. 13. <ul><li>? </li></ul>? ? ? ? ? ? ? ? Questions
    14. 14. <ul><li>Benn Wheeler </li></ul><ul><li>[email_address] </li></ul><ul><li>http:// au.linkedin.com/in/bennwheeler </li></ul><ul><li>Reginald de Silva </li></ul><ul><li>[email_address] </li></ul><ul><li>http://au.linkedin.com/in/regdesilva </li></ul><ul><li>Mark Mansour </li></ul><ul><li>[email_address] </li></ul><ul><li>http:// au.linkedin.com/in/markmansour </li></ul>Contacts
    15. 15. <ul><li>Agile software development </li></ul><ul><li>Using Agile software development – part 1 </li></ul><ul><li>Using Agile software development – part 2 </li></ul><ul><li>Using Agile software development – part 3 </li></ul><ul><li>Agile development - Version One </li></ul><ul><li>Agile manifesto </li></ul><ul><li>Agile modeling </li></ul><ul><li>Behaviour Driven Development definition </li></ul><ul><li>Behaviour Driven Development </li></ul><ul><li>Introducing BDD </li></ul><ul><li>Kano Analysis </li></ul><ul><li>Parking Lot Diagrams </li></ul><ul><li>Planning Poker </li></ul>More information…

    ×