WORKING WITHREQUIREMENTS Agile way Linda Vītuma Sanda Linde www.ebit.lv
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 managementSanda Linde 16 years in IT industry Proud to be “early majority” My passions: quality, quality, quality
Analysis phaseIn parallel with development
Requirement estimates Planning poker
Requirements vs. User stories ProjectWiki
Detailed user stories Speciﬁcation. Testcase. User guide.
Business process for user stories Media Wiki
User story review with clientSystem Requirement Speciﬁcation: MediaWiki vs Word
Development phase In parallel with analysis
Priorities from customer Requirement interdependence analysis
How much time to ﬁnish? Instead of how much has been spent.
Project guidelinesWe respond to changes but respect initial estimatesWe are open to new requirements but we haveliabilities to existent requirementsRequirements are for system but user stories are forpeopleRequirements give us ideas for implementation butuser stories tell us about business problem to besolved
Looking in the futureAnalysis phasedeliverables in wordformat :(Development phasedeliverables in CD ?Project end deliverablesin MediaWiki(maybe) ;)
All is oneSpeciﬁcation, design description, testdocumentation, user guides = wiki