Agile in a Nutshell Delivering more value faster at less cost
Who am I? Consultant. Coach. Storyteller. Games Maker. VP of Learning and Development My Blog:  www.selfishprogramming.org
...it’s an adventure!
Agile Principle #1: Deliver value
Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a  presenter </li></ul><u...
Agile Principle #2: Respect for people
Pick a project <ul><li>Identify 3 challenges the project faces </li></ul><ul><li>Share these with a friend </li></ul><ul><...
Pop Quiz Question #1 Time Cost Scope ?
Pop Quiz Question #2 “ Without a goal it’s difficult to score” ?
Pop Quiz Question #3 “ Show me the value!” ?
Agile Principle #3: Eliminate wa ste
Agile Principle #1: Deliver value
Value in a Waterfall Project Value in an Agile Project
Why adopt Agile? <ul><li>1. Desperation : To survive against fierce competition as competitors deliver higher quality deli...
What is Agile?
What is Agile? “ Agile is now widely recognised as a  project delivery and general working approach  with a  proven track ...
Where does Agile come from? Agile Manifesto Snowbird, Utah Feb. 2001 Your turn? 14 October 2010 First man on the moon Jul....
The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through thi...
eXtreme Programming (XP) Scrum Lean Software Development Feature Driven Development Adaptive Systems Development Dynamic S...
Think “Team”
 
