1.Agile Methodology(SCRUM) Khushbu Desai(07030244003)

2. Agile Manifesto (2001)

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 interactionoverprocesses and tools

Working SoftwareoverComprehensive Documentation

Customer collaborationovercontract negotiation

Responding to changeoverfollowing a plan

That is, while there is value in the items on

the right, we value the items on the left more .

3. Principal #1:Individuals and interactionoverprocesses and tools 4. Principal #2: Working SoftwareoverComprehensive Documentation Requirements Gathering Use Cases / Scenarios Functional Specs Design Specs Code Integrate Test Fix User Stories / Project Plan Iteration 1 Iteration 2 Iteration 3 Iteration 4 Design /Code / Test Stories for Next Iteration 5. Principal #3: Customer collaborationovercontract negotiation 6. Principal #4: Responding to changeoverfollowing a plan 7. Total TransparencyAt any time the status of the project is visible for everybody 8. Scrum Basics Pete Deemer CPO, Yahoo! India R&D 9. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 7 8 9 10 11 12 1 2 3 4 5 6 13 10. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 11. Product Owner

Responsible for the overall project vision and goals

Responsible for managing project ROI vs. risk

Responsible for taking all inputs into what the team should produce, and turning it into a prioritized list (the Product Backlog)

Participates actively in Sprint Planning and Sprint Review meetings, and is available to team throughout the Sprint

Determines release plan and communicates it to upper management and the customer

12. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 13. Team

7 people, + or 2

• Has worked with as high as 15, as few as 3

• Can be shared with other teams (but better when not)

• Can change between Sprints (but better when they dont)

• Can be distributed (but better when colocated)

Cross-functional

• Possesses all the skills necessary to produce an increment of potentially shippable product

• Team takes on tasks based on skills, not just official role

Self-managing

• Team manages itself to achieve the Sprint commitment

14. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 15. The Role of the ScrumMaster

The ScrumMaster does everything in their power to help the team achieve success

This includes:

• Serving the team

• Protecting the team

• Guiding the teams use of Scrum

16. What the ScrumMaster Does

Serves the team

• The ScrumMaster takes action to help remove impediments to the teams effectiveness

• The ScrumMaster facilitates the teams group interactions, to help the team achieve its full potential

Protects the team

• The ScrumMaster protects the team from anything that threatens its effectiveness, such as outside interference or disruption

• The ScrumMaster will need to confront uncomfortable issues, both inside and outside the team

Guiding the teams use of Scrum

• The ScrumMaster teaches Scrum to the team and organization

• The ScrumMaster ensures that all standard Scrum rules and practices are followed

• The ScrumMaster organizes all Scrum-related practices

17. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 18. Product Backlog Product Owner lists items in descending order of priority (highest priority item is listed first, next-highest is second, etc.) Size estimates are rough estimates (can either be arbitrary points, or ideal days) 19. Product Backlog

List of everything that could ever be of value to the business for the team to produce

Ranked in order of priority

• Priority is a function of business value versus risk

Product Owner can make any changes they want before the start of a Sprint Planning Meeting

• Items added, changed, removed, reordered

How much documentation is up to the team and Product Owner to decide

The farther down the list, the bigger and less defined the items become

• ~2 Sprints worth are defined in detail

20. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment Product Backlog 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 21. Sprint Planning Meeting

Takes place before the start of every Sprint

Team decideshow much Product Backlog it will commit to complete by the end of the Sprint, and comes up with a plan and list of tasks for how to achieve it

Whats a good commitment?

• Clearly understood by all

• Shared among the team

• Achievable without sacrificing quality

• Achievable without sacrificing sustainable pace

Attended by Team, Product Owner, ScrumMaster, Stakeholders

May require 1-2 hours for each week of Sprint duration

• 2 week Sprint = 2-4 hours, 4 week Sprint = 4-8 hours

22. Sprint Pre-Planning Meeting

Not textbook Scrum, but many teams find it useful

Takes place several days before the end of a Sprint (and start of the next Sprint

Product Owner spends an hour walking the team through the items at the top of the Product Backlog for thenextSprint

Team asks questions, requests clarification, recommend items to be broken down further

Weds Thurs Fri Mon Tues Pre-Meeting for Sprint 4 Review & Retrospective for Sprint 3 (afternoon) Sprint Planning Meeting for Sprint 4 (morning) Sprint 4 Begins 23. The Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book in shopping cart Design business logic Sanjay 4 Design user interface Jing 2 Implement back-end code Tracy 2 Implement front-end code Tracy 6 Complete documentation Joe 8 Unit testing Philip 4 Regression testing Philip 2 Upgrade transaction processing module Implement back-end code Tracy 5 Complete documentation Joe 6 Unit testing Philip 3 Regression testing Philip 3 Total 214 24. Daily Scrum Meeting

Every weekday

Whole team attends

Everyone stands

Lasts 15 minutes or less

Everyone reports 3 things only to each other

• What was I able to accomplish since last meeting

• What will I try to accomplish by next meeting

• What is blocking me

No discussion, conversation until meeting ends

Product Owner can attend and report

Update of artifacts after standup

25. Table Exercise: Daily Scrum Meeting

Do a Daily Scrum Meeting for your table

• One person plays the role of ScrumMaster

• The rest of the table are team-members

Each team-member reports to the group:

• What I was able to get done since last Daily Standup Meeting

• What I willtryto get done by the next Daily Standup Meeting

• What is blocking me? (If nothing, say No Blocks)

But there is a twist

26. Updating the Sprint Backlog

Before or after the Daily Scrum, team members update the hours remaining on the Sprint Backlog

27. Updating the Sprint Backlog Day of Sprint Backlog Item Task Owner Initial Est. 1 2 3 4 5 6 Enable all users to place book in shopping cart Design business logic Sanjay 4 2 0 Design user interface Jing 2 2 2 Implement back-end code Tracy 2 4 2 Implement front-end code Tracy 6 6 6 Complete documentation Joe 8 6 6 Unit testing Philip 4 3 3 Regression testing Philip 2 2 2 Upgrade transaction processing module Implement back-end code Tracy 5 10 8 Complete documentation Joe 6 6 6 Unit testing Philip 3 3 3 Regression testing Philip 3 2 2 Total 214 220 205 28. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 29. Sprint Review

Purpose of the Sprint Review is

• Demo what the team has built

• Generate feedback, which the Product Owner can incorporate in the Product Backlog

Attended by Team, Product Owner, ScrumMaster, functional managers, and any other stakeholders

Ademo ofwhats been built, not apresentation aboutwhats been built

• no Powerpoints allowed!

Usually lasts 1-2 hours

Followed by Sprint Retrospective

30. The Basics of Scrum No Changes (in Duration or Deliverable) Commitment 4-Week Sprint Potentially Shippable Product Product Owner Review Scrum Master The Team 7 8 9 10 11 12 1 2 3 4 5 6 13 Daily Scrum Meeting Retrospective 31. Sprint Retrospective

What is it?

• 1-2 hour meeting following each Sprint Demo

• Attended by Product Owner, Team, ScrumMaster

• Usually a neutral person will be invited in to facilitate

• Whats working and what could work better

Why does the Retrospective matter?

• Accelerates visibility

• Accelerates action to improve

32. Velocity Based on Historical Data Teams Recent Sprints 90 points 120 points 100 points ~105 size points per Sprint 33. Thank You