Scrum project case in Yahoo Korea (야후 거기 스크럼 프로젝트)

7/28/2019 Scrum project case in Yahoo Korea ( )

1/15

Yahoo! Presentation, Confidential 1

Scrum project cases(KR Gugi)

2008.10

Sam Hwang

(PMO)


2/15

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)


3/15


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 backlogexcept incident and s1

Issue Bugzilla ticket for all backlog items and put links onbacklog to trace

Include all product req., engineering tasks, innovation and

meetings.

Product Baklog Sprint Start Date End Date

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


4/15


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


5/15

Dashboard / Daily Scrum meeting Use whiteboard and wall: easy to share and update

PM provide performance and feedbacks


burndown chart

0

20

40

60

80

100

120

140

160

180

200

220

Day

1

Day

2

Day

3

Day

4

Day

5

hoursofworkremainin

IN PROGRESSTO DO DONE

Task Confgu daabasand SpaeDs orTraOwnerSanjayTimeRema ning:4 hrs


Task Confgu da abasand SpaeDs orTraOwnerSanjayTimeRema ning:4 hrs

Task Confgu daabasand SpaeDs orTraOwnerSanjayTimeRema ning:4 hrsTask Confgu daabasand SpaeDs orTra

OwnerSanjayTimeRema ning:4 hrs

Task Confgu daabasand SpaeDs orTraOwner`SanjayTimeRema ning:4 hrs

Task Confgu da abasand SpaeDs orTraOwnerSanjayTimeRema ning:4 hrsTask Confgu daabasand SpaeDs orTra



Task Confgu da abasand SpaeDs orTraOwner SanjayTimeReman ing:4 hrs












Task Confgu da abasand SpaeDs orTraOwnerSanjayTimeRema ning:4 hrsTask Confgu daabasand SpaeDs orTra








Have daily scrum meeting to

check progress & share issue Do not push developers to do

over-time work to finish jobsbut must analyzed the

reasons and write it down


6/15

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 onSprint 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


7/15Yahoo! Presentation, Confidential 7

Scrum process lesson learned

(Planning, Backlog, Estimation)


8/15

Scrum process

Planning

It is a like to find an optimized way continuously withprogressive elaboration process

Fix schedule and control scope


9/15

Scrum process

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 theirworks : Calendar vs. Ideal time

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 + acceptancecriteria + visual elements

Users involvement is critical

Put every things in Backlog including bug fix and documentationand meetings, etc..



Scrum velocity tracking & improvement


11/15

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 itsteadily when we motivate them enough

Avoid volatility in velocity

Learn good ways doing of Agile from experts from inside or outside oforganization

Try to apply pair programming or pair-review at least

Participate Agile conferences or held team seminar regularly



Scrum tools


13/15

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
http://sprint.corp.yahoo.com/http://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.versionone.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.rallydev.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.danubetech.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.pivotalsf.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fstudios.thoughtworks.com%2Fmingle-project-intelligencehttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fstudios.thoughtworks.com%2Fmingle-project-intelligencehttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.pivotalsf.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.danubetech.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.rallydev.com%2Fhttp://redirect.corp.yahoo.com/?url=http%3A%2F%2Fwww.versionone.com%2Fhttp://sprint.corp.yahoo.com/


14/15

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."


15/15

Documents

Scrum project case in Yahoo Korea (야후 거기 스크럼 프로젝트)