Applied Scrum with User Stories

Public Training Price : $1195 per student
Private Training Price : Request a quote
Print this outline
Enroll in this Public Class

 

 

 

Applied Scrum with User Stories Training Class Summary

This course teaches the Scrum approach to project management and will demonstrate how Scrum can enable your projects to quickly develop working software that meets business needs. In Scrum, teams work within time-boxed iterations (called sprints) to produce production-quality software driven by business priorities. This course explains Scrum’s empirical, adaptive approach, key techniques, and how each team member contributes to its success. In this comprehensive, experiential, highly-interactive course you will learn how to build a product backlog with user stories as input, how to estimate using story points, how to create the sprint backlog, how to plan your sprint work using ideal days, how to create sprint burn-down and burn-up charts and how to work in 30 day sprints. You will apply what you learn in a series of exercises that take you through project start-up, sprint planning, and running a sprint.

Audience: This course is intended for all who will actively participate in a project using the Scrum approach. People on the boundaries of the project (secondary customers, management staff, and participants in related processes) will also benefit.

Prerequisites: Effective User Story Development or a basic understanding of user story writing.

Class Length: 2 days

Applied Scrum with User Stories Training Class Objectives
  • Understand key concepts and terms
  • Be able to explain the methodology’s benefits and key techniques
  • Become familiar with the progression of key activities and artifacts
  • Prepare to participate in an upcoming project
Applied Scrum with User Stories Training Class Detailed Outline
  1. Scrum Methodology Fundamentals
    • Intro to Scrum/benefits vs. waterfall
    • What is iterative development?
    • Sprints – goal, structure, scope
    • Roles and responsibilities – The ScrumMaster, project team
  2. Agile Estimating
    • Reasons to estimate and measure
    • Basic estimating techniques
    • Values in agile estimating
    • Exercise: Do a relative estimate
    • Estimating size with story points
    • Estimating in ideal days
    • Techniques for estimating
    • Exercise: Derive an estimate using Planning Poker
    • When to re-estimate
  3. Agile Planning
    • Reasons to plan
    • The problem with traditional planning
    • The product backlog
    • Techniques for story prioritization
    • Exercise: Prioritize a product backlog using Planning Poker
    • Release planning
    • Exercise: Create a release plan
    • Iteration planning
    • Exercise: Create story tasks and produce an iteration plan
    • Estimating velocity
    • Exercise: Calculate team velocity for a product backlog
    • Planning for uncertainty
  4. Project Initiation and Release Planning
    • Role of the product owner
    • Establishment of project charter
    • Product backlog
    • Exercise: Build a product backlog
    • Setting priorities
    • Release planning
  5. Planning a Sprint
    • Conducting Sprint Planning Meeting
    • Part 1: Selecting a subset of the product backlog
    • Part 2: Developing the sprint backlog
    • Exercise: Build a sprint backlog
    • Developing sprint tasks
    • Exercise: Establish sprint plan tasks
  6. Running a Sprint
    • Conducting the daily Scrum
    • Managing the sprint scope
    • Scrum warning signs
    • Tracking progress/burndown
    • Exercise: Build and maintain burndown (59 minute Scrum)
  7. Closing a Sprint
    • Conducting a sprint review
    • Conducting a sprint retrospective
    • Inspecting and adapting the process
    • Reporting project status
    • Updating the backlog
    • Closing the project