Scrum Project Management

27
MIRUM AGENCY 2015 Scrum Project Management Digital Farm #17 20 November 2015 Mirum Jakarta presents

Transcript of Scrum Project Management

Page 1: Scrum Project Management

MIRUM AGENCY 2015

Scrum Project ManagementDigital Farm #17

20 November 2015

Mirum Jakarta presents

Page 2: Scrum Project Management

MIRUM AGENCY 2015

Prewords

https://www.linkedin.com/in/jpartogi

Joshua PartogiProfessional Scrum Trainer at Scrum.org

https://medium.com/@jpartogi

5 mitos di industri software development Indonesia

5 alasan kenapa banyak Manajer IT di Indonesia yang perlu ‘diganti’

Kenapa praktisi software development di Indonesia harus merevolusi caranya berpikir

Kenapa perusahaan di Indonesia sebenarnya tidak membutuhkan manajer

Other articles:

Page 3: Scrum Project Management

MIRUM AGENCY 2015

Scrum MethodologyChapter 1

A problem can’t be solved from the same state of mind that created it. — Einstein

Page 4: Scrum Project Management

Waterfall methodology

Scrum methodology

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development

GO LIVE

Workload Analysis

Time & resource planning

> > > > > >Review>

Iteration = sprint

Scrum

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe

Development whole

projects

GO LIVE

Workload Analysis

Time & resource planning

> > > > > >>Review whole

projects

Waterfall vs Agile/Scrum

Page 5: Scrum Project Management

Scrum methodology

Client gives (sometimes very rough) brief

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

“I want to build website that contains informations and at the end generates some revenue.”

Page 6: Scrum Project Management

Scrum methodology

Creating Story

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Story ~ UX (features, deliverables)

Results: 1. Information page. 2. Shopping transaction inside the website. 3. Customer service. 4. People can buy via website, and get the products from the store directly.

by Product Owner

Page 7: Scrum Project Management

Scrum methodology

Wireframe & UI (Design)

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Breaking down Story into details.

Home

Products (level 1)

Products (level 2)

Products (detail)

Payment

Confirm Order

Customer Service

Open TicketContact

by UX / UI Designer

Page 8: Scrum Project Management

Scrum methodology

Story Carding

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Story carding = giving point to each story. The larger the points, more difficult the story.

Products (detail) Confirm OrderHome

Payment Customer ServiceProducts (level 1)

Contact Open TicketProducts (level 2)

21

8

8

5

5 5

13

13

13

by Scrum Master + Engineers + Head of Engineers

Page 9: Scrum Project Management

Scrum methodology

Sprint Planning

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Allocate stories into sprints.

31 34 34Jumlah story point / sprints =

Products (detail) 8 Confirm Order 13Home 5

Payment 21 Customer Service 8Products (level 1) 13

Open Ticket 5Products (level 2) 13

by Scrum Master + Engineers + Head of Engineers

Sprint 1 Sprint 2 Sprint 3

Contact 5

Page 10: Scrum Project Management

Scrum methodology

Sprint Planning

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Then, we can define number of developers needed.

Sprint 1 Sprint 2 Sprint 3

Length per sprint 2 weeks 2 weeks 2 weeks

Total Story Point 31 34 34

Developer Velocity 20 points / sprint 20 points / sprint 20 points / sprint

Total developer needed 2 2 2

by Scrum Master + Engineers + Head of Engineers

Tips: 1 story is assigned to 1 developer. So at the end we can get the velocity of the developer. It will be our data for next projects.

Page 11: Scrum Project Management

Scrum methodology

Sprint Planning

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

This is another possibility.

Sprint 1 Sprint 2 Sprint 3

Length per sprint 2 weeks 2 weeks 2 weeks

Total Story Point 31 34 34

Developer Velocity 35 points / sprint 35 points / sprint 35 points / sprint

Total developer needed 1 1 1

by Scrum Master + Engineers + Head of Engineers

Page 12: Scrum Project Management

Scrum methodology

Sprint Planning

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

This is another possibility.

Sprint 1 Sprint 2

Length per sprint 3 weeks 3 weeks

Total Story Point 49 50

Developer Velocity 50 points / sprint 50 points / sprint

Total developer needed 1 1

by Scrum Master + Engineers + Head of Engineers

Page 13: Scrum Project Management

Scrum methodology

Sprint Planning

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

This is another possibility.

Sprint 1 Sprint 2

Length per sprint 3 weeks 3 weeks

Total Story Point 49 50

Developer Velocity 25 points / sprint 25 points / sprint

Total developer needed 2 2

by Scrum Master + Engineers + Head of Engineers

Page 14: Scrum Project Management

Developers doing development according to story & sprints that has been assigned on previous step.

This phase contains: 1. Development 2. Testing & bug-fixing

Scrum methodology

Sprint Running

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

by Scrum Master + Engineers

Page 15: Scrum Project Management

Contains all the new request(s) from client.

Backlog is reviewed in Retrospective phase. It will be determined whether the new request(s) will be accommodated in next sprint or not.

Scrum methodology

Backlog

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprintBacklog

by Scrum Master + Engineers

Page 16: Scrum Project Management

Reviewing the previous sprint:

Scrum methodology

Retrospective

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

1. Has current sprint finished well or not? 2. Testing is not over? Still have some bug? 3. New request on Backlog? Will be

accommodated in next sprint?

= actual= based on sprint planning

by Scrum Master + Engineers

Page 17: Scrum Project Management

Scrum methodology

Sprint Planning for 2nd sprint

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

Unfinished story from previous sprint, New request from Backlog

Products (detail) 8 Confirm Order 13Home 5

Payment 21 Customer Service 8Products (level 1) 13

Contact 5 Open Ticket 5Products (level 2) 13

NEW: About 3

by Scrum Master + Engineers + Head of Engineers

Page 18: Scrum Project Management

Scrum methodology

2nd Sprint Running

Brief accepted

Problem analysis, requirements building, UX

UI / Wireframe Development GO

LIVEWorkload Analysis

Time & resource planning

> > > > > >Review>

sprint

by Scrum Master + Engineers

finally GO LIVE!

2nd Sprint’s Retrospective by Scrum Master + Engineers

3rd Sprint Planning by Scrum Master + Engineers + Head of Engineers

3rd Sprint Running by Scrum Master + Engineers

3rd Sprint Retrospective by Scrum Master + Engineers

Page 19: Scrum Project Management

Scrum essentials

Other notes of Scrum

Stand-up meetingIn a circle, each person tells what to do today

No-project-manager management

Scrum master: help solving problem, handling client, not pushing for deliverables.

Involvement of all members.

Page 20: Scrum Project Management

Scrum is running on:

…and many more

Page 21: Scrum Project Management

MIRUM AGENCY 2015

Bonus StageChapter 2

Page 22: Scrum Project Management

Tools which supports Scrum

Project Management Tool https://trello.com/

Page 23: Scrum Project Management

Tools which supports Scrum

Project Management Tool https://jira.atlassian.com

Page 24: Scrum Project Management

Tools which supports Scrum

Harvest Timesheet App https://www.getharvest.com/

Page 25: Scrum Project Management

MIRUM AGENCY 2015

Classic QuestionChapter 3

Page 26: Scrum Project Management

More suitable to technical project

Is it possible to apply Scrum in Mirum?

Classic Question

Client must be involved also

No-project-manager management

Improvise, improvise, improvise

Other’s opinion?

Page 27: Scrum Project Management

https://id.linkedin.com/in/aldosantoso

Joshua Partogi

Aldo Santoso

Tito Pratikto

Thanks to:

http://www.slideshare.net/aldosantoso

Prepared by: