Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

User Story:

Agile process. Usage of user stories and use cases. WIKI and TFS
by

Tadas Makčinskas

on 14 June 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of User Story:


Story:
"In order to REACH A GOAL as a ROLE I do SMTH"
Size: __
Acceptance criteria:
<list>
acceptance criteria 1

Notes / references to other sources:

Use CASE

sized to deliver business value, not bound in size
usually
permanent artifact
, useful for maintenance and further development
hard to use while discussing business goal
great tool to
document requirements
after decisions are made
tends to focus on
software implementation


Title:
"DO SMTH"

Main path:
<#list>
Steps [max=9]
(only one level of hierarchy)

Extensions:
<#list>
Of extensions in main scenario
(all exceptions and scenario extensions goes here)
Including UI
related requirements to UC

Adding to much detail
into UC

Starting
using multiple levels of hierarchy
in main path instead of adding it within Extensions

Creating UC for each UI
UC Common mistakes to avoid
!
User STORY

small & bound to size (i.e. sprint length)
used in
scheduling work
is
temporal
is a great
reminder
for further discussions while creating a solution
great tool to
gather
and
transit requirements
in various meetings for various groups
tends to focus on
business solution

Writing

user stories for
Client, Product Owner
or
Developer
as a ROLE

Not including Reason (business value)
in a story

Absent
Acceptance Criteria
US Common mistakes to avoid
!
UML panaudos atvejis ir lietuviu kalba
atnaujinti konfiguraciją

pateikti naują užsakymą
kur reikia panaudoti būdvardžius (atsakant į klausimą
Kokią(-į)?
)
aprašyti veiksmą
neatsakinėti į klausimą
Kam?
neatsakinėti
Ką ... daro?
....
nenaudoti
bendrinių pavadinimų

(pvz. konfiguracijos atnaujinimas)
Ką galiu daryti?
Full transcript