Scrum Meets

2010 Q1.1 Scrum Meetings 1

Scrum Meets

Sprint Plan Meet

Daily Standup Meet

Triage Meet

Sprint Review Meet

Sprint Retrospection Meet


Sprint Plan – Daily Standup – Sprint Review

What we do in Sprint Plan MeetHow we do Story Point EstimationHow we calculate Story HoursBurndown and Velocity

What I do in Daily Standup Call

Is Triage Meet required?

How we conduct Sprint Review MeetingSprint Retrospection Discussion


Sprint Planning Team hours available

Set sprint goal

Definition of DONE

Estimate Effort for backlog stories having priority

Freeze stories / tasks for Sprint

Sprint Backlog sign-off


Calculate available hours

Name Hours / Day Days in office Total Hours

Akbar 7.6 9 69

Vamsi 8 10 80

Anoop 4 10 40

Rich 8 8 64

Sridevi 8 10 80

Total Team Hrs 333

Work Day DateAvailable

Hours

1 15-Mar 8

2 16-Mar 8

3 17-Mar 8

4 18-Mar 8

5 19-Mar 5

6 22-Mar 0

7 23-Mar 8

8 24-Mar 8

9 25-Mar 8

10 26-Mar 8

Total Hrs. 69

Average Hrs. 7.66

Akbar

iGen Team Sprint4

Team availability for Sprint4 is 320 Hours

Engineers calculate their available hours for sprint. Update your Scrum Master Scrum Master update Sprint Time Sheet for total team availability Estimate Effort for backlog stories having priority


Set Sprint Goal Short description of what the current sprint will attempt to

achieve

“Installer (setup.exe) functionalities for iGen upgrade and uninstall”


List out ‘Definition of Done’

Construction approach discussed with teamCode construction is complete with standardsUnit testcases updated and executed for the modulePeer review doneSource checked-in to local CVSFunctionality verified in nightly buildStory documented with flowchart and UML diagramSource merged to Main TruncReady for demo

Non-Functional Requirements:All pages should be fully loaded within 2 secondsAll pages should support 200 simultaneous user sessions

Story is ‘Done’ only when it passes all verification in DOD. Else treated incomplete.

Applicable to all stories in sprint backlog

Story Estimation

Fibonacci Numbers Complexity, Size, Uncertainty Planning Poker Set Story Point Split into tasks Estimate Hours


Fibonacci was known in his time and is still recognized today as the "greatest European mathematician of the middle ages."

He was one of the first people to introduce the Hindu-Arabic number system into Europe

The sequence, in which each number is the sum of the two preceding numbers is known as the Fibonacci series: 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, …

The Fibonacci sequence, generated by the rule f1 = f2 = 1 , fn+1 = fn + fn-1

The Fibonacci numbers are Nature's numbering system. They appear everywhere in Nature, from the leaf arrangement in plants, to the pattern of the florets of a flower, the scales of a pineapple, growth of every living thing, including a single cell, a grain of wheat, a hive of bees, and even all of mankind.

0 1 1 2 3 5 8 13 21 Big!


Fibonacci Numbers

Estimate each story by discussing its:

Complexity Structural Complexity

Size Step away from answering "how long will it take“ Care about "how big is the job“ Estimated size of the problem does not change when applied to one team

vs. another. The size of the problem is the same, regardless of how fast each could tackle the problem.

Uncertainty Increases with number of choices


Play Planning Poker

Every developer will get cards with Fibonacci numbers. Then Scrum Master will select first story. Every developers and testers will

estimate Story size Point = Complexity X Size X Uncertainty

Sridevi =

Vamsi =

Anoop =

Show cards at a time. Talk about High & Low numbers Repeat until everyone agrees on just one number.


21 BIG1385321 ?

3

5

13


Estimate in Hours

Split Story into Tasks Make sure your tasks are small enough to track the work

that’s being done Estimate hours for each task. Sum up.

Let us Estimate User Story 1 – “As a user I want to save file to disk, that I downloaded using Curl library“ –

Story Point 2

User Story 2 – “I as a user want I need to get registered as new user and get notified on status“ – Story Point ________

User Story 3 – “I as a registered user want I need to change my password on my first login“ – Story Point ________

Exercise

