Scrum project cases (KR Gugi)

2008.10

Sam Hwang (PMO)

Yahoo! Presentation, Confidential

Scrum case: KR Gugi (Local)

Scrum Period 2007.12.11 ~ 2008.8.3 (8 Months) Sprint Length/cycle 30 weeks (141 Workdays)/a week Total Requests 241 (1.7 requests/day) Resolved Requests 197 (1.3 requests/day)

Scrum case: KR Gugi (Local)

Product Baklog
P4 P2 P1 P3 P3 P3 [Gugi 3.5] 3.5 [Gugi 3.5] 3.5 TechQA >> App. >> scanmus Sprint Start Date End Date 01 03 01 15 12 18 >> 3 12 ~ 4 13 (5)

Backlog
Excel template is efficient than tool Managed by PM Always put priority over backlog items. Dont start to do any works which are not listed in backlog except incident and s1 Issue Bugzilla ticket for all backlog items and put links on backlog to trace Include all product req., engineering tasks, innovation and meetings.

Scrum case: KR Gugi (Local)

Sprint planning meeting
Fix the meeting time: Every Friday afternoon with team Always pickup top priority of backlog first until fill teams capacity up Consider holidays, meetings, bugs fix; usually 4-5 hrs / a person / a day Estimate by team members (hr base) and take a full responsibility Estimate by hour base

Scrum case: KR Gugi (Local)

TO DO
burndown chart 220 200 180
Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Owner: Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Owner:` Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Owner:` Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

IN PROGRESS

DONE

hours of work remaining

160 140 120 100 80 60 40 20 0 Day 1 Day 2 Day 3 Day 4 Day 5

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

Owner: Sanjay Owner: Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Owner:` Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Owner:` Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Owner:` Sanjay Time Remaining: Time Remaining: 4 hrs 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Owner:` Sanjay Time Remaining: 4 hrs

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Task: Configure database Task: Configure database and SpaceIDs for Trac and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs Owner: Sanjay Time Remaining: 4 hrs

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

Task: Configure database and SpaceIDs for Trac Owner: Sanjay Time Remaining: 4 hrs

Dashboard / Daily Scrum meeting

Use whiteboard and wall: easy to share and update PM provide performance and feedbacks Have daily scrum meeting to check progress & share issue Do not push developers to do over-time work to finish jobs but must analyzed the reasons and write it down

Scrum case: KR Gugi (Local)

Sprint review
Every Friday morning with the team Demo the result of current sprint; email the result to stakeholders after review meeting Check team velocity and use it history data for next planning Do not run separately Sprint review and Retrospective; more focus on Sprint review Sometime open tech talk or have a deep discussion

Outcome
Reduce interrupt works & over-time works Increase productivity and service quality; keep focus on jobs; Service incidents: 18 during 2H 2007 vs. 3 during 1H 2008 More innovation in the team : life-map, Nova, TDD, CI, Global search

Scrum process lesson learned (Planning, Backlog, Estimation)

Yahoo! Presentation, Confidential

Scrum process
Planning
It is a like to find an optimized way continuously with progressive elaboration process

Fix schedule and control scope

Scrum process
Backlog
Even rough UI help to scope and estimate clearly It would be a perfect when it has following components: User story + scenario (steps) + constraints + acceptance criteria + visual elements Users involvement is critical Put every things in Backlog including bug fix and documentation and meetings, etc..

Estimation
Its always difficult but improved To estimate well, Knowing teams velocity is the most important Trust team members estimation Engineers are tend to be optimistic when they estimate their works : Calendar vs. Ideal time

Scrum velocity tracking & improvement

Yahoo! Presentation, Confidential

10

Scrum process
Team velocity & improvement
Dash-board is an essential mechanism for team to be self-organized Go through trial & error to get a reliable velocity Its hard to improve teams velocity after settled in but could improve it steadily when we motivate them enough Avoid volatility in velocity Learn good ways doing of Agile from experts from inside or outside of organization Try to apply pair programming or pair-review at least Participate Agile conferences or held team seminar regularly

Scrum tools

Yahoo! Presentation, Confidential

12

Scrum tools
Agile management Sticky notes/Post-its Whiteboards Twiki Spreadsheets templates (Excel) Yahoo! Sprint Manager (internally developed) Commercial Version One: Agile Community/Team/Enterprise (VersionOne, Inc.) Rally Community/Program (Rally Software) ScrumWorks Basic/Pro (Danube Technologies, Inc.) Pivotal Tracker (Pivotal Labs) Mingle (ThoughtWorks Studios) CI (open source) Hudson Jenkins Continuum

What should I do to Agile

"On the bathing tub of T'ang, the following words were engraved: "If you can one day renovate yourself, do so from day to day. Yea, let there be daily renovation."