Agile Scrum Overview

Scrum Overview

Scrum is one of several Agile processes available today. Scrum’s Agile project management approach gives you the ability to quickly develop working software that meets business needs. In Scrum, teams work in cycles called “Sprints” to produce production-quality software based on business priorities using an empirical, adaptive approach. This course is a high-level introduction to this approach’s value and key practices.

You will learn the basics of any Agile approach, the three roles defined by Scrum, how to build a product backlog, and how to plan and work in Sprints.

Course Objectives

  • Understand key concepts and terms of Agile and Scrum
  • 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


This course is intended for anyone who is interested in learning about this approach. Since Agile and Scrum focus on “the team”, this course is beneficial to all software project roles, including the business partners who define the goals and needs of the business.




1-day session, 9:00 am-4:00 pm (?)



Course Outline:

  1. Agile Methodology Fundamentals
    • What are Agile methods?
    • What is iterative development? Covers the basics and principles of iterative development and industry best practices.
    • Agile methods’ values
    • Intro to Scrum/benefits vs. waterfall: Looks at a brief history of Scrum, a comparison to waterfall, and the advantages of Scrum.
  2. Scrum in a Nutshell
    • What is Scrum – an overview of Scrum process flow
    • Scrum Roles and responsibilities – Product Owner, Scrum Master, Team
  3. Traditional Management vs. Scrum
    • Agile Leadership Principles – Servant Leadership, Empirical Management, Empowerment, Quality-First, Continuous Improvement
  4. Planning and Estimating
    • Provides planning overview:  Why do we plan and what makes a good plan?
    • Explains how Agile planning is different:  Planning takes place at the Day, Iteration, and Release level
    • Estimation of Size and Duration.  Story points vs. ideal days.
    • Planning concepts – Story Points and Velocity
    • Estimation techniques.  Introduces planning poker and other techniques for estimating effort.
  5. Project Initiation and Release Planning
    • Lays out the responsibilities and expectations of the product owner and his/her relationship to the project team.
    • Initiating the project. Describes project initiation activities, including “Sprint 0”
    • Product backlog: Definition of the product backlog and how it is established.
    • Setting priorities: How the product backlog gets prioritized and maintained.  Focus is on the role of the product owner.
    • Release planning: Demonstrate how to use prioritized backlog, estimated velocity, and sprint goals to establish a release plan.
  6. Planning a Sprint
    • Conducting Sprint Planning Meeting
    • Part 1 – Selecting a subset of the product backlog
      Discuss how to determine the sprint scope
    • Part 2 – Developing the sprint backlog: Discuss how to estimate velocity, and establish a sprint goal
    • Developing sprint tasks: Topics covered include task granularity, dependencies, scheduling and assignment
  7. Running a Sprint
    • Conducting the daily Scrum: Explores the focus and conduct of the daily Scrum. Learn what is included and what is excluded. Learn the value of the daily Scrum.
    • Managing the sprint scope: Discuss tips and techniques for insulating the team from distractions.
    • Tracking progress/burndown
  8. Closing a Sprint
    • Conducting a sprint review: Demonstrate what is expected and covered in a sprint review.
    • Conducting a sprint retrospective: Discuss the purpose and scope of a sprint retrospective.
    • Inspecting and adapting the process: Discuss a key aspect of Scrum: inspect and adapt.  Emphasizes the importance of self-directed teams.
    • Reporting project status: Discuss metrics and velocity.
    • Updating the backlog: Covers re-prioritization, injects and budget constraints.
    • Closing the project: Summary and definition of “done.”