MGMT 4066 – AGILE PROJECT

MANAGEMENT

CLASS 3 – BUSINESS ANALYSIS

AND REQUIREMENT GATHERING

Saifur Rahman (Saif)

MdSaifur.Rahman@georgebrown.ca
TODAY’S AGENDA:
• Value Stream Mapping
• User Story Identification and Prioritization
• Elements of a Good User Story
• Customer Satisfaction and the Kano Model
• Lean’s Seven Forms of Waste

2
TODAY’S LESSON EXPECTATIONS
• Define and describe a value stream map.
• Describe the MoSCoW approach to user story prioritization.
• Describe how business value can be identified using the Kano model.
• Identify Lean’s seven forms of waste.

3
AGILE PROJECT INITIATING
• Chapter 4: Capturing and Prioritizing
User Stories through the Value
Stream

4
VALUE STREAM MAPPING
• Also know as Process Mapping (in Business Analysis & Lean Six Sigma)
• Value stream mapping is a Lean management technique that analyzes
the current state of a process to identify and remove waste.
• The goal of value stream mapping is to design a more efficient future
state process.

5
VALUE STREAM MAPPING (CONT.)
• A stream flows most efficiently when there are no obstructions to affect its current.
• Obstructions can be any one of the three forms of waste: mura, muda, muri, or non-value
activities.
• A future state process is a re-envisioned process with obstructions removed to achieve
better efficiency, or flow, resulting in greater customer value.

6
VALUE STEAM MAPPING NODES AND ICONS

7
VALUE STREAM MAP EXAMPLE

8
VALUE STREAM/ PROCESS MAP EXAMPLE (SIMPLE)

https://www.youtube.com/watch?v=wLkvvqypq1E 9
VALUE STREAM/ PROCESS MAP EXAMPLE (DETAILED)

https://www.youtube.com/watch?v=l3mi-Y4leiM 10
VALUE STREAM/ PROCESS MAP EXAMPLE (MORE EXAMPLE)

https://www.youtube.com/watch?v=4W-vLESAhoo 11
IN-CLASS EXERCISE

• Consider your approach to organizing an event (birthday party or wedding).

Create a value stream/ process map. Identify where there may be areas of
improvement (or wastes).

12
PRIORITIZING REQUIREMENTS AND USER STORIES
• Value streams help identify requirements and user stories. Once identified,
requirements or user stories should be prioritized.
• 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.

13
MOSCOW PRIORITIZATION TECHNIQUE

Image source: https://www.productplan.com/glossary/moscow-prioritization/ 14

MOSCOW PRIORITIZATION TECHNIQUE

https://www.youtube.com/watch?v=QfZo9cxnQgY 15
BALANCING REQUIREMENT PRIORITY

For the purposes of planning, requirements should be

distributed across categories.
• Must-have requirements should not exceed 60 percent of the
overall distribution. A greater percentage can add additional
risk to the project.
• Could-have requirements should not exceed 20 percent of the
overall distribution. More than this would indicate that the
project may not be achieving business value, and numerous
superficial features or requirements are being implemented.
• Should-have requirements should represent the difference
between the must-have and could-have requirements.

16
USER STORY CARDS
• User stories typically follow a simple template: As a <type of stakeholder>, I
want <some goal> so that <some reason>.
• Additional elements of a user story include the following:
• Size/points—These are used to help estimate the user story for planning purposes.
• Business value—This captures the value the user story contributes to the organization,
project mission, or customer and can help prioritize the story.
• Verification criteria—These capture how the user story can be verified as complete
and will be covered later in this chapter.

17
USER STORY CARDS

18
USER STORY CARDS

https://youtu.be/LGeDZmrWwsw 19
USER STORY CARDS PRACTICE
• Practice exercise – prepare 3 user stories as the host for a birthday/ wedding event

20
WHAT WE LEARNED TODAY

• The role of value stream/ process mapping in identifying and creating user
stories and requirements
• Prepare a process map using the swimlanes

21
NEXT LESSON

• Capturing and Prioritizing User Stories

• Review of Assignment 1 draft + Prepare activity table
• Prepare an activity table with all the steps and actors (see sample below) for your
project
Steps Actors Activities
Step 1 Customer Calls restaurant for reservation
Step 2 Restaurant Manager Confirms availability
Step 3 Customer Visits restaurant
Step 4 Waitress Collects order
Step 5 Chef Cooks food
Step 6 Waitress Serves food
Step 7 Customer Pays bill

22
NEXT WEEK – CAPTURING AND
PRIORITIZING USER STORIES

Saif

MdSaifur.Rahman@georgebrown.ca