Initial introduction about Scrum project management.

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

2. MIRUM AGENCY 2015
Prewords
https://www.linkedin.com/in/jpartogi
Joshua Partogi
Professional 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:

3. MIRUM AGENCY 2015
Scrum Methodology
Chapter 1
A problem can’t be solved from
the same state of mind that created it.
— Einstein

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

5. Scrum methodology
Client gives (sometimes very rough) brief
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
Analysis
Time &
resource
planning
> > > > > >Review>
sprint
“I want to build website that contains informations and at the end generates some revenue.”

6. Scrum methodology
Creating Story
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

7. Scrum methodology
Wireframe & UI (Design)
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

8. Scrum methodology
Story Carding
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

9. Scrum methodology
Sprint Planning
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

10. Scrum methodology
Sprint Planning
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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.

11. Scrum methodology
Sprint Planning
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

12. Scrum methodology
Sprint Planning
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

13. Scrum methodology
Sprint Planning
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

14. 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
LIVE
Workload
Analysis
Time &
resource
planning
> > > > > >Review>
sprint
by Scrum Master + Engineers

15. 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
LIVE
Workload
Analysis
Time &
resource
planning
> > > > > >Review>
sprint
Backlog
by Scrum Master + Engineers

16. Reviewing the previous sprint:
Scrum methodology
Retrospective
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

17. Scrum methodology
Sprint Planning for 2nd sprint
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

18. Scrum methodology
2nd Sprint Running
Brief
accepted
Problem analysis,
requirements
building, UX
UI /
Wireframe
Development
GO
LIVE
Workload
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

19. Scrum essentials
Other notes of Scrum
Stand-up meeting
In 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.

20. Scrum is running on:
…and many more

21. MIRUM AGENCY 2015
Bonus Stage
Chapter 2

22. Tools which supports Scrum
Project Management Tool
https://trello.com/

23. Tools which supports Scrum
Project Management Tool
https://jira.atlassian.com

24. Tools which supports Scrum
Harvest
Timesheet App
https://www.getharvest.com/

25. MIRUM AGENCY 2015
Classic Question
Chapter 3

26. 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?

27. https://id.linkedin.com/in/aldosantoso
Joshua Partogi
Aldo Santoso
Tito Pratikto
Thanks to:
http://www.slideshare.net/aldosantoso
Prepared by: