1 / 15

Scrum: Prepare, Plan, Run, and Track Sprints for Successful Project Management

This comprehensive guide outlines how to effectively implement the Scrum framework, from preparing for a project to tracking sprint progress. Learn how to identify customer needs, create a high-level plan, build a product backlog, establish a release plan, and successfully run sprints.

sradcliff
Download Presentation

Scrum: Prepare, Plan, Run, and Track Sprints for Successful Project Management

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 Jarred Payne Ashrith Pillarisetti

  2. Prepare for Project • Plan the Project • Plan a Sprint • Run a Sprint • Track the Sprint Scrum

  3. Prepare for Project establish the business case Identify what the customer wants Define the vision assemble teams set up your team's infrastructure

  4. Plan The Sprint  Create High Level Plan This plan is a roadmap to guide more detailed decisions. Plan changes as its implemented. The product backlog will come from the high level plan

  5. Build Product Backlog • Broad Description of all potential features • Prioritized according to business value • Team estimates size of a feature (difficulty of implementation, how many subsystems need to be involved, etc …. )

  6. Establish Release Plan Each sprint, your team will complete an increment of the product that it could ship.  Identify groups of features that, together, provide enough business value to release to your customers Determine in which sprints the team expects to complete those groups of features.

  7. Plan a Sprint

  8. Sprint Backlog The sprint backlog is the list of work the team must address during the next sprint. Features are broken down into tasks 1 to 6 hours of work Planning Poker With this level of detail the whole team understands exactly what to do, and potentially, anyone can pick a task from the list.

  9. Tasks

  10. Figure out Team Capacity

  11. Run a Sprint  Sprint Backlog is frozen during the sprint No new requirements Track Sprint Progress Finish the Sprint Unfinished tasks pushed to next sprint Bugs

  12. Scrum Meetings Usually are daily meetings but for us, we can have them every class period Each person answers 3 questions: What did you accomplish since the last meeting? What do you plan on working on until the next meeting? Anything that will prevent you from working on your tasks? (e.g. Have a big test, interviews, stuck)

  13. Prepare for Next Sprint • Update the features and their priorities as customers' needs change. • Break down features that are likely to be implemented in the next sprint • Meet with team leader and/or PM to plan out your specific tasks

  14. Track Progress

  15. Sprint Progress

More Related