Assign Story Point to Story2 and Story3Discuss on Each Stories Acceptance Criteria, Technical issues foreseen. Get clarified with PO or SM.valuate by numbers that are relative to Estimated story


21 BIG1385321 ?


Update Sprint Plan sheet

StoryID Story Owner Status ActualHrs

EstimatedHrs

Day 1

Day 2

Day3

Day 4

Day 5

#873 Feature1 Eng 1 Done 16 4 4 16 12 8 0

#652 Feature2 Eng 2 Active 8 8 7 7 4 2

#622 Feature3 Active

#622-1 Task1 Eng 1 Active 4 4 4 3 1 1

#622-2 Task2 Eng 2 Active 5 5 5 2 2 2

#622-4 Task4 Eng 2 Done 8 16 16 16 8 2 0

#622-3 Task3 Eng 3 Done 4 0 0 0 4 0 0

#639 Feature4 Eng 4 Done 4 4 4 4 3 3 0

Total 41 52 39 20 5


Track your Burndown chartID Category Story Owner Status Actual

HrsEstimatedHrs

Day 1

Day 2

Day3

Day 4

Day 5

Day …

S1 Setup Setup st1 Eng 1 Done 16 4 4 16 12 8 0 0

D1

DB Schema DB st1 Eng 2 Active 8 8 7 7 4 2 2

Total 50 50 48 44 43 34


Burndown chart Update the amount of time remaining to complete

each of the tasks

Record this information on a graph called the Sprint Burndown Chart.

It shows, each day, how much work (measured in hours) remains until the team’s commitment is completed.

Shows the team their actual progress towards their goal – and not in terms of how much time has been spent so far.


Team Velocity Velocity is a measurement of how much story points the

team had done in an iteration I can say my team’s Velocity is 33. Velocity measuring recommended after 3rd Sprint

Mean (Best 3) = 37

Mean (Last 3) = 33

Mean (Worst 3) = 28

0

10

20

30

40

1 2 3 4 5 6 7 8 9

Sprints

StoryPoints


Team Velocity What if sprint duration is unequal ? Sprint1 – 1 Wk, Sprint 2 – 4 Wks, Sprint 3&4 – 2 Wks Measure in Person Days

Duration Weeks W Days Engineers Person Days Leaves P DaysSprint1 1 6 3 18 1 17Sprint2 4 22 3 66 5 61Sprint3 2 13 3 39 3 36Sprint4 2 10 3 30 1 29


Scrum daily standup It’s the team’s opportunity to report to itself on progress and

obstacles Short (10 minute) meeting that happens every workday at

an appointed time Everyone stands

Anoop Daily standup 19-Mar-10

Today #8421 Report describing all images used in iGen portal.. - DONE#8410 Admin page template design…5 hrs remaining - ACTIVE

Tomorrow #8410 Admin page font color fix# May be late to office tomorrow… By 2 hrs. Anyway I’ll try to compensate that within sprint.

Blockers My XIG mailbox overflows. Increase my mailbox size.Color code for Admin page fonts not received yet. Notified Rich, but no response yet.

Support 1 Hr.


Set ‘Triage Call’

Making sure the task has enough information for the developers and makes sense

Making sure the task status is as expected

Making sure the bug / task has sensible "Severity" and "Priority" fields. If not re-prioritize those ▪ Priority is Business▪ Severity is Technical


Sprint review

The team demos what they’ve built during the Sprint

This is not a “presentation” the team gives – there are no PowerPoints

Show what’s been built and get feedback

Product owner, team members, stakeholders and anyone else interested can show for this review meet


Sprint review / retrospection It’s an opportunity for the team to discuss what’s working

and what’s not working, and agree on changes to try.

iGen Sprint Review Sprint4

Plus Minus Action Items

Sprint goal met

Good feedback for demo

Customer not happy with coding standards

Introduce process for internal code review

Daily standup takes long

Take technical discussions off-line.

iGen Sprint Retrospection Sprint4

Plus Minus Action Items

Productivity has increased compared to Sprint3

Late night scrum-of-scrum

Discussion required with onsite coordinator

More Unplanned leave

Pre-notice required

Audio bridge not clear most of the times

Contact Call Centre. Change bridge.


Thank You !- Krishnakumar B (40103434)

- Scrum Master, Xerox Innovation Group.

Scrum Meets

Documents

Transcript of Scrum Meets