The presentation was held at CodeCamp Iasi - Oct 2014

1. 1

2. As a BA I want to detail clear
stories
Cristian Leon | BA | Yonder
2

3. BA?
3

4. Agile?
4

5. Tell me a story
Traditional requirements
HLR + User stories = LOVE
5

6. 6

7. What to keep in mind when detailing
US?
INVEST | DOR | DOD
7

8. UI &UX
present in
the story
when
refining it
8

9. Negotiate the Acceptance
Criteria with the PO
functional | nonfunctional
Agreed by everyone
9

10. Mistakes I did
- horizontal slicing
- too much vertical story slicing
- excessive info
- vague AC
- all titles started: “As a user I want to..”
- multiple stories “in progress” at the same time
- broken traceability
10

11. Template for a US
1.Title
2.Description
3.Goal
4.Current functionality
5.Acceptance criteria
6.Wireframe / Mockup / Prototype / Diagram
7.Technical info
8.Clarifications
11

12. 1. Title
Search registered books by title
12

13. 2. Description
As a librarian I want to be able to search the registered books
by their title, so that I can efficiently find them for students.
The search criteria represents letters and numbers and the
title are already available in our DB.
The application is for 20 libraries, each with 20 librarians.
Results will be displayed in a list, 50rows/page, 10 columns.
13

14. 3. Goal
Extend the search functionality by using the tile.
14

15. 4. Current functionality
- Existing application
- Existing search window.
- Currently, a librarian can search books only by their ISBN code
15

16. 5. Acceptance criteria
Functional:
- If >5 results, see multiple pages links
Non-functional:
- concurrency: 40.000 librarians can search books in the same
time by IBAN
16

17. 6. Visual representation(s)
Wireframe (LF) / Mockup (HF) / Prototype (Int) / Diagram
17

18. 18

19. 7. Technical info
- DB with titles
- Configuration files
- Technical documentation (architecture)
19

20. 8. Clarifications (as attachments)
E-mails
Meeting
notes
Sketches
20

21. Template for a US
1.Title
2.Description
3.Goal
4.Current functionality
5.Acceptance criteria
6.Wireframe / Mockup / Prototype / Diagram
7.Technical info
8.Clarifications
21

22. read the story (please)
- grooming agenda sent 3 days in advance
- 2 grooming sessions per sprint
- keep it enjoyable
- ask each team-member to present 1 story during
grooming
- ask the tough questions
- give the bad news early and often
- 1:1
- link sprint success with grooming
22

23. Ways to handle non-US
Spikes – log them separately issue tracker, 0sp, time-boxed
Administrative story – avoid it. If required, 0sp and drag each sprint
Horizontal story – avoid it. If required treat as a normal story
23

24. BA toolset
24

25. Confluence - team collaboration tool -
www.atlassian.com/software/confluence
25

26. Jira (issue tracker) www.atlassian.com/software/jira
26

27. RTC (issue tracker) www-03.ibm.com/software/products/en/rtc/
27

28. 28
Mingle (trial issue tracker)
www.thoughtworks.com/products/mingle-agile-project-management

29. Lumzy – (free) www.lumzy.com/
29

30. MockUpBuilder - mockupbuilder.com/
30

31. Balsamiq – www.balsamiq.com
31

32. Pencil - pencil.evolus.vn/
32

33. MS Visio - www.office.microsoft.com/en-001/visio/
33
User login
Login checks OK NO
YES
Home Page
Error message
Open task which
displays the map
YES
Map loads area and
zoom as configured
Map is displayed with
area and zoom
NO

34. Draw.io (free) www.draw.io
34

35. pen&paper - (free)
35

36. Food for thought
“I believe the role of analysis is vital, and that a good
business analyst is of benefit to any team.
However, the temptation for an experienced analyst to
slip back into being a buffer between the IT team and the
customer, enabling each to become lazy in
communicating with the other is a constant danger.”
http://www.infoq.com/articles/agile-business-analyst-role by
Shane Hastie
36

37. Questions | Answers
Cristian Leon | BA | Yonder
Codecamp v10.14
37

38. 38