Your SlideShare is downloading. ×
0
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Agile writer
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile writer

4,092

Published on

Published in: Technology, Business
1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,092
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
351
Comments
1
Likes
6
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile Writer<br />Girish Mahadevan<br />www.gpod.in<br />youtextme@gmail.com<br />
  • 2. Basics<br />What is Agile?<br />It’s a method based on iterative development.<br />Why Agile?<br />The goal is not to release things faster for the sake of it. It is to achieve nimbleness and agility to deliver on the company’s strategy as it moves forward and/or tactically changes.  <br /> <br />It is about creating more business opportunities for ourselves rather than being cased into a model that requires our resource commitment for a time window that is longer than what the market we’re competing in requires. <br />
  • 3. The Agile Manifesto – a statement of values<br />Process and tools<br />Individuals and interactions<br />Following a plan<br />Responding to change<br />Comprehensive documentation<br />Working software<br />Contract negotiation<br />Customer collaboration<br />over<br />over<br />over<br />over<br />Source: www.agilemanifesto.org<br />
  • 4. Iterative development process<br />Product<br />Backlog<br />Product<br />Backlog<br />Product<br />Backlog<br />Product<br />Backlog<br />Sprint<br />Backlog<br />Sprint<br />Backlog<br />Sprint<br />Backlog<br />Sprint<br />Backlog<br />Sprint<br />Backlog<br />Sprint 1<br />Sprint 2<br />Sprint 3<br />Sprint 4<br /> ….<br />Sprint N<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />Features<br />
  • 5. Agility via Prioritized Backlog<br />
  • 6. Scrum Framework<br />Daily Scrum<br />Meeting<br /> S P R I N T<br />24 hours<br />Backlog tasks<br />expanded<br />by team<br />Potentially Shippable<br />Product Increment<br />8 10 days<br />Sprint Backlog<br />Product Backlog<br />As prioritized by Product Owner<br />Product is designed, coded, tested and documented during the sprint.<br />
  • 7. Ceremonies<br />Scrum Framework<br />Roles<br />Artifacts<br /><ul><li>Product owner
  • 8. ScrumMaster
  • 9. Team
  • 10. Sprint planning
  • 11. Sprint review
  • 12. Sprint retrospective
  • 13. Daily scrum
  • 14. Product backlog
  • 15. Sprint backlog
  • 16. Burn down charts</li></li></ul><li>The Scrum Framework - Roles<br />Ceremonies<br />Roles<br /><ul><li>Sprint planning
  • 17. Sprint review
  • 18. Sprint retrospective
  • 19. Daily scrum meeting
  • 20. Product owner
  • 21. ScrumMaster
  • 22. Team</li></ul>Artifacts<br /><ul><li>Product backlog
  • 23. Sprint backlog
  • 24. Burndown charts</li></li></ul><li>Scrum Roles<br />Management:<br />Strategy & Vision<br />Allocate resources<br />Address escalated issues<br />Product Owner:<br />Defines and prioritize features <br />Sets the DONE criteria <br />Scrum Team:<br />Cross functional<br />Commitsto what it can do<br />Manages itself and its work<br />Gives a demo of their work<br />Scrum Master:<br />Ensures team is fully functional<br />Is not a project manager<br />Removes impediments<br />
  • 25. Who does what?<br />
  • 26. The chicken and the pig<br />
  • 27. The Scrum Framework - Ceremonies<br />Roles<br />Artifacts<br />Ceremonies<br /><ul><li>Product owner
  • 28. ScrumMaster
  • 29. Team
  • 30. Product backlog
  • 31. Sprint backlog
  • 32. Burndown charts
  • 33. Sprint planning
  • 34. Daily scrum
  • 35. Sprint review
  • 36. Sprint retrospective</li></li></ul><li>Sprint Planning – not the meeting meeting<br />Product Backlog<br />Team Capabilities<br />Business Conditions<br />Technology<br />Current Product<br />Product Owner<br />Scrum Team<br />Management<br />Customers<br /> Sprint Planning<br /> Meeting<br />Sprint Goal<br />Sprint Backlog<br /> We should use 5% of our sprint time on this.<br />At most workplaces, 10% of the sprint is time boxed for this meeting.<br />
  • 37. Sprint Planning board<br />
  • 38. Sprint Tasks in General<br />
  • 39. Daily Scrum<br />
  • 40. Daily Scrum – Minutes of Meeting<br />
  • 41. Say it right<br />
  • 42. Sprint review meeting<br />
  • 43. Sprint review meeting tasks<br />
  • 44. Sprint velocity<br />After 3 to 5 sprints, velocity can be used to estimate completion dates.<br />
  • 45. Sprint Retrospective<br />
  • 46. Scrum Framework - Artifacts<br />Roles<br />Ceremonies<br />Artifacts<br /><ul><li>Product owner
  • 47. ScrumMaster
  • 48. Team
  • 49. Sprint planning
  • 50. Sprint review
  • 51. Sprint retrospective
  • 52. Daily scrum meeting
  • 53. Product backlog
  • 54. Sprint backlog
  • 55. Burndown charts</li></li></ul><li>Product Backlog<br />This is the product backlog<br />
  • 56. Backlog Grooming<br />
  • 57. The Sprint Backlog<br />
  • 58. Sprint notes<br />
  • 59. Burn down Chart<br />Perfect scrum, No one home, Overestimation and Underestimation <br />
  • 60. Again, why daily?<br />How does a project get to be a year late?<br />One day at a time <br />Can Scrum meetings be replaced by emailed status reports?<br /> No<br />Entire team sees the whole picture every day<br />Create peer pressure to do what you say you’ll do<br />
  • 61. Typical Sprint<br />Sprint Planning & Retrospective<br />10%<br />Sprint work<br />80%<br />Backlog refinement<br />5%<br />Sprint Review<br />5%<br />2 weeks<br />
  • 62. Writer’s Role<br />
  • 63. Documentation review cycle<br />
  • 64. What’s so different for an Agile writer<br />
  • 65. Project Management Techniques<br />
  • 66. Scaling – What it’s not<br />
  • 67. Scrum of Scrums / Meta-Scrum<br />Scrum Master<br />Product Owner<br />Scrum team member<br />
  • 68. How do I propose Agile in my organization<br />
  • 69. Basic truth about People<br />
  • 70. Basic truth about performance<br />
  • 71. Good reads<br />Agile and Iterative Development: A Manager’s Guide by Craig Larman<br />Agile Estimating and Planning by Mike Cohn<br />Agile Project Management with Scrum by Ken Schwaber<br />Agile Retrospectives by Esther Derby and Diana Larsen<br />Agile Software Development Ecosystems by Jim Highsmith<br />Agile Software Development with Scrum by Ken Schwaber and Mike Beedle<br />Scrum and The Enterprise by Ken Schwaber<br />User Stories Applied for Agile Software Development by Mike Cohn<br />Lots of weekly articles at www.scrumalliance.org<br />BUY BOOKS ONLINE at the AGILE FOR ENTERPRISE ORGANIZATIONS web store (http://astore.amazon.com/agilescrumsoftwaredevelopment-20)<br />
  • 72. Catch me if you can<br />girish.mahadevan@facebook.com<br />www.gPod.in<br />
  • 73. Let’s scrum? Any questions?<br />

×