We try to use the agile software development methodology "Scrum" to organize the university course "Media Production III" in the Digital media Bachelor’s program (MDM)
 of Hamburg Media School and Leuphana University.

1. Welcome
Digital media Bachelor’s program (MDM)
Media Production III: Let’s try Scrum
Christian Heise, Centre for Digital Cultures
Hamburg Media School, 9.4.2015

2. Today
1. Any Issues?
2. Introduction: Your Name, 3 personal Tags and your
expectations
3. Introduction to Scrum
4. Structure of the Course and Assessment
5. Your „User Stories“ / Your Visions
6. Find/form your Team
7. Tasks until next Session (Define your focus & Sprint Planning)

3. Let’s try Scrum: manage
chaos - a short introduction

4. Typical Software / Project
Development Process (theoretically)
1. Requirements
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance

5. Typical Software / Project
Development Process (in reality)
1. Initial Requirements (always changes)
2. Design (unexpected changes)
3. Implementation (takes to long)
4. Testing (skipped)
5. Deployment (dreaded)
6. Maintenance (miscalculated)

6. Result: Naturally Chaos
Source: Jez Elliott (CC-BY 2.0)

7. How to control chaos?
Source: Nguyen Hung Vu (CC-BY 2.0)

8. Wrong
Question!
Source: 18r (CC-BY-NC-ND 2.0)

9. Right Question:
How to use and manage
chaos?
Source: Jason Carter (CC-BY 2.0)

10. Source: http://scrum.kaverjody.com/wp-content/uploads/2013/01/9-The-new-new-product-development-game.pdf

11. Source: http://agilemanifesto.org/

12. We need a light-weight
agile project
management toolkit.

13. Source: http://borisgloger.com/scrum/scrum-flow/

14. The idea - it is all about:
People
Things
Behaviors

15. People
Things
Behaviors

16. Source: West Point Military Academy (CC-BY 2.0)
Source: Jez Nicholson (CC-BY-SA 2.0)
Source: Don O'Brien (CC-BY 2.0)
scrum masterscrum team
Product Owner
People & Roles
+ additional Roles: User, Customer,
Manager

17. The scrum team
deliver the product and they
are responsible for the
quality. They work with als
stakeholders to understand
the requirements. The
Teams performs its
commitment voluntarily.
They work continuously with
the product owner to define
the strategic direction of the
project.
Source: West Point Military Academy (CC-BY 2.0)

18. The product owner drives
the project from the business
point of view. She
communicates a clear vision
of the product and she
defines its main
characteristics. She also
accepts the product at the
end of a Sprint. She makes
sure that the team only works
on the most valuable Backlog
Items. She has the same goal
as the team. Source: Don O'Brien (CC-BY 2.0)

19. The scrum master protects the
team from all disturbances. He
is not part of the team. He
helps to improve the
productivity of the scrum team.
Scrum master works with
product owner to ensure the
Product Owner fulfills his job.
ScrumMaster coaches the
Product Owner and helps him
against outsides odds.
Source: Jez Nicholson (CC-BY-SA 2.0)

20. People
Things
Behaviors

21. Things we want to do.

22. The product/vision is described
as a list of detailed features:
The product backlog.
Source: Drew Stephens (CC-BY-SA 2.0)

23. The features are
described in terms of
user stories.

24. The scrum team estimates the
work associated with each story
and decides on which work will
be done in the (next) sprint.

25. The product owner
owns the product
backlog, the sprint team
owns the sprint backlog

26. Result: a ranked and
weighted list of product
features.
Source: Jacopo Romei (CC-BY-SA 2.0)

27. Again, what?
People
‣ Product Owner
‣ Scrum Master
‣ ScrumTeam
‣ additional Roles
Things
‣ Vision
‣ Backlog
‣ Stories
‣ Estimates

28. People
Things
Behaviors

29. Typical Software / Project
Development Process (in reality)
1. Initial Requirements (always changes)
2. Design (unexpected changes)
3. Implementation (takes to long)
4. Testing (skipped)
5. Deployment (dreaded)
6. Maintenance (miscalculated)

30. Source: J. Aaron Farr: Scrum - Agile for Everyone
Agile Software / Project
Development Process

31. Source: J. Aaron Farr: Scrum - Agile for Everyone

32. So why Iterative?

33. Get rapid Feedback
Reduced Risks
Get better in estimation
Get better in calculation
Get things done
What else?

34. Source: J. Aaron Farr: Scrum - Agile for Everyone

35. Sprints start with a sprint
planning meeting. Sprints
end with a retrospective.

36. At the planning meeting,
we commit to an amount
of work.

37. Each day we have a daily
scrum meeting.
All Team members have to
answer the following questions:
1. What did you do?
2. Any obstacles?
3. What will you do?

38. Source: Shintaro Kakutani (CC-BY 2.0)
Sprint review / retrospective helps us in
getting better

39. Ok, got it. But exactly
why do we need Scrum?

40. It's simple and un-opinionated.
It provides clear measures.
Each story is estimated.
Over time, we can improve estimates and notice trends.
Burn-down and Velocity.
Keeps team focused.
Maintains flexibility.
Because we want to get things done!

41. How do we start?

42. 1. Communicate Visions
2. Get People committed to Visions.
3. Create a backlog with stories.
4. Plan Sprint
5. Start iterating.

43. Remarks? Questions?
@christianheise or
heise@leuphana.com

44. Backup

45. Course schedule
INTRO
Session 1: 14:00 - 17:15
Introduction, Introduction SCRUM, Vision market place
FIRST SPRINT PHASE
Session 2: 14:00 - 17:15 - Sprint Planning, 1st Daily Sprint
Session 3: 14:00 - 17:15 - ggf. Sprint Planning, ggf. 2st Daily Sprint, maybe Experts
Session 4: 14:00 - 17:15 - ggf. Sprint Planning, ggf. 3st Daily Sprint, maybe Experts
REVIEW AND RETROSPECTIVE I
Session 5: 9:45 – 17:15
1 Tag Review and Retrospective, Sprint Planning
SECOND SPRINT PHASE
Session 6: 14:00 - 17:15,
Session 7: 9:45 – 17:15
REVIEW AND RETROSPECTIVE II
Session 8: 9:45 – 17:15
1 Review and Retrospective, critical reflexion of SCRUM, Finish