1. Agile Writer Girish Mahadevan www.gpod.in youtextme@gmail.com

2. Basics What is Agile? It’s a method based on iterative development. Why Agile? 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. 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.

3. The Agile Manifesto – a statement of values Process and tools Individuals and interactions Following a plan Responding to change Comprehensive documentation Working software Contract negotiation Customer collaboration over over over over Source: www.agilemanifesto.org

4. Iterative development process Product Backlog Product Backlog Product Backlog Product Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint Backlog Sprint 1 Sprint 2 Sprint 3 Sprint 4 …. Sprint N Features Features Features Features Features Features Features Features Features Features Features Features Features Features Features Features

5. Agility via Prioritized Backlog

6. Scrum Framework Daily Scrum Meeting S P R I N T 24 hours Backlog tasks expanded by team Potentially Shippable Product Increment 8 10 days Sprint Backlog Product Backlog As prioritized by Product Owner Product is designed, coded, tested and documented during the sprint.

8. ScrumMaster

9. Team

10. Sprint planning

11. Sprint review

12. Sprint retrospective

13. Daily scrum

14. Product backlog

15. Sprint backlog

17. Sprint review

18. Sprint retrospective

19. Daily scrum meeting

20. Product owner

21. ScrumMaster

23. Sprint backlog

25. Who does what?

26. The chicken and the pig

28. ScrumMaster

29. Team

30. Product backlog

31. Sprint backlog

32. Burndown charts

33. Sprint planning

34. Daily scrum

35. Sprint review

37. Sprint Planning board

38. Sprint Tasks in General

39. Daily Scrum

40. Daily Scrum – Minutes of Meeting

41. Say it right

42. Sprint review meeting

43. Sprint review meeting tasks

44. Sprint velocity After 3 to 5 sprints, velocity can be used to estimate completion dates.

45. Sprint Retrospective

47. ScrumMaster

48. Team

49. Sprint planning

50. Sprint review

51. Sprint retrospective

52. Daily scrum meeting

53. Product backlog

54. Sprint backlog

56. Backlog Grooming

57. The Sprint Backlog

58. Sprint notes

59. Burn down Chart Perfect scrum, No one home, Overestimation and Underestimation

60. Again, why daily? How does a project get to be a year late? One day at a time Can Scrum meetings be replaced by emailed status reports? No Entire team sees the whole picture every day Create peer pressure to do what you say you’ll do

61. Typical Sprint Sprint Planning & Retrospective 10% Sprint work 80% Backlog refinement 5% Sprint Review 5% 2 weeks

62. Writer’s Role

63. Documentation review cycle

64. What’s so different for an Agile writer

65. Project Management Techniques

66. Scaling – What it’s not

67. Scrum of Scrums / Meta-Scrum Scrum Master Product Owner Scrum team member

68. How do I propose Agile in my organization

69. Basic truth about People

70. Basic truth about performance

71. Good reads Agile and Iterative Development: A Manager’s Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber User Stories Applied for Agile Software Development by Mike Cohn Lots of weekly articles at www.scrumalliance.org BUY BOOKS ONLINE at the AGILE FOR ENTERPRISE ORGANIZATIONS web store (http://astore.amazon.com/agilescrumsoftwaredevelopment-20)

72. Catch me if you can girish.mahadevan@facebook.com www.gPod.in

73. Let’s scrum? Any questions?