Introduction to Scrum. Scrum is an Agile process, focused on iterative and incremental development. By dedicating resources, collapsing feedback loops, timeboxing activities, and adapting to design changes, Scrum teams deliver the greatest ROI back to the business.

1. Introduction to Scrum – Agile Methodology

2. Product Engineering.
We support innovation teams in
large organizations by
prototyping proof of concepts.
Our focus is on deep tech: AI,
Blockchain, Mobile, Analytics.
Venture Builder.
We are serial entrepreneurs. Our
startup studio is where we walk
the talk and build our own lean
projects.

3. Scrum
‘Agile’ for
everyone

4. Typical Software
Development Process

5. Design
Implementation
Testing
Deployment
Maintenance
Requirements

6. Requirements
Implementation
Testing
Deployment
Maintenance
Design
Takes too long Skipped
Dreaded
Changes

7. Result?
Delays.
Loss of control.
Stress.
Quality issues.

8. Solution?
Accept reality.
Project management for
real life.

9. How? Scrum.

11. A light-weight agile project
management toolkit.

12. Scrum ‘rituals’ or practices:
3 artefacts, 3 roles, 4 ceremonies
Tasks = artefacts
People = roles
Meetings = ceremonies

13. 1.
Tasks = Scrum Artefacts.
Product increment
Product backlog
Sprint backlog

14. Scrum process: product increments

15. Why iterative?

16. Prototype leads to Product.
Rapid feedback.
Reduced risk.

17. Define product backlog
Features described and prioritized as user stories.

18. Scrum team estimates work
associated with each story.
Each feature ranked in order
of importance

19. Sprint backlog

20. Iterations = Sprints
1 - 4 Weeks

21. Each sprint has very specific
measurable, attainable goals.

22. vs
WATERFALL METHODOLOGY AGILE METHODOLOGY

23. 2.
People = 3 scrum roles.
Product Owner.
Scrum Master.
Scrum Team.

24. Product owner owns the
product backlog.

25. Scrum master facilitates
agile process.

26. Scrum team, cross-functional
development team.
includes testers, designers, ops engineers in addition to developers.

27. 3.
Meetings = ceremonies.
4 ceremonies

28. Ceremonies.
Ritual Happens on
1 Sprint planning meeting First day of the sprint
2 Daily scrum meeting Every day of the sprint
3 Sprint review / demo Last day of the sprint
4 Sprint retrospective Last day of the sprint

29. Why scrum?

30. Simple.
Un-opinionated.
Clear measures.

31. Each story is estimated.
Over time, we can improve
estimates and notice trends.

32. Work remaining % rate = days to completion

33. Keeps team focused.
Maintains flexibility.

34. How do we start?

35. 1. Committed people.
2. Create product backlog.
3. Start iterating.

36. It can take several sprints
before it feels natural.

37. TIPS
Don’t get stuck in process
Don’t get stuck in meetings
Don’t trash the backlog
Keep trying

38. QUESTIONS?
Andries De Vos
CEO & Co-Founder
andries@slash.us.com