Call : (+91) 968636 4243
Mail :

Managing Agile Requirements

( Duration: 2 Days )

In Managing Agile Requirements training course, you will learn on to build a product backlog using a use case (or user story) model as input, and how to plan and 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.

Leveraging either the use case requirements approach or the user stories approach and Scrum’s agile project management approach gives you the ability to quickly develop working software that meets business needs. In Scrum, teams work in 30 day sprints to produce production-quality software driven by business priorities and using an empirical, adaptive approach. This course explains this approach’s values, key techniques, and how each team member contributes to success. This course blends ideas from Scrum, Extreme Programming (XP), and the Rational Unified Process (RUP).

By attending Managing Agile Requirements workshop, delegates will learn to:

  • 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

  • Basic Requirements Management knowledge and experience.

The Managing Agile Requirements class is intended for all who will actively participate in a project using Agile approach. People on the edges of the project (secondary customers, management staff, and others in related processes) will also benefit.



Agile Methodology Fundamentals

  • What are agile methods?
  • What is iterative development?
  • Principles of iterative development and industry accepted best practices
    • Agile methods’ values
    • Intro to Scrum/benefits vs. waterfall

Scrum in a Nutshell

  • What is Scrum and an overview of Scrum process flow
  • Scrum Roles and responsibilities - The ScrumMaster, project team
  • How does Scrum work and how do we conduct project planning?

Traditional Management vs. Scrum

  • Agile Leadership Principles – Servant Leadership, Empirical Management, Empowerment, Quality-First, Continuous Improvement, and "Standardization"

Use Case / User Stories Overview

  • What are use cases (or user stories)?
  • Describe how to develop a use case model / user story model
  • Describe the basic process for writing a use case specification (or user story) and describe the components
  • Discuss the relationship between use case / user story and user interfaces
  • Review tips for writing quality use case specification / user stories

Planning and Estimating

  • Planning Overview. Why do we plan and what makes a good plan?
  • How is agile planning different? Planning takes place at the Day, Iteration, and Release level
  • Estimation of Size and Duration. Story points vs. ideal days.
  • Ideal days
  • Planning Poker

Project Initiation and Release Planning

  • Role of the product owner
    • Lays out the responsibilities and expectations of the product owner and his/her relationship to the project team
  • Establishment of project charte
    • Overview of basis for scope of work, starting point for product backlog. Describe other project initiation activities
  • Product backlog
    • Definition of the product backlog, how it is established. Demonstrate how to size use cases / user stories
  • 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

Planning a Sprint

  • Conducting Sprint Planning Meeting
  • Part 1: Selecting a subset of the product backlog
    • Discuss how to determine the sprint scope including hangover
  • Part 2: Developing the sprint backlog
    • Discuss how to avoid hangover, estimate velocity, and establish a sprint goal
  • Developing sprint tasks
    • Topics covered include task granularity, dependencies, scheduling and assignment

Running a Sprint

  • Conducting the daily Scrum
    • Discuss 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
    • Learn how to handle the sprint being behind or ahead
  • Warning signs and how to address them
    • Covers common pitfalls and avoidance strategies and recipes for failure
  • Tracking progress/burndown
    • Methods for managing task completion. Covers burndown and progress tracking

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
  • Reporting project status
    • Discuss metrics, hangover, and velocity
  • Updating the backlog
    • Covers re-prioritization, injects and budget constraints
  • Closing the project
    • Summarization and definition of done

Encarta Labs Advantage

  • One Stop Corporate Training Solution Providers for over 6,000 various courses on a variety of subjects
  • All courses are delivered by Industry Veterans
  • Get jumpstarted from newbie to production ready in a matter of few days
  • Trained more than 50,000 Corporate executives across the Globe
  • All our trainings are conducted in workshop mode with more focus on hands-on sessions

View our other course offerings by visiting

Contact us for delivering this course as a public/open-house workshop/online training for a group of 10+ candidates.