Let’s try scrum for in a university course
-
Upload
christian-heise -
Category
Science
-
view
271 -
download
0
Transcript of Let’s try scrum for in a university course
![Page 1: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/1.jpg)
WelcomeDigital media Bachelor’s program (MDM)
Media Production III: Let’s try Scrum
Christian Heise, Centre for Digital Cultures Hamburg Media School, 9.4.2015
![Page 2: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/2.jpg)
Today1. 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)
![Page 3: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/3.jpg)
Let’s try Scrum: manage chaos - a short introduction
![Page 4: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/4.jpg)
Typical Software / Project Development Process (theoretically) 1. Requirements
2. Design
3. Implementation
4. Testing
5. Deployment
6. Maintenance
![Page 5: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/5.jpg)
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)
![Page 6: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/6.jpg)
Result: Naturally Chaos
Source: Jez Elliott (CC-BY 2.0)
![Page 7: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/7.jpg)
How to control chaos?Source: Nguyen Hung Vu (CC-BY 2.0)
![Page 8: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/8.jpg)
Wrong Question!
Source: 18r (CC-BY-NC-ND 2.0)
![Page 9: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/9.jpg)
Right Question:How to use and manage
chaos?
Source: Jason Carter (CC-BY 2.0)
![Page 10: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/10.jpg)
Source: http://scrum.kaverjody.com/wp-content/uploads/2013/01/9-The-new-new-product-development-game.pdf
![Page 12: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/12.jpg)
We need a light-weight agile project
management toolkit.
![Page 14: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/14.jpg)
The idea - it is all about:People Things
Behaviors
![Page 15: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/15.jpg)
People Things
Behaviors
![Page 16: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/16.jpg)
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
![Page 17: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/17.jpg)
The scrum teamdeliver 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)
![Page 18: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/18.jpg)
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)
![Page 19: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/19.jpg)
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)
![Page 20: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/20.jpg)
People Things
Behaviors
![Page 21: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/21.jpg)
Things we want to do.
![Page 22: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/22.jpg)
The product/vision is described as a list of detailed features:
The product backlog.
Source: Drew Stephens (CC-BY-SA 2.0)
![Page 23: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/23.jpg)
The features are described in terms of
user stories.
![Page 24: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/24.jpg)
The scrum team estimates the work associated with each story and decides on which work will
be done in the (next) sprint.
![Page 25: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/25.jpg)
The product owner owns the product
backlog, the sprint team owns the sprint backlog
![Page 26: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/26.jpg)
Result: a ranked and weighted list of product
features.
Source: Jacopo Romei (CC-BY-SA 2.0)
![Page 27: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/27.jpg)
Again, what?People
‣ Product Owner ‣ Scrum Master ‣ ScrumTeam
‣ additional Roles
Things ‣ Vision ‣ Backlog ‣ Stories ‣ Estimates
![Page 28: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/28.jpg)
People Things
Behaviors
![Page 29: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/29.jpg)
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)
![Page 30: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/30.jpg)
Source: J. Aaron Farr: Scrum - Agile for Everyone
Agile Software / Project Development Process
![Page 31: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/31.jpg)
Source: J. Aaron Farr: Scrum - Agile for Everyone
![Page 32: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/32.jpg)
So why Iterative?
![Page 33: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/33.jpg)
Get rapid Feedback Reduced Risks
Get better in estimation Get better in calculation
Get things done
What else?
![Page 34: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/34.jpg)
Source: J. Aaron Farr: Scrum - Agile for Everyone
![Page 35: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/35.jpg)
Sprints start with a sprint planning meeting. Sprints end with a retrospective.
![Page 36: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/36.jpg)
At the planning meeting, we commit to an amount
of work.
![Page 37: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/37.jpg)
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?
![Page 38: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/38.jpg)
Source: Shintaro Kakutani (CC-BY 2.0)
Sprint review / retrospective helps us in getting better
![Page 39: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/39.jpg)
Ok, got it. But exactly why do we need Scrum?
![Page 40: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/40.jpg)
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!
![Page 41: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/41.jpg)
How do we start?
![Page 42: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/42.jpg)
1. Communicate Visions 2. Get People committed to Visions.
3. Create a backlog with stories. 4. Plan Sprint
5. Start iterating.
![Page 44: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/44.jpg)
Backup
![Page 45: Let’s try scrum for in a university course](https://reader034.fdocuments.in/reader034/viewer/2022042818/55ba2488bb61eb8d4c8b4813/html5/thumbnails/45.jpg)
Course schedule
INTROSession 1: 14:00 - 17:15 Introduction, Introduction SCRUM, Vision market place
FIRST SPRINT PHASESession 2: 14:00 - 17:15 - Sprint Planning, 1st Daily SprintSession 3: 14:00 - 17:15 - ggf. Sprint Planning, ggf. 2st Daily Sprint, maybe ExpertsSession 4: 14:00 - 17:15 - ggf. Sprint Planning, ggf. 3st Daily Sprint, maybe Experts
REVIEW AND RETROSPECTIVE ISession 5: 9:45 – 17:151 Tag Review and Retrospective, Sprint Planning
SECOND SPRINT PHASESession 6: 14:00 - 17:15, Session 7: 9:45 – 17:15
REVIEW AND RETROSPECTIVE IISession 8: 9:45 – 17:15 1 Review and Retrospective, critical reflexion of SCRUM, Finish