Your SlideShare is downloading. ×
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,075

Published on

Published in: Technology, Business
1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,075
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
    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.
  • 7. Ceremonies
    Scrum Framework
    Roles
    Artifacts
  • The Scrum Framework - Roles
    Ceremonies
    Roles
    Artifacts
    • Product backlog
    • 23. Sprint backlog
    • 24. Burndown charts
  • Scrum Roles
    Management:
    Strategy & Vision
    Allocate resources
    Address escalated issues
    Product Owner:
    Defines and prioritize features
    Sets the DONE criteria
    Scrum Team:
    Cross functional
    Commitsto what it can do
    Manages itself and its work
    Gives a demo of their work
    Scrum Master:
    Ensures team is fully functional
    Is not a project manager
    Removes impediments
  • 25. Who does what?
  • 26. The chicken and the pig
  • 27. The Scrum Framework - Ceremonies
    Roles
    Artifacts
    Ceremonies
  • Sprint Planning – not the meeting meeting
    Product Backlog
    Team Capabilities
    Business Conditions
    Technology
    Current Product
    Product Owner
    Scrum Team
    Management
    Customers
    Sprint Planning
    Meeting
    Sprint Goal
    Sprint Backlog
    We should use 5% of our sprint time on this.
    At most workplaces, 10% of the sprint is time boxed for this meeting.
  • 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
  • 46. Scrum Framework - Artifacts
    Roles
    Ceremonies
    Artifacts
  • Product Backlog
    This is the product 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?

×