cristian leon as a ba i want to write clear stories
DESCRIPTION
CodeCampIasi25Oct2014TRANSCRIPT
1
2
As a BA I want to detail clear stories
Cristian Leon | BA | Yonder
3
BA?
4
Agile?
5
Tell me a story
Traditional requirements
HLR + User stories = LOVE
6
7
What to keep in mind when detailing US?
INVEST | DOR | DOD
8
UI &UX present in the story
when refining it
9
Negotiate the Acceptance Criteria with the PO
functional | nonfunctional
Agreed by everyone
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
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
12
1. Title
Search registered books by title
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.
14
3. Goal
Extend the search functionality by using the tile.
15
4. Current functionality
- Existing application - Existing search window.- Currently, a librarian can search books only by their ISBN code
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
17
6. Visual representation(s)
Wireframe (LF) / Mockup (HF) / Prototype (Int) / Diagram
18
19
7. Technical info
- DB with titles - Configuration files- Technical documentation (architecture)
20
8. Clarifications (as attachments)
E-mailsMeeting
notes
Sketches
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
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
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
24
BA toolset
25
Confluence - team collaboration tool - www.atlassian.com/software/confluence
27
RTC (issue tracker) www-03.ibm.com/software/products/en/rtc/
28
Mingle (trial issue tracker) www.thoughtworks.com/products/mingle-agile-project-management
31
Balsamiq – www.balsamiq.com
33
MS Visio - www.office.microsoft.com/en-001/visio/
Login checks OK NO
User login
Home Page
YES
Error message
Open task which displays the map
Map loads area and zoom as configured
YES
Map is displayed with area and zoom
NO
35
pen&paper - (free)
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
37
Questions | Answers
Cristian Leon | BA | YonderCodecamp v10.14
38