Webinar-Use-Cases-And-User-Stories-For-Agile-Requirements.pdf

Requirements Principles Identify the principles that lead to effective Agile requirements ZẾSI #2 5ñäxz: Setting the Stage for Establish the vision as the — Identify the different lev

Use Cases and User Stories

for Agile Requirements

Peter Schmidt, PMP, PMI-ACP, CPL VP, Client Services, ESI International

oschmidi@esi-intl.com

2 AEE MODERN

analyst

Requirements Principles

Identify the principles that lead to effective Agile requirements

ZẾSI #2 5ñäxz:

Setting the Stage for

Establish the vision as the — Identify the different level foundation of Agile

requirements of Agile requirements for effective requirements

building talent, driving results 2

Agile Requirements Principles Requirements Principles

Just in-time detail

a at) ay A am amy amy

LD) LD)” <<)” <A” <A” <A”

Prioritized top down

Please Take the Poll

= What are the challenges you face when it comes to writing good requirements?

Think breadth then depth

Break it down into small chunks Collaboration

Following INVEST (Independent, Negotiable, Valuable, Estimate-able, Small, Testable)

lyst

ESI satis 7 building talent, driving results 5

Writing Good Requirements Requirements Principles

™ anal + lưng ` I KIÊN = building talent, driving results

Setting Project Direction lá ca

Revisit the vision periodically and

Revisit the vision revise it based on feedback,

Innovative ideas, and needed change

Describe what the project | Focus on attainable goals

will look like in the future Identify potential problems

Examine patterns and and risks relationships throughout the

project Balance opportunities and

™ anal ` ESI | =— 7 building talent, driving results 7

Agreeing on Project Deliverables

Documents:

Artifacts needed after

project

needed during Documents:

Required

building talent, driving results

Deliverables

MC RATT Release Planning

Agreeing on Project Deliverables

0 Vision Document 0 Executable Process Models Business

O Resource Plan (PM) Ci Enterprise Architecture Model (EA) Ci Feature Design Abstract Help Documentation CO Communication Plan (PM) Software Architecture (ARCH) New As-IS Business Processes

(BPE)

O High Level story backlog 0 Story Backlog (Functional, Non-

Functional, Change Management) Data Architecture (DA) 0 ICD/Serice Definition (SA) Features, Stories, Acceptance

Tests, Business Rules (SA)

O Project Financials (PM) ~ Release Plan O Network/Deployment Architecture

(CM) ” WSDL Documentation (DEV)

C Enterprise Architecture Document

(EA) (EA) C Enterprise Architecture Document D Master Testing Plan (TE) 0 Data Dictionary (DA) Technical

Agreeing on Tools Setting the Stage for Requirements

Project Initiation

1 Portfolio Tracking Tool (add

project business case and supporting docs for approval]

Agreeing on Tools

Release Plannii\

D Ñile Projert Tool {add resources,

setup initial backlog and release plan)

lterafl0n\ Ì

0 Agile Project Tool (groom backlog

and release plan, track progress)

Setting the Stage for Requirements

Waa Ta

Agile Project Tool (groom backlog

and release plan, track progress)

WOR Cr

0 Agile Project Tool (close

project after product owner acceptance)

C Enterprise Business Repository

(checkout as-s process models) working/final deliverable folders) 0 Sharepoint (setup project 0 Test Environments O System Architect (update mapping} © Enterprise Business Repository (check-in new

process models, coordinate with

@

ESI Se! analyst building talent, driving results

From Portfolio Ideas to Team

Levels of Agile Requirements

Build Story Release Iteration

Team Backlog Plan

building talent, driving results

Example Requirement Levels Levels of Agile Requirements

Theme Job Seeker

Feature Management Hesume

Please Take the Poll

EpIcs — Portfolio Level Levels of Agile Requirements

= They represent the “2" layer of abstraction” in Themes

lyst

SI ana ys! building talent, driving results

INTERNATIONAL

EpIcs — Portfolio Level Levels of Agile Requirements

Architectural Epics—Portfolio Level -evels of Agile Requirements

infrastructure side of initiatives

= Architectural epics represent large scale implementations that could require execution

in Waterfall practices as well as Agile

`

` x

¬

—— —_~ oe

~-_

—_

_ ~~ ¬— ¬ —

atl

- —

- => co

ww

a 4

“

` 4 _

ESI ats = building talent, driving results

Go-See and understand “What do

they do today? Why is it not

working?”

Use interviews, shadowing, surveys, and market research to understand true needs

Visioning Summary Setting the Stage for Requirements

Start collecting high level themes and features here that lead to defining the scope of the effort

ESI te KIÊN = building talent, driving results

Setting the Stage for

of major processes Diagrams

and high level ¢ Facilitator Led * High Level process steps for the Visioning Workshop Process Diagrams

system ui ¢ Ul Flow Diagrams

¢ Who needs to do What? men we modeling eams Breakout ¢ Backlog (high level)

Features — Program Level hit bu bu Requirements

Features — Program Level ita Requirements

Features are important for Agile teams to plan and estimate iterations

SI Se! analyst building talent, driving results

INTERNATIONAL

Challenges tn Prioritizing Features Levels of Agile

for the Program Backlog Requirements

=" Product managers want to avoid prioritizing features for

= Quantification of value for

competitive — this is often too abstract in nature to prioritize =" Comparing “apple” features to

“oranges features can be very challenging

What is a Story? Levels of Agile Requirements

requirement statement = Understandable

from the perspective of = Independent

= Stories should be = Valuable documented and visible = Estimable

SI ana ys} building talent, driving results

INTERNATIONAL

Levels of Agile

Characteristics of a great user story:

" They are short and easy to read s They are captured in a ‘list format’ large

BRD’s not welcome here! » They can be discarded after

implementation = They represent small increments of

functionality They should be relatively easy to estimate Detailed system behavior is NOT captured

User Stories — Team Level Levels of Agile Requirements

Characteristics of a great user story;

" Card

" 2or3 sentences to describe intent of story " Format: As a <role> | can <activity> so that <business value>

"= Conversation

=» The card in essence Is the introduction to a conversation

between, product owner, developers, users, team, customer etc,

in short all stakeholders involved The conversation is intended to

seek clarity and drive out details =" Confirmation

"= = Acceptance test, has the story been implemented according to conditions of satisfaction?

ESI KIÊN = building talent, driving results

Requirements Writing Workshops Setting the Stage for Requirements

stories as possible Prepare the room with post-it notes, flip charts and markers

Need an effective facilitator to run these

meetings to keep folks on track Establish Meeting

Norms!

building talent, driving results

Identifying Stories Levels of Agile Requirements

Depending on your project type, there are several ways to identify stories such as:

Please Take the Poll

= When developing Agile requirements, what modeling techniques do you use?

Use Case Modeling

Process Modeling Business Information Modeling = None

lyst

ESI as = building talent, driving results so

Personas Levels of Agile

Requirements

= Personas are like ‘avatars’ that represent different

customer segments for your business They stand-in for

Levels of Aglle

What Are They? When to Use Them?

the Actors and their Goals = When identifying Themes

systems = For communicating a simple

visual representation of the project scope

SI ana » building talent, driving results

INTERNATIONAL

Levels of Agile

= Hesearch the domain and

Interview real users

= Perform surveys to identify true

needs, behaviors and characteristics

= Brainstorm the initial set of roles

with product owner and SMEs

= Organize the set

= Consolidate and prioritize the target roles

SI Se! analyst building talent, driving results

INTERNATIONAL

sample Use Case Diagram Levels of Agile Requirements

Release 2) Customer Support

Sample Questions to Ask setting the Stage for Requirements

y ¢ What are you trying to achieve? Why?

The Levels of Requirements SEIS Or gi Requirements

INTERNATIONAL

Example Theme—Feature—Story Sàn I6 GÌ GMM Requirements

find it 2 AS an employer | want to

modify a job posting so it is correct

3 As an employer | want view a list of my open job postings so | can analyze them

SI ana ys} building talent, driving results

INTERNATIONAL

Levels of Agile

1 As an employer | 1 UAT1—Verify that only an authorized user

want to post a job so with a valid employer account can post a job

others can find it 2 UAT2—-Verify that a duplicate job posting

5 UAT5—Verify that the screen fields pass our

standard field format rules (link here to doc)

6 UAT6—Verify that all required fields are

entered (list them or link to UI Prototype)

lyst

ESI satis = building talent, driving results

Example Story—Tasks Levels of Agile Requirements

1 As an employer | 1 Create a database table to store the job posting

want to post a job so _°C!al's:

others can find it 2 Design and build the screen for job posting

3 Write the automated acceptance tests 4 Code, unit test and automate UAT1

5 Document/record the on page video help for the job

Agile Requirements Elicitation

Techniques

‘Visioning ¢ Interviews/Surveys ¢ User Roles, Personas ¢ Use Cases Diagrams ¢ Process Diagrams ¢ Ul Flow Diagrams

Setting the Stage for Requirements

~\_/ Breakdown/Slicing

¢ CRUD ¢ Business Rule ¢ Process Steps

Pulling It All Together

Levels of Agile Requirements

EFFECTIVE/AGILE REQUIREMENTS GATHERING CHEAT SHEET

© Prepare Yourself (skills) © Product Vision © Post-it Note Brainstorming © Identify Stakeholders © Conditions of Satisfaction © Story Mapping

e Understand Problem e Profile Users/Personas e Break Down EPICS

e Design the Approach © Context Diagram © Non-Functional

Requirements

© Identify Dependencies © Identify Proof of Concept

© Prioritize Next Release

e Plan Next Release

© Schedule Sessions e Use Case Diagrams

© Business Processe Diagrams

e UI Sitemap/Strawman e Themes/Features List e Prioritize Roadmap

Acceptance Tests

Test Examples Business Rules User Interface Prototypes Detailed Activity Diagrams

Requirements Gathering Process Requirements Requirements

Acceptance Testing e Setup Test Data

© Collaborate Closely with

Developers and Users

User

Focused

Process

Focused Theme Focused

Bottom

Up Non-Functional Requirements Requirements

Brainstorming Deep-Dive Testing Active Stakeholder Participation | Use Simple Visual Models | Use Simple Tools | Model with Others | Model with a Purpose | Just Enough

CRUD

Business

Rules User/ Platform

ults

Thanks for listening!

Peter Schmidt, PMP, PMI-ACP, CPL VP, Client Services, ESI International

oschmidi@esi-intl.com

www.esi-intl.com

Z&I #⁄« analyst