B e i ng a B A
Te c h n i c a l E x c e l l e n c e
J ul y 3 0 , 2 0 1 3
An Introd Intr oduction uction to User User Sto Stories: ries: “ C h a n g i n g tOn h e ce w aUpon y o r gaa n i z a t i… ons change.” Time Time
Q&A wit w ith h Tom Kar Karasm asmanis anis
Changing Change. Develop the Professio Professional. nal. Develop the Profession. © Internatio International nal Institute of Business Business Analysis Analysis
2
Tom Karasmanis •
IIBA Product Manager & Host Being a BA: Technical Excellence
Tom Kar asmanis is a Seni or Consultant with over 25 year s' experience in IT, including roles as a Business Arc hitect, Business/Systems Analyst, Project Leader, Technical Architect, and Software Engineer. He has worked i n publishi ng, healthcar e, public sector, banking, financial services, insurance, supply chain, telecommunications, and retail.
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 B e i n g a B A : T e c h n i c a l E x c e l l e n c e . Tom is a management c onsultant in enterpr ise business analy sis and business arc hitectur e, and assists organizations to build their BA practic es. He speaks regularly at international c onfer ences.
Tom holds a Bachelor of Applied Sc ienc e in Chemic al Engineeri ng fr om the University of Toronto and lives in Toronto, Canada. 3 © International Institute of Business Analysis
How to Participate •
Ask Questions!
Use th e Qu estion b ox Qu estions can b e for a wide range of topics, from use cases to requirements to managing stakeholders to modeling Short questions please If the answer is too deep for this show, ch eck th e forum Download this presentation and leave comments at
http://community.IIBA.org/TechnicalExcellence 4 © International Institute of Business Analysis
Main Points
Agile • Basic intro for context
User Stories • • • •
W hat they are Principles for good ones Templates S am p les
5 © International Institute of Business Analysis
Agile Extension to the BABOK ® Guide
W HAT IS AGILE?
6 © International Institute of Business Analysis
What is a Agile? Agile Extension to the BABOK ® Guide Agile Manifesto (www.agilemanifesto.org) clearly defines what agile means, and the principles that support it
7 © International Institute of Business Analysis
What is a Agile? Manifesto for Agile S/W Development
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to chan ge over following a plan
8 © International Institute of Business Analysis
Agile Teams Teams of cross-functional developers with skills such as: • Business analysis • Technical design • Software development • QA • UI design • Architecture 9 © International Institute of Business Analysis
Agile and Business Analysis •
Requirements are elicited and refined through an iterative process of: Planning Defining acceptance criteria Prioritizing Developing Reviewing the results
10 © International Institute of Business Analysis
Agile and Business Analysis •
Agile business analysis is about ensuring: The right information is available to the development team In the right level of detail At the right time So they can build the right product
11 © International Institute of Business Analysis
Agile and Business Analysis Techniques are similar Timing and how they are used are different
•
Changes Artefacts are as lightweight as possible Focus on artefacts closer to the code
• Design models over requirements documents © International Institute of Business Analysis
12
Agile – Scrum •
Most predominant process Agile process framework is Scrum
4 formal meetings (ceremonies) • Sprint planning • Daily scrum (aka stand-up) • Sprint reviews • Sprint r etrospectives
13 © International Institute of Business Analysis
Agile – Scrum •
Artefacts
Product Backlog (or just Backlog) • List of ‘ requirements’ prioritized by customer value – highest to lowest • Continually updated and reprioritized • ‘Requirements’ documented as user stories • At each sprint identif y user stories f or sprint • Always working on items of highest © International Institute of Business Analysis
14
Once Upon a Time …
T HE USER STORY
15 © International Institute of Business Analysis
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
16 © International Institute of Business Analysis
Description of a User Story Includes a short description of the problem to be solved From the user’s perspective Only detail needed is information that reduces the risk of misunderstanding by developers that create the estimate Can be functional or non-functional
17 © International Institute of Business Analysis
Good User Stories •
INVEST criteria: – any sequence N egotiable – not too much detail V aluable – identify user/stakeholder value E stimable – usable for planning S mall – fits into a sprint/iteration T estable – acceptance criteria ( TCs) 18
I ndependent
© International Institute of Business Analysis
User Story Includes … Actor: Stakeholder who benefits from the user story. Description: A high-level overview of what functionality the user story includes. Benefit: The business value the story delivers. A user story should also have defined Acceptance and Evaluation 19 Criteria
© International Institute of Business Analysis
Structure of a User Story •
Title (optional) Describes an activity that the user wants to carry out with the system Typically, it is an active ‐ verb goal phrase, similar to the way use cases are titled
20 © International Institute of Business Analysis
Structure of a User Story •
Description No mandatory structure for user stories Most popular format includes:
• User role or persona [W HO] • Necessary action / behaviour / f eature [WHAT] • Benefit or business value received by the user when the story is implemented [WHY] 21 © International Institute of Business Analysis
Templates •
Typical format
•
As a I need to so that
Alternative format (priority focused):
In order to as a I need to © International Institute of Business Analysis
22
Example User Story
As a Security Officer , I need to print a report of all after hours accesses to the building so that I can search for unauthorized access
23 © International Institute of Business Analysis
Template As a/an …
I want to …
So that …
Player
Register for practice sessions
I can improve my skills
Administrator
Create practice sessions
Players can register
…
…
…
24 © International Institute of Business Analysis
Co mmunit y. I I B A. o r g | I I B A. o r g | inf o @I I B A. o r g
Tom Karasmanis
.
IIBA ® Prod u ct Manag er, Vend or Sh owcase Web inar .
IIBA ® Prod u ct Manag er, Tech n ical Excel l ence Web in ar .
http://community.IIBA.org/TechnicalExcellence .
[email protected] .
@t0mkar
If you have questions, concerns or comments about this webinar, please contact
[email protected]. 25
© International Institute of Business A nalysis
.
25
