1. WORKING WITH
REQUIREMENTS
Agile way
Linda Vītuma
Sanda Linde
www.ebit.lv

2. Who are we?
Linda Vītuma
12 years in IT industry
Pretend to be “early adapter”
My passions: information system “go-live”, problem
solving and change management
Sanda Linde
16 years in IT industry
Proud to be “early majority”
My passions: quality, quality, quality

3. Analysis phase
In parallel with development

4. Requirement estimates
Planning poker

5. Requirements vs. User stories
ProjectWiki

6. Detailed user stories
Specification. Testcase. User guide.

7. Business process for user stories
Media Wiki

8. User story review with client
System Requirement Specification: MediaWiki vs Word

9. Development phase
In parallel with analysis

10. Priorities from customer
Requirement interdependence analysis

11. How much time to finish?
Instead of how much has been spent.

12. Project guidelines
We respond to changes but respect initial estimates
We are open to new requirements but we have
liabilities to existent requirements
Requirements are for system but user stories are for
people
Requirements give us ideas for implementation but
user stories tell us about business problem to be
solved

13. Looking in the future
Analysis phase
deliverables in word
format :(
Development phase
deliverables in CD ?
Project end deliverables
in MediaWiki
(maybe) ;)

14. All is one
Specification, design
description, test
documentation, user
guides = wiki

15. That’s all.
Thank you for attention!

16. References
Agile Manifesto: http://agilemanifesto.org/
Planning poker: http://
www.mountaingoatsoftware.com/topics/planning-poker
User stories: http://www.mountaingoatsoftware.com/
topics/user-stories
Wiki: http://wiki.org/wiki.cgi?WhatIsWiki