Agile in Action
Agile Project Structure Release 1 – 12 weeks Iteration 1 – 4 weeks Project 1 – many weeks
Agile Requirement User Story
Anatomy of a User Story AS A  <role> I NEED  <capability> SO THAT  <achieve some goal> <ul><li>Binary question format (Y/N...
Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a  presenter </li></ul><u...
About User Stories User Story Epic
About User Stories User Story Epic Project Backlog
Make stories even-sized User Story Epic Project Backlog Project Backlog
Stories at different levels of granularity Release 1 – 12 weeks Iteration 1 – 4 weeks Project 1 – many weeks Iteration Lev...
Themes – Story Groupings Project Backlog World Peace Sustainable Philanthropy
Definition of Done User Story Acceptance Criteria Acceptance Tests
Quality is not negotiable 
The XP Game Team Manifesto Team Speed Networking Kanban Board Building Celebratory Team Lunch Show & Tell User Story Writi...
Agile Heartbeat Tuesday Tuesday Tuesday <ul><li>Show & Tell </li></ul><ul><li>Iteration Retrospective </li></ul><ul><li>De...
VELOCITY AS A MEASURE OF WORK
Velocity Burndown Chart # of Iteration Level Stories Iteration Days
Agile Principle #1: Deliver value
Agile Values Communication Simplicity Feedback Courage Respect
Team Manifesto
Agile Principle #4: Continuous Learning
The Agile Challenge Pros ☺  Value-driven: Business Value + Agile Values ☺  Team-centric ☺  Working a sustainable pace (9 –...
Agile Principle #5: Continuous Improvement
In Summary
Agile Principle #1: Deliver value
Agile Principle #2: Respect for people
Agile Principle #3: Eliminate wa ste
Agile Principle #4: Continuous Learning
Agile Principle #5: Continuous Improvement
Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a  presenter </li></ul><u...
The Gift of Feedback
Further Information Consultant. Coach. Storyteller. Games Maker. Resources Courses on Agile  including Agile Project Manag...
Upcoming SlideShare
Loading in...5
×

Agile in a Nutshell

7,827

Published on

Presented at International Institute of Business Analysis (IIBA) UK Chapter on 14 October 2010: http://www.selfishprogramming.com/2010/10/05/iiba-uk-chapter-event-14-october-2010/

Published in: Business

Agile in a Nutshell

  1. 1. Agile in a Nutshell Delivering more value faster at less cost
  2. 2. Who am I? Consultant. Coach. Storyteller. Games Maker. VP of Learning and Development My Blog: www.selfishprogramming.org
  3. 3. ...it’s an adventure!
  4. 4. Agile Principle #1: Deliver value
  5. 5. Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a presenter </li></ul><ul><li>I need to give an introduction to Agile concepts </li></ul><ul><li>So that participants better understand how Agile can increase the </li></ul><ul><li>value they deliver. </li></ul><ul><li>Acceptance Criteria: </li></ul><ul><li>[ ] We understand the core concepts of Agile. </li></ul><ul><li>[ ] We have identified two or more ideas to try out Agile at work. </li></ul><ul><li>[ ] We have had fun. </li></ul>
  6. 6. Agile Principle #2: Respect for people
  7. 7. Pick a project <ul><li>Identify 3 challenges the project faces </li></ul><ul><li>Share these with a friend </li></ul><ul><li>Share these with the group </li></ul>
  8. 8. Pop Quiz Question #1 Time Cost Scope ?
  9. 9. Pop Quiz Question #2 “ Without a goal it’s difficult to score” ?
  10. 10. Pop Quiz Question #3 “ Show me the value!” ?
  11. 11. Agile Principle #3: Eliminate wa ste
  12. 12. Agile Principle #1: Deliver value
  13. 13. Value in a Waterfall Project Value in an Agile Project
  14. 14. Why adopt Agile? <ul><li>1. Desperation : To survive against fierce competition as competitors deliver higher quality deliverables faster </li></ul><ul><li>2. Frustration : From the burden of legacy processes and not enough value being delivered </li></ul><ul><li>3. Fear : Of being left behind as Agile becomes the de facto way of working more efficiently and effectively </li></ul><ul><li>4. Hope : The belief there must be a better way of doing things that would reduce waste, deliver more value and make work meaningful </li></ul><ul><li>5. Desire for Continuous Improvement : To go from Mediocrity to Good to Great </li></ul>
  15. 15. What is Agile?
  16. 16. What is Agile? “ Agile is now widely recognised as a project delivery and general working approach with a proven track record of delivering more business value faster through higher quality deliverables in comparison to traditional methodologies. ”
  17. 17. Where does Agile come from? Agile Manifesto Snowbird, Utah Feb. 2001 Your turn? 14 October 2010 First man on the moon Jul. 1969
  18. 18. The Agile Manifesto 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. www.agilemanifesto.org
  19. 19. eXtreme Programming (XP) Scrum Lean Software Development Feature Driven Development Adaptive Systems Development Dynamic Systems Development Method (DSDM) Crystal Kanban ...... Different kinds of Agile
  20. 20. Think “Team”
  21. 22. Agile in Action
  22. 23. Agile Project Structure Release 1 – 12 weeks Iteration 1 – 4 weeks Project 1 – many weeks
  23. 24. Agile Requirement User Story
  24. 25. Anatomy of a User Story AS A <role> I NEED <capability> SO THAT <achieve some goal> <ul><li>Binary question format (Y/N) </li></ul><ul><li>Statement </li></ul><ul><li>Given-When-Then </li></ul>BV Effort <Title> Acceptance Criteria:
  25. 26. Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a presenter </li></ul><ul><li>I need to give an introduction to Agile concepts </li></ul><ul><li>So that participants better understand how Agile can increase the </li></ul><ul><li>value they deliver. </li></ul><ul><li>Acceptance Criteria: </li></ul><ul><li>[ ] We understand the core concepts of Agile. </li></ul><ul><li>[ ] We have identified two or more ideas to try out Agile at work. </li></ul><ul><li>[ ] We have had fun. </li></ul>
  26. 27. About User Stories User Story Epic
  27. 28. About User Stories User Story Epic Project Backlog
  28. 29. Make stories even-sized User Story Epic Project Backlog Project Backlog
  29. 30. Stories at different levels of granularity Release 1 – 12 weeks Iteration 1 – 4 weeks Project 1 – many weeks Iteration Level Story Release Level Story Project Level Story
  30. 31. Themes – Story Groupings Project Backlog World Peace Sustainable Philanthropy
  31. 32. Definition of Done User Story Acceptance Criteria Acceptance Tests
  32. 33. Quality is not negotiable 
  33. 34. The XP Game Team Manifesto Team Speed Networking Kanban Board Building Celebratory Team Lunch Show & Tell User Story Writing Technical Design Walkthru Collaboration in Action
  34. 35. Agile Heartbeat Tuesday Tuesday Tuesday <ul><li>Show & Tell </li></ul><ul><li>Iteration Retrospective </li></ul><ul><li>Design </li></ul><ul><li>Development </li></ul><ul><li>Test </li></ul><ul><li>Iteration Planning </li></ul><ul><li>Release Planning </li></ul><ul><li>Mid-Iteration Review </li></ul><ul><li>Agile Estimating </li></ul><ul><li>Pre-Planning </li></ul><ul><li>Backlog Grooming </li></ul><ul><li>User Story Writing </li></ul><ul><li>Daily Standup </li></ul><ul><li>Scrum of Scrums </li></ul>Ongoing iterative activities throughout the sprint
  35. 36. VELOCITY AS A MEASURE OF WORK
  36. 37. Velocity Burndown Chart # of Iteration Level Stories Iteration Days
  37. 38. Agile Principle #1: Deliver value
  38. 39. Agile Values Communication Simplicity Feedback Courage Respect
  39. 40. Team Manifesto
  40. 41. Agile Principle #4: Continuous Learning
  41. 42. The Agile Challenge Pros ☺ Value-driven: Business Value + Agile Values ☺ Team-centric ☺ Working a sustainable pace (9 – 5 everyday) ☺ Responsive to change through iterative planning and estimating ☺ Deliver high business value ☺ Deliver faster ☺ Fun! GOOD Very GOOD BAD VERY BAD Iteration 0 Iteration 1 Iteration 2 Iteration 3 <ul><li>Cons </li></ul><ul><li>Must understand the Business Value you are delivering </li></ul><ul><li>Must want to work with people </li></ul><ul><li>Focused work makes Agile very tiring </li></ul><ul><li>Must be able to embrace uncertainty by adapting to change </li></ul><ul><li>Prioritise by Business Value first, then re-prioritise by constraints </li></ul><ul><li>Define scope by Minimum Marketable Feature Set instead of by want </li></ul><ul><li>Making work fun is hard work! </li></ul>Agile Experience Retrospective
  42. 43. Agile Principle #5: Continuous Improvement
  43. 44. In Summary
  44. 45. Agile Principle #1: Deliver value
  45. 46. Agile Principle #2: Respect for people
  46. 47. Agile Principle #3: Eliminate wa ste
  47. 48. Agile Principle #4: Continuous Learning
  48. 49. Agile Principle #5: Continuous Improvement
  49. 50. Session Goal and Acceptance Criteria <ul><li>Introduction to Agile Concepts </li></ul><ul><li>As a presenter </li></ul><ul><li>I need to provide an introduction to Agile concepts </li></ul><ul><li>So that participants better understand how Agile can increase the </li></ul><ul><li>value they deliver. </li></ul><ul><li>Acceptance Criteria: </li></ul><ul><li>[ ] We understand the core concepts of Agile. </li></ul><ul><li>[ ] We have identified two or more ideas to try out Agile at work. </li></ul><ul><li>[ ] We have had fun. </li></ul>
  50. 51. The Gift of Feedback
  51. 52. Further Information Consultant. Coach. Storyteller. Games Maker. Resources Courses on Agile including Agile Project Management and Customer Value Analysis http://www.emergn.com The Original XP Game by Pascal Van Cauwenberghe and Vera Peeters http://www.xp.be/xpgame.html Scrum and XP in the Trenches by Henrik Kniberg www.infoq.com Fun and Games http://www.agilecoach.net/ Conferences XP Days Benelux (25 – 26 November 2010) http://www.xpday.net/ XP Day London (December 2010) http://www.xpday.org/ VP of Learning and Development My Blog: www.selfishprogramming.org My email: portia.tung@emergn.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×