Scrum Events

Question 1

Waht are the Scrum events in a Sprint

Answer 1

Each scrum project delivers final product after a number of cycles called Sprints.
- Events in a Sprint includes
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective

Question 2

Waht are the increments in a Scrum project

Answer 2

1. An increment is developed in each sprint, which could be potentially be released.
2. An increment may or may not be released at the end of sprint but is must be potentially rerleasable.
3. Customer rerquest changes when they see increment (sprint review) and we apply changes in product backlog.

Question 3

What is the characters of Sprint

Answer 3

1. Sprint is time-boxed event, its duration should be fixed at beginning of the project.
2. Items in sprint backlog should not change after sprint gets started.
3. Sprint goal should not change at all.
4. The PO and Scream team might try to negotiate scope as more is learned.
5. Each user story in product backlog should be developed in a single sprint.
6. Important to agree on definition of “Done” at beginning of project. A 99.9% completed item is not considered “Done”.
7. “Non-Done” items will not be part of increment and demonstrated to customer at Sprint meeting.

Question 4

How to consider Sprint Time Boxes

Answer 4

1. Most companies uses sprint time boxes of 2-4 weeks.
2. If using time box larger than one month then unapplied changes will become too large to add complexity and risk.
3. Sprint should not be short, else we will not be able to deliver final product.

Question 5

Can Sprint be cancelled?

Answer 5

1. The PO has authority to cancel a sprint. This can happen when sprint becomes obsolete, due to changes in product backlog, strategies etc.
2. When cencelled, items “Done” will be reviewed and accepted and rest will be put back in product backlog.

Question 6

What is the timing for Sprint Planning

Answer 6

1. The Scrum team no need to wait until 100% product backlog completion.
2. The PO and Scrum team can start the first sprint when there are user stories items with measurement.
3. The first thing in each sprint is Sprint Planning. All 3 role (core team) should attend the meeting.
4. Scrum team estimate the work items that can be done in single sprint.
5. PO has ranked and ordered product backlog based on value of items.
6. PO also ensure tha user stories are easy to understand.

Question 7

What Scrum team needs to do in the Sprint Planning

Answer 7

1. Scrum team selectes the user stories from top of product backlog and puts them in sprint backlog.
2. Estimation of amount of work is done by Scream team.
3. Scrum team should create a sprint goal. Ex: We are goint to enable parts of product to set up login process., This makes other features of product more useful to customer and potential change request will be raised soon.

Question 8

What the Spring backlog looks like after Spring Planning Meeting

Answer 8

1. Sprint Backlog will be ready at the end of meeting and scrum team will be able to deliver through sprint.
2. User Story Ex:
   
   • Title: Login Process
   • ID: 250
     -Estimate: 9
   • Importance: 80
   • When user enteres the username and password, they will be taken to dashboard.
   • Task: 250-1, 250-2
3. Backlog Ex:
   
   • Sprint Goal
   • ToDo
   • Doing
   • Done