Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Scrum Introduction

No description
by

on 9 October 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Scrum Introduction

Scrum An Introduction Traditional Project planning & project management Trying to estimate and plan all work before the project kicks off Project manager responsible for dividing work High risk for disappointed customers because project delivered what was initially planned, not what is needed now Over Time Over Budget Lesser Quality Waterfall Model Design Plan Build Test Deploy Because of lenghty build phase, risk for distraction through Scope Creep Stakeholders try to add / change requirements Waterfall Model Scrum Characteristics Work is done is small, self-organizing teams, decisions are made on team level Work is done during timeboxed periods (sprints) during which outside influence is avoided Not all tasks are planned at the beginning of a project Scrum does not specify engineering practices Project environment is constantly changing.
Not everything can be know in advance in a complex situation. If you try to plan everything up to task level, your project has a high risk of failure Scrum Roles Product Owner Represents the business
Decides on what has priority to build Scrum Master manages the use of Scrum, not the team. Removes impediments that block the work of the team Development Team Self organizing, cross-functional team that builds the functionality prioritized by the Product Owner
Between 4 and 9 members Scrum Team Sprint Daily
Scrum Done Functionality Stories Scrum Project steps Sprint Planning Session Whole Scrum Team decides on functionality to be build in the next sprint. Based on the priorities from the Product Owner and the estimates of how much can be done by the Team. Sprint The team decides who works on what.
The functionality to work on has been decided on in the Planning session and does not change in the sprint. Daily Scrum the team tells each other: what they did the previous day; what they will do today; what is impeding them from working optimally. Sprint Review The team demonstrates the finished functionality to the Product Owner and the other Stakeholders.
Feedback and input is given for the next sprint Sprint Retrospective The team reflects on the finished sprint and decides on improvements for the next sprint 3 hours 4 hours 15 minutes max 30 days 8 hours Input: Product Backlog contains functionality (stories) necessary for finished product. Is maintained and prioritized by Product Owner Estimations Estimations of work per story, given by the Development Team Output: Sprint Backlog Contains top priority stories from Product Backlog that are estimated to fit in this sprint Input: Sprint Backlog Updated to reflect current status Team updates What is done, what will be worked on today, what is blocking Story ABC
Priority: 1
Estimate: 80 Hours Story DEF
Priority: 2
Estimate: 55 Hours Story GHI
Priority: 3
Estimate: 12 Hours Story JKL
Priority: 4
Estimate: 34 Hours Story: MNO
Priority: 5
Estimate: 40 Hours Story PQR
Priority: 6
Estimate: 23 Hours Story ABC
Priority: 1 Story DEF
Priority: 2 Story GHI
Priority: 3 Story JKL
Priority: 4 Story: MNO
Priority: 5 Story PQR
Priority: 6 Product Backlog Sprint Backlog Sprint size = 150 Hours Important: Functionality is 'Done' in a Sprint if it is ready for deployment:
- Working
- Tested
- Documented

Scrum Sprints deliver working implements of te final product, so part of the functionality could be used before the project is finished Burndown Chart Shows the finished work and the estimated remaining work, plotted on the days of the sprint.

Gives the Scrum Team a quick overview of Sprint All this constitutes the 3 Pillars of Scrum: Transparency A common defenition of 'Done'
A common understanding of the steps within a project
All Development Team members decide together who works on what Inspection Everyone in the Scrum Team frequently inspects the Backlogs and Burn Down Chart Adaptation Adjustments to the project can be made by the Product Owner. He can change the Product Backlog to influence the content of the next Sprint.
The Sprint Review and Sprint Retrospective are designed for adapting the content and the process of the next sprint max 30 days 15 minutes
Full transcript