32
Lena Bigelow Business 550 Presentation SCRUM

SCRUM

  • Upload
    breena

  • View
    41

  • Download
    0

Embed Size (px)

DESCRIPTION

SCRUM. Lena Bigelow Business 550 Presentation . Scrum vs. Waterfall Approach. Scrum. Waterfall Approach. -Traditional Approach: -Requirements Gathering, Analysis, Design, Code, Test, Deploy - Each stage is completed before moving on - Artifact Driven. A project management process - PowerPoint PPT Presentation

Citation preview

Page 1: SCRUM

Lena BigelowBusiness 550 Presentation

SCRUM

Page 2: SCRUM

- A project management process

- Embraces iterative and incremental practices

- Concentrates on what is important: Managing a

project or writing software that produces

business value

-Traditional Approach:

-Requirements Gathering, Analysis, Design, Code, Test,

Deploy

- Each stage is completed before moving on

- Artifact Driven

Scrum Waterfall Approach

Scrum vs. Waterfall Approach

Page 3: SCRUM

- Designed to increase productivity and reduce the time it takes to benefit from a software/product development.

- - Mature and scalable

- -Flexible

- 80% of a product’s value comes from 20% of its features

What Is Scrum?

Page 4: SCRUM

Version 1: 20% featuresVersion 2: 20% + 20% = 40% features

Incremental delivery allows the business to realize benefits much earlier in the cycle.

Work on small pieces at a time = Iterative

What Is Scrum?

Page 5: SCRUM

Scrum Asks… Fundamental Project Management Issue

What have you done during the last 24 hours?

This is progress, it’s work completed to date.

What do you plan to do in the next 24 hours?

This is forward planning, it is work you are about to do.

What is stopping you from getting on with the work of the next 24 hours?

These are your obstructions or immediate risks, it might be things you need in order to work.

Understanding Scrum

Page 6: SCRUM

Product Owner

2. Scrum Master – Represents management to the project

-Responsible for enacting Scrum values and practices

3. Project Team-5-10 members

-Cross functional

Scrum’s 3 Roles

Page 7: SCRUM

-Scrum records requirements in a Product Backlog

-Product owner prioritizes requirements (Items that add immediate business value are on top)

-The Project Team - do the actual work-Make Sprint Backlog

-GOAL: -After 30 days, should have a “potentially shippable product

increment”

SCRUM-The Process

Page 8: SCRUM

-Every 30 days = Provide something of value to the business

*Positives: If they like what they see after 30 days, they can re-prioritize the product backlog so they are ALWAYS producing

goods that will be used

Remember: 80% value comes form 20% of its features

Scrum-Goals

Page 9: SCRUM

The Scrum Process

Page 10: SCRUM

-24 Hour Cycle Meetings-Have to stand

-Time boxed – 15 minutes-Scrum Master & Project Team are only allowed to speak

-If you’re late, you pay $

Questions Asked:What did you do yesterday?

What will you do today?What obstacles are in your way?

Daily scrum meeting

Page 11: SCRUM

“Pigs” = Committed“Chickens” = Involved

A chicken and a pig where chatting about setting about a business together. The pig asked the chicken: "What kind of

business would we set up?" The chicken thought for a moment and said "How about a restaurant?" The pig liked the idea but asked "What would we serve?" The chicken responded "How

about ham’n’eggs?" At which point the pig refused to take the business venture any further. The chicken was confused and asked "Why?" The pig responded "Well, you would only be

involved, whereas I would be committed."

Who Is Committed To Your Project?

Page 12: SCRUM

Product Backlog

Page 13: SCRUM

Sprint Backlog At Inception

(All the things that will be done)

Page 14: SCRUM

Sprint Backlog - After Work Has Been Performed

(Can see actual progress being made)

Page 15: SCRUM

Sprint Burndown - After Work Has Been Performed

-Should Be Steady Work Flow! Warning Indicator !

Page 16: SCRUM

Sprint Burndown - Work Has Not Been Performed Fast Enough

Possibilities-Too many distractions

-Sprint backlog not updated-Sprint backlog items are too difficult

Page 17: SCRUM

Sprint Burndown – Work Has Been Performed Too Fast – Lack Of Work

Page 18: SCRUM

Profit & Loss Using Traditional Development

Page 19: SCRUM

Profit & Loss Using Scrum

-Recognize Profit Earlier

Page 20: SCRUM

-Scrum lets us move our projects from "top right” "bottom left".

-Accepting that 80% of a product’s value comes from 20% of its features

means you can move from complicated simple.

Page 21: SCRUM

21

Energy SoftwareCase Study

- Develops a software product for oil and energy companies

-Aiming to create new versions aka new “projects”

-Development of the whole project is called a new “program”

-Distributed between Norway and Malaysia(main activities in Europe, offices in Asia)

21

Page 22: SCRUM

22

Energy Software

-Experienced in carrying out distributed projects (using agile methods is new to them)

-New product versions - twice a year

-6 old versions are maintained

-Started 18 employees - Now 190 employees

22

Page 23: SCRUM

23

Energy Software Knowledge

-Two major groups

1. The Service Organization (distributed all over the World)

2. Product Development Organization (distributed in Norway and Malaysia)

-Followed traditional waterfall model

-Needed better quality and more agility23

Page 24: SCRUM

24

Energy Software Scrum 3 Month Trial

-Challenges-

-Daily scrum meetings via telephone conferencing & Web cameras (connection not strong enough for video conferencing)

-Only 2 hour common working time window

-Silence caused my distance

-Misunderstanding requirements

24

Page 25: SCRUM

25

Energy Software Scrum 3 Month Trial

-Positives-

- Improved communication(more structured & frequent)

- Improved Trust

- Increase in motivation (receive quick clarification & all share equal value on team)

- Improved quality

- Collaboration 25

Page 26: SCRUM

26

Energy Software Scrum 3 Month Trial

-Lessons Learned-

-Arrange proper SCRUM training

- Travel (Face To Face Visits are important)

- Encourage frequent communication

- Provide a set of communication tools

- Arrange overlapping working time

26

Page 27: SCRUM

-The ethos of simplicity and the art of the possible

“Don’t procrastinate, do something, no matter how small…”-Ken Schwaber – Scrum’s co-founder

Again- What Is Scrum?

Page 28: SCRUM

A) Short for Scrum-diddley-umptiousness

B) So.Cool.Rad.Uptown.Management

C) Moving toward complex and complicated management processes

D) Moving through complex and complicated towards simple business practices

Multiple Choice Question #1:

What Is Scrum?

Page 29: SCRUM

A) Short for Scrum-diddley-umptiousness

B) So.Cool.Rad.Uptown.Management

C) Moving toward complex and complicated management processes

D) Moving through complex and complicated towards simple business practices

Good Job, You’re Smart!!!

Page 30: SCRUM

Exactly the same as the waterfall approach

Designed to increase productivity and reduce the time it takes to realize value

Solely to document records of Product Backlogs and Sprint Backlogs

There is not one, it is all about discussing your daily activities with your coworkers

Basically, What Is The Point Of Scrum?

Page 31: SCRUM

Exactly the same as the waterfall approach

Designed to increase productivity and reduce the time it takes to realize value

To document records of Product Backlogs and Sprint Backlogs

There is not one, it is all about discussing your daily activities with your coworkers

Good Job, You’re Right Again!!! Look Out Now Gurl!!!

Page 32: SCRUM

Meow !!! Thank you !!! Meow