Agile User Stories and Goal Modeling
Samedi Heng, Manuel Kolp, Yves Wautelet
M. Kolp - LSINF 1210: Information Systems and Project Management, 2017-2018
What is User Story?
2
o A text of maximum of two lines written from point of view
of end-users.
o Proposed by Kent Beck in eXtreme Programming (XP).
o The most used requirements artifacts in Agile Methods.
o Popularized by Mike Cohn in 2004: User Stories Applied.
What is User Story?
3
o The 3C:
 Card
 Conversation
 Confirmation (~Acceptance Test)
What is User Story?
4
o The 3C:
 Card
 Conversation
 Confirmation (~Acceptance Test)
What is User Story?
5
o Acceptance Test
 (Given) some context
 (When) some action is carried out
 (Then) a particular set of observable consequences should
obtain
o Example
 Given my bank account is in credit, and I made no withdrawals
recently,
 When I attempt to withdraw an amount less than my card's
limit,
 Then the withdrawal should complete without errors or
warnings
AgileAlliance
What is User Story?
6
o The 3C:
 Card
 Conversation
 Confirmation
https://elearning.industriallogic.com/gh/submit?Action=PageAction&album=composingUserStories&path
=composingUserStories/userStories/promise&devLanguage=None
Write User Story
7
o User story templates: As [WHO], I want [WHAT], so that [WHY]
o User story templates proposed by Mike Cohn:
I as a <role>,
I want <function>,
so that <business value>.
As a creator, I want to upload
a video, so that any users can
view it.
As a <type of user>,
I want <capability> ,
so that <business value>.
As a book buyer, I want to
search for a book by ISBN, so that
I can find the right book quickly.
As a <type of user>,
I want <some goal>,
so that <some reason>.
As a user, I can indicate folders not to
backup, so that my backup drive isn't
filled up with things I don't need saved.
Write User Story
8
User Story Templates
Write Good User Story?
9
INVEST
o Independent
o Negotiable
o Valuable to users or customer
o Estimable
o Small
o Testable
User Story Concept
10
o EPIC and THEME
o User Story Point: 1, 2, 4, 8, 16, 32, …
o Velocity: total of implemented story point of an iteration
https://www.linkedin.com/pulse/features-themes-
epics-story-tasks-scrum-hassan-bba-is-smc-sfc
User Stories Examples
11
o As a user I want to have a Job board.
o As a user I can search for a job.
o A a user I can search for a job by attributes like location, salary range, job title,
company name, and the date the job was posted.
o As a user I can view informaiton about each job that I matched by search
o As a user I can view detailed infomation about a company that has posted a job.
User Story is not
12
Use Case
User Story is not
13
IEEE-830 document requirements
User Story vs. Use Case vs. Requirements
14https://www.slideshare.net/SandraSvanidzait/user-stories-in-agile-software-development
User Story Management
15
User Story Iceberg
Mike Cohn
User Story Management
16
User Story Mapping
Source: Tarang Patel
User Story in Scrum
17
Product Backlog, Sprint Backlog, Product Backlog grooming
https://www.neonrain.com/agile-scrum-web-development/
User Story in Scrum
18
Release Burndown Chart
https://www.mountaingoatsoftware.com/agile/scrum/scrum-tools/release-burndown
User Story in KANBAN
19https://ketiljensen.wordpress.com/2009/10/31/kanban-the-next-step-in-the-agile-evolution/
User Story in KANBAN
20http://www.continuousagile.com/unblock/kanban.html
Goal-Oriented for Modeling User Stories
21
http://modernux.se/docs/userstorymapping/
Goal-Oriented for Modeling User Stories
22
Rationale Tree: i* framework graphical notation (S. Heng PhD Thesis)
Goal-Oriented for Modeling User Stories
23
Rationale Tree: Supporting CASE-Tool (S. Heng PhD Thesis)
User story View Rationale Tree View
Goal-Oriented for Modeling User Stories
24
Rationale Tree: Identifying EPIC user story and Theme (S. Heng PhD Thesis)
o Epic: top-level Task elements not issued from the refinement of another
Task element but that itself need to be refined in more elements (WHAT
Dimension).
o Theme: all elements under the scope of Task (EPIC) elements.

Agile User Stories and Goal Modeling

  • 1.
    Agile User Storiesand Goal Modeling Samedi Heng, Manuel Kolp, Yves Wautelet M. Kolp - LSINF 1210: Information Systems and Project Management, 2017-2018
  • 2.
    What is UserStory? 2 o A text of maximum of two lines written from point of view of end-users. o Proposed by Kent Beck in eXtreme Programming (XP). o The most used requirements artifacts in Agile Methods. o Popularized by Mike Cohn in 2004: User Stories Applied.
  • 3.
    What is UserStory? 3 o The 3C:  Card  Conversation  Confirmation (~Acceptance Test)
  • 4.
    What is UserStory? 4 o The 3C:  Card  Conversation  Confirmation (~Acceptance Test)
  • 5.
    What is UserStory? 5 o Acceptance Test  (Given) some context  (When) some action is carried out  (Then) a particular set of observable consequences should obtain o Example  Given my bank account is in credit, and I made no withdrawals recently,  When I attempt to withdraw an amount less than my card's limit,  Then the withdrawal should complete without errors or warnings AgileAlliance
  • 6.
    What is UserStory? 6 o The 3C:  Card  Conversation  Confirmation https://elearning.industriallogic.com/gh/submit?Action=PageAction&album=composingUserStories&path =composingUserStories/userStories/promise&devLanguage=None
  • 7.
    Write User Story 7 oUser story templates: As [WHO], I want [WHAT], so that [WHY] o User story templates proposed by Mike Cohn: I as a <role>, I want <function>, so that <business value>. As a creator, I want to upload a video, so that any users can view it. As a <type of user>, I want <capability> , so that <business value>. As a book buyer, I want to search for a book by ISBN, so that I can find the right book quickly. As a <type of user>, I want <some goal>, so that <some reason>. As a user, I can indicate folders not to backup, so that my backup drive isn't filled up with things I don't need saved.
  • 8.
    Write User Story 8 UserStory Templates
  • 9.
    Write Good UserStory? 9 INVEST o Independent o Negotiable o Valuable to users or customer o Estimable o Small o Testable
  • 10.
    User Story Concept 10 oEPIC and THEME o User Story Point: 1, 2, 4, 8, 16, 32, … o Velocity: total of implemented story point of an iteration https://www.linkedin.com/pulse/features-themes- epics-story-tasks-scrum-hassan-bba-is-smc-sfc
  • 11.
    User Stories Examples 11 oAs a user I want to have a Job board. o As a user I can search for a job. o A a user I can search for a job by attributes like location, salary range, job title, company name, and the date the job was posted. o As a user I can view informaiton about each job that I matched by search o As a user I can view detailed infomation about a company that has posted a job.
  • 12.
    User Story isnot 12 Use Case
  • 13.
    User Story isnot 13 IEEE-830 document requirements
  • 14.
    User Story vs.Use Case vs. Requirements 14https://www.slideshare.net/SandraSvanidzait/user-stories-in-agile-software-development
  • 15.
    User Story Management 15 UserStory Iceberg Mike Cohn
  • 16.
    User Story Management 16 UserStory Mapping Source: Tarang Patel
  • 17.
    User Story inScrum 17 Product Backlog, Sprint Backlog, Product Backlog grooming https://www.neonrain.com/agile-scrum-web-development/
  • 18.
    User Story inScrum 18 Release Burndown Chart https://www.mountaingoatsoftware.com/agile/scrum/scrum-tools/release-burndown
  • 19.
    User Story inKANBAN 19https://ketiljensen.wordpress.com/2009/10/31/kanban-the-next-step-in-the-agile-evolution/
  • 20.
    User Story inKANBAN 20http://www.continuousagile.com/unblock/kanban.html
  • 21.
    Goal-Oriented for ModelingUser Stories 21 http://modernux.se/docs/userstorymapping/
  • 22.
    Goal-Oriented for ModelingUser Stories 22 Rationale Tree: i* framework graphical notation (S. Heng PhD Thesis)
  • 23.
    Goal-Oriented for ModelingUser Stories 23 Rationale Tree: Supporting CASE-Tool (S. Heng PhD Thesis) User story View Rationale Tree View
  • 24.
    Goal-Oriented for ModelingUser Stories 24 Rationale Tree: Identifying EPIC user story and Theme (S. Heng PhD Thesis) o Epic: top-level Task elements not issued from the refinement of another Task element but that itself need to be refined in more elements (WHAT Dimension). o Theme: all elements under the scope of Task (EPIC) elements.