MGMT 4066 – AGILE

PROJECT MANAGEMENT

CLASS 5 – CAPTURING AND

PRIORITIZING USER STORIES:
WORKING SESSION
Costin Laurentiu

Costin.Laurentiu@georgebrown.ca
TODAY’S AGENDA:
• Capturing Requirements
• Creating User Stories
• Developing Use Cases

2
TODAY’S LESSON EXPECTATIONS
• Recap of Week 4
• Create User stories and User Story Cards
• Define and prioritize requirements
• Create Use Cases

3
USER STORIES
• User Story represents a small, concise statement of functionality or quality
needed to deliver value to a specific stakeholder.

Capturing the Need of

a Specific Stakeholder

Basis for Identifying

Needs and Price
Estimation, Planning
A Sentence or Two that
Describes who has the
Need Addressed by the
Story

• Statement of Value: "As a <who>, I need to <what>, so that <why>."

"Given...When...Then" is another common format.

4
USER STORIES
EXAMPLES

5
USE CASES AND SCENARIOS
• Use Cases and Scenarios describe how a person or system interacts with the solution
being modelled to achieve a goal.

Describe the interactions between the…..

Primary Actor Solution

Secondary Actor
• Use cases are usually triggered by the primary actor, but in some (Needed to achieve the
methods may also be triggered by another system or by an Primary Actor’s Goal)
external event or timer.
• Describe the possible outcomes of an attempt to accomplish a
particular goal that the solution will support.

6
USE CASES AND SCENARIOS

7
USE CASES AND SCENARIOS EXAMPLE

https://www.youtube.com/watch?v=oesoKbn0yeA 8
PRIORITIZE REQUIREMENTS
• Purpose: Rank requirements in the order of relative importance.
• The act of ranking requirements to determine their relative importance to
stakeholders.
• Prioritization is an ongoing process, with priorities changing as the context changes.
• Prioritization is a critical exercise that seeks to ensure the maximum value is
achieved.

9
BASIS FOR PRIORITIZING REQUIREMENTS
• The basis on which requirements are prioritized is agreed upon by relevant stakeholders
(and determined by product owner). Typical factors that influence prioritization include:
• Benefit
• Penalty
• Cost
• Risk
• Dependencies
• Time Sensitivity
• Stability
• Regulatory Compliance

10
MOSCOW PRIORITIZATION MODEL
• The MoSCoW prioritization model, developed helps to organize and structure
requirement and user story priority.
• Must-have requirements—These requirements are mandatory. The project cannot
launch unless they are fulfilled.
• Should-have requirements—These requirements are high priority. Their absence may
not prevent a project from launching but may prevent an organization from realizing
the full benefit of the project.
• Could-have requirements—These requirements aren’t as high in priority but could
represent additional value.
• Won’t-have requirements—These requirements will not be included in a release or
project. They can be included in later phases, but for the purpose of the project, are
removed from planning and further discussion.

11
LEAN’S SEVEN FORMS OF WASTE
Another method of identifying value is the elimination of waste. Value stream mapping
identifies obstacles that are impeding a process from achieving optimal flow. Business value
can be assigned to a story by identifying the type of obstacle(s) a story removes. Lean
identifies seven forms of waste:
1. Transportation waste—Materials, information, or resources are unnecessarily moved to fulfill a process.
2. Waiting waste—Resources are idle while they wait for a dependent process or activity to be completed.
3. Overproduction waste—Resources are producing more than necessary to achieve customer needs.
4. Defect waste—The process results in an unacceptable outcome.
5. Inventory waste—Additional resources or work in progress items do not directly contribute to or impede
a process’s ability to achieve customer value.
6. Movement/ Motion waste—Materials, information, or resources are excessively moved to complete a
specific process activity.
7. Extra processing waste—Work is performed that is not required to satisfy the customer need.

12
USER STORY CARDS

13
PRACTICE USER STORY DEVELOPMENT
From the following scenario, select one or two steps that can be improved –
• Find at least two wastes (from the 7 waste of Lean) in one of the steps and
develop one process improvement project to improve this step(or steps)
• Develop 2 user stories in a user story card format (see previous slide)
• Prepare one use case scenario, showing the interaction of the primary actor
with the system/ proposed project.

14
PRACTICE USER STORY DEVELOPMENT
Steps Actors Activities
Step 1 Customer Call restaurant for reservation
Step 2 Res Manager Confirm reservation
Step 3 Customer Order food
Step 4 Waiter Receive food order
Step 5 Chef Cooks food
Step 6 Waiter Bring food to the table
Step 7 Customer Pay bill
Step 8 Customer Write a review

15
ASSIGNMENT 2

• Team Formation
• Assignment 2 introduction

16
WHAT WE LEARNED TODAY

• How to create user stories

• How to prioritize user stories using the MoSCoW model
• How to create high-quality user stories
• How to prepare the User Story Card
• How to create the Use cases

17
NEXT LESSON

• Building Agile Project Teams

18
NEXT WEEK – BUILDING AGILE
PROJECT TEAMS

Costin Laurentiu

Costin.Laurentiu@georgebrown.ca