1 / 32

SCRUM

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

breena
Télécharger la présentation

SCRUM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCRUM • Lena Bigelow • Business 550 Presentation

  2. 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 • Embraces iterative and incremental practices • Concentrates on what is important: Managing a project or writing software that produces business value

  3. What Is 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

  4. What Is Scrum? • Version 1: 20% features • Version 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

  5. Understanding Scrum

  6. Scrum’s 3 Roles • 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

  7. SCRUM-The Process • -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”

  8. Scrum-Goals • -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

  9. The Scrum Process

  10. Daily scrum meeting • -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?

  11. Who Is Committed To Your Project? • “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."

  12. Product Backlog

  13. Sprint Backlog At Inception(All the things that will be done)

  14. Sprint Backlog - After Work Has Been Performed(Can see actual progress being made)

  15. Sprint Burndown - After Work Has Been Performed-Should Be Steady Work Flow! Warning Indicator !

  16. Sprint Burndown - Work Has Not Been Performed Fast EnoughPossibilities-Too many distractions-Sprint backlog not updated-Sprint backlog items are too difficult

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

  18. Profit & Loss Using Traditional Development

  19. Profit & Loss Using Scrum-Recognize Profit Earlier

  20. -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.

  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

  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

  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 agility 23

  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

  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

  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

  27. Again- What Is 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

  28. Multiple Choice Question #1:What Is 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

  29. Good Job, You’re Smart!!! • 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

  30. Basically, What Is The Point Of 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

  31. Good Job, You’re Right Again!!! Look Out Now Gurl!!! • 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

  32. Meow !!! Thank you !!! Meow

More Related