PMI-ACP Lesson 05 Agile Analysis and Design

Copyright 2014, Simplilearn, All rights reserved.1
PMI® & ACP are the registered marks of Project Management Institute, Inc. Copyright 2014, Simplilearn, All rights reserved.
Agile Analysis and Design
PMI®—Agile Certified Practitioner (PMI-ACP)®

● Explain Product and Iteration/Sprint backlogs
● Prioritize backlogs and determine Minimal Marketable Features
● Create Agile Personas and Wireframes
● Develop an Agile Charter
● Identify best practices for Agile Modeling
After completing
this lesson, you will
be able to:
Objectives

A product roadmap is a planned approach that
helps with strategic project planning and
communication of that plan with respect to
important product milestones. A Product
roadmap:
● forms an integral part of any product strategy;
● provides the framework to plan changes;
● manages the effect those changes would have
on the product; and
● represents the long term product vision/goal of
the product.
Agile Product Roadmap

Product Backlog
Product backlog always lists items adding value for the customer. It is maintained by the product
manager/owner and is the major input for release, wave, and iteration planning.
It includes:
● functional requirements;
● non-functional requirements; and
● product enhancement suggestions by various stakeholders.
The objective of creating a product backlog:
To expand the product vision, through an evolutionary requirements definition process. Items for
the closest couple of months are usually quite detailed, while items that will be worked on some 6-
12 months can be defined broadly and imprecisely.

A story map is an arrangement of the story cards which represents:
● the sequence in which the stories will be needed by the business on the horizontal axis; and
● the priority of the stories on the vertical axis.
Agile Story Maps
Blue cards represent a
user activity. The sequence
of blue cards indicates the
minimum marketable
features (MMF) for the
product.
For the team to actually
build the system, they
need to deliver some
subset of the pink cards,
which provide more detail
about the blue cards.

A Wireframe is a low fidelity, non-graphical prototype/artifact. The Wireframe should be simple with
no colors, graphics or other layout features.
● It shows the skeleton of a screen, representing its structure, and basic layout.
● It contains and localizes contents, features, navigation tools, and interactions available to the user.
Agile Wireframes are:
● black and white and are accompanied by some annotations to describe the behavior of the
elements, their relationships and their importance.
● often put in context within a storyboard and are refined frequently.
● used as a communication tool that serves as an element of conversation and confirmation of ’agile’
user stories.
Agile Wireframes

User stories combined with Wireframes are effective in capturing requirement from business.
Simplilearn Solutions Private Limited website, initially designed as a Wireframe, was populated
with videos and articles. The graphics below show the various versions of the website.
Agile Wireframes—Real Life Example
Website with
Wireframe
Design
Operational
Website with
videos and
articles
Course Name
Video Heading
Pick Location
Banner
Enroll Now
Banner
Key Features
Button Button Button
Search
Introduction Video

An Agile Charter is typically documented on a whiteboard. A chartering session helps a team:
● understand the parameters of team work and its context within the project;
● prepare them to make well-informed decisions going forward;
● identify the value the project will deliver to the business; and
● develop trust and confidence that is needed in the project.
Chartering
An Agile Charter answers the following:
● Why are we building this product?
● How will we know if it is successful?
● Who is the project community?

Three components of the Agile Project Charter are as follows:
Components of Agile Project Charter
Vision
Defines the “Why” of the project, higher purpose,
or the reason for the project’s existence
Mission
Defines the “What” of the project and states what will
be done in the project to achieve its higher purpose
Success Criteria
Management tests that describe effects outside of
the solution itself

Agile Persona is a central element of Alan Cooper’s interaction design. A persona is an imaginary
representation of a user role and a natural extension to user roles. Generally, avoid picking personas
who are real users.
Add details to each persona:
● Likes and dislikes
● When, where, why
● Model and make of car
● Job
● Goals
Agile Personas
Example of an Agile Persona:
Jason is a software developer who lives in Manhattan. He has
an apartment in SoHo and enjoys walking his Chihuahua
around the neighborhood chatting with people he runs into.
He uses an Apple Air for his programming and often spends
his day working in the Urban Grind coffee shop enjoying their
fresh ground cappuccinos. Jason is passionate about Agile
techniques and is an active member of the local Agile
Leadership Network.

Jiscs Digimap Services, to enhance their product, wanted to come up with a list of personas to
increase usability and user experience. After interviewing different people, five distinct personas
based on different user behaviours were distilled. This activity allowed the team to create a list of
features, which each of the persona would want to have. Based on the features envisioned, they were
then prioritized and developed.
Agile Personas—Real Life Example
Focus on the core audiences and their goals
Create a list of tasks for each persona
Avoid potential distractions from issues which are of little benefit to users

Agile Personas—Real Life Example (contd.)
The five distinct personas distilled from the interviews are shown below:

Agile Modeling
Agile Modeling is a collection of values, principles, and practices for modeling software that can be
applied on a software development project in an effective and lightweight manner.

Best Practices of Agile Modeling
There are several best practices followed in Agile Modeling:

Real Life Example
According to the 2011 CHAOS report from the
Standish Group, Agile projects are often more
successful than non-Agile projects.
The building blocks in the success of Agile process
are:
● Capturing requirements through user stories
● Use of Agile Personas and Wireframe
● Creating product roadmaps
● Story mapping
CHAOS Report, 2011 - Standish Group
“Agile process is the universal remedy for
software development project failure. Software
applications developed through the Agile
process have three times the success rate of
the traditional Waterfall method and a much
lower percentage of time and cost overruns.”
The details of the published CHAOS report
are:

Quiz

QUIZ
a.
b.
c.
d.
A story map is an arrangement of the story cards. The vertical axis will show________.
1
priority of the story
all the stories
manual entry of the story
stories needed by the business

QUIZ
a.
b.
c.
d.
A story map is an arrangement of the story cards. The vertical axis will show________.
1
Answer: b.
Explanation: The vertical axis shows the priority of the stories and the horizontal axis shows
the stories needed by the business.
priority of the story
all the stories
manual entry of the story
stories needed by the business

QUIZ
a.
b.
c.
d.
Which of the following is maintained by the product manager and is the major input for
release, wave, and iteration planning?2
Story map
Product backlog
Story cards
Iteration release

QUIZ
a.
b.
c.
d.
Which of the following is maintained by the product manager and is the major input for
release, wave, and iteration planning?2
Answer: c.
Explanation: Product backlog expands the product vision, through an evolutionary
requirements definition process, into a product feature list, or backlog. It is maintained by
the product manager and is the major input for release, wave, and iteration planning.
Story map
Product backlog
Story cards
Iteration release

QUIZ
a.
b.
c.
d.
Which of the following is a low fidelity prototype that shows a skeleton of a screen
representing its structure and basic layout?3
Chartering
Modeling
Wireframes
User story

QUIZ
a.
b.
c.
d.
Which of the following is a low fidelity prototype that shows a skeleton of a screen
representing its structure and basic layout?3
Answer: d.
Explanation: Wireframes is a low fidelity prototype that shows a skeleton of a screen
representing its structure and basic layout.
Chartering
Modeling
Wireframes
User story

QUIZ
a.
b.
c.
d.
How many product backlogs are there for four teams working on a major release?
4
2
3
4
1

QUIZ
a.
b.
c.
d.
How many product backlogs are there for four teams working on a major release?
4
Answer: a.
Explanation: There is only one product backlog regardless of the number of teams.
2
3
4
1

QUIZ
a.
b.
c.
d.
What is not a feature of an Agile Charter?
5
Written on a single piece of paper
Should explain the Why, What, and Success Criteria of the project
Is usually based on a Charter template from the organization’s PMO
Written on a whiteboard

QUIZ
a.
b.
c.
d.
What is not a feature of an Agile Charter?
5
Answer: d.
Explanation: The Agile Charter is intended to be lightweight and is not intended to be based
on a standard template.
Written on a single piece of paper
Should explain the Why, What, and Success Criteria of the project
Is usually based on a Charter template from the organization’s PMO
Written on a whiteboard

QUIZ
a.
b.
c.
d.
What does JBGE in Agile Modelling stand for?
6
Just Barely Good Enough
Java Bytecoder Generic Enhancement
None of the above
Job Based Governance and Engineering

QUIZ
a.
b.
c.
d.
What does JBGE in Agile Modelling stand for?
6
Answer: b.
Explanation: Just Barely Good Enough for the situation at hand and no more.
Just Barely Good Enough
Java Bytecoder Generic Enhancement
None of the above
Job Based Governance and Engineering

QUIZ
a.
b.
c.
d.
Where does the Product Backlog for an existing product come from?
7
Developers
Customer support staff
All of the above
Customers

QUIZ
a.
b.
c.
d.
Where does the Product Backlog for an existing product come from?
7
Answer: d.
Explanation: Customers, developers, product managers, and customer support staff can all
provide ideas for features in the product backlog.
Developers
Customer support staff
All of the above
Customers

● The Product Roadmap determines the vision and release structure for the
product. The Product Backlog supports it.
● Agile Story Maps determine the depth of features a product will contain.
● Lightweight Agile Wireframes are used to represent the layout and design of
a software product.
● Agile Chartering is lightweight and uses a whiteboard or single piece of
paper for the project vision.
● Agile Personas can be used to describe fictional users of the system.
● Various Agile Modeling techniques provide a collection of values, principles,
and practices for modeling software that can be applied on a software
development project in an effective and lightweight manner.
Summary
Here is a quick
recap of what was
covered in this
lesson:

PMI-ACP Lesson 05 Agile Analysis and Design

More Related Content

What's hot (20)

Viewers also liked (7)

Similar to PMI-ACP Lesson 05 Agile Analysis and Design (20)

More from Thanh Nguyen (16)

Recently uploaded (20)

PMI-ACP Lesson 05 Agile Analysis and Design