2013-07-30 ba technical user stories

7/30/2019 2013-07-30 BA Technical User Stories

1/25

Changing the way organ izat ions change.

Being a BA Technica l Exc el le nce July 30, 2013

An Introduction to User Stories:Once Upon a Time

Q&A with Tom Karasmanis


2/25

Changing Change.

Develop the Professional. Develop the Profession. International Institute of Business Analysis

2


3/25

International Institute of Business Analysis

3

Tom Karasmanis

IIBA Product Manager & HostBeing a BA: Technical Excellence Tom Kar asmanis is a Senior Consultant with over 25 year s'

experience in IT, including roles as a Business Architect,Business/Systems Analyst, Project Leader, Technical Architect, and

Software Engineer. He has worked i n publishi ng, healthcar e, publicsector , banking, f inancia l serv ices, insurance, supply chain,

te lecommunicat ions, and reta i l . Tom served as the Chief Architect of the IIBA from 2009 to 2011. He is

now Product Manager & Host of two IIBA webinars: Vendor Showcase

and Being a BA: Technical Excel lence. Tom is a managementc onsultant in enterpr ise business analy sis and business arc hi tectur e,

and assists organizat ions to bui ld their BA pract ices. He speaksregular ly at internat ional c onfer ences.

Tom holds a Bachelor of Appl ied Sc ienc e in Chemic al Engineeri ng fr om

the University of Toronto and l ives in Toronto, Canada.


4/25

Ask Questions!

Use the Question box

Questions can be for a widerange of topics, from use casesto requirements to managing

stakeholders to modeling Short questions please

If the answer is too deep for this

show, check the forum


4

How to Participate

Download this presentation and leave comments at

http://community.IIBA.org/TechnicalExcellence


5/25

Agile

Basic intro for context

User Stories What they are

Principles for good ones

Templates

Samples


5

Main Points


6/25

WHAT IS AGILE?

Agile Extension to the BABOK Guide


6


7/25


7

What is a Agile?

Agile Extension to the BABOK

Guide

Agile Manifesto

(www.agilemanifesto.org) clearly

defines what agile means, and theprinciples that support it


8/25


8

What is a Agile?

Manifesto for Agile S/W Development Individuals and interactionsover processes

and tools Working softwareover comprehensive

documentation

Customer collaborationover contractnegotiation

Responding to changeover following a plan


9/25


9

Agile Teams

Teams of cross-functionaldeveloperswith skills such as:

Business analysis

Technical design

Software development QA

UI design

Architecture


10/25


10

Agile and Business Analysis

Requirements are elicited andrefined through an iterativeprocess of:

Planning

Defining acceptance criteria

Prioritizing

Developing Reviewing the results


11/25


11


Agile business analysis is aboutensuring:

The right information is available tothe development team

In the right level of detail

At the right time

So they can build the right product


12/25


12


Techniques are similar

Timing and how they are used aredifferent

Changes

Artefacts are as lightweight aspossible

Focus on artefacts closer to thecode

Design modelsover requirementsdocuments


13/25


13

Agile Scrum

Most predominant process Agileprocess framework is Scrum

4 formal meetings (ceremonies)

Sprint planning

Daily scrum (aka stand-up)

Sprint reviews

Sprint retrospectives


14/25


14

Agile Scrum

Artefacts

Product Backlog (or just Backlog)

List of requirementsprioritized by

customer value highest to lowest

Continually updated and reprioritized Requirementsdocumented as user

stories

At each sprint identify user stories for

sprint

Always working on items of highest


15/25

THE USER STORY

Once Upon a Time


15


16/25


16

User Stories are Used To

Prioritize work into iterations/sprints

Identify risks

Estimate effort (for sprint and total)

Establish a common understanding

of business need to be implemented


17/25


17

Description of a User Story

Includes a short description of theproblem to be solved

From the users perspective

Only detail needed is information

that reduces the risk ofmisunderstanding by developersthat create the estimate

Can be functional or non-functional


18/25


18

Good User Stories

INVEST criteria:

Independent any sequence

Negotiable not too much detail

Valuable identify user/stakeholder

value

Estimable usable for planning

Small fits into a sprint/iteration Testable acceptance criteria (

TCs)


19/25


19

User Story Includes

Actor:Stakeholder who benefitsfrom the user story.

Description:A high-level overview ofwhat functionality the user story

includes. Benefit:The business value the

story delivers.

A user story should also have

defined Acceptance and Evaluation

Criteria


20/25


20

Structure of a User Story

Title (optional)

Describes an activity that the userwants to carry out with the system

Typically, it is an activeverb goal

phrase, similar to the way use casesare titled


21/25


21

Structure of a User Story

Description

No mandatory structure for userstories

Most popular format includes:

User role or persona [WHO] Necessary action / behaviour / feature

[WHAT]

Benefit or business value received bythe user when the story is implemented

[WHY]


22/25


22

Templates Typical format

As a I need to so that

Alternative format (priorityfocused):

In order to as a I need to


23/25


23

Example User Story

As a Security Officer,I need to print a report of all after

hours accesses to the buildingso that I can search for

unauthorized access


24/25


24

TemplateAs a/an I want to So that

Player Register for

practice sessions

I can improve my

skills

Administrator Create practicesessions

Players canregister


25/25

Community. I IBA.org | I IBA.org | [email protected]

. Tom KarasmanisIIBA Product Manager, Vendor Showcase Webinar

.

IIBA

Product Manager, Technical Excel lence Webinar. http://community.IIBA.org/TechnicalExcellence

. [email protected]

. @t0mkar

If you have questions, concerns or comments about thiswebinar, please contact [email protected].


25. 25

2013-07-30 ba technical user stories

Documents