• Like
Agile iiba-meetup 30.11.2011
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Agile iiba-meetup 30.11.2011

  • 1,016 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,016
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 1. WORKING WITHREQUIREMENTS 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 managementSanda Linde 16 years in IT industry Proud to be “early majority” My passions: quality, quality, quality
  • 3. Analysis phaseIn 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 clientSystem 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 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
  • 13. Looking in the futureAnalysis phasedeliverables in wordformat :(Development phasedeliverables in CD ?Project end deliverablesin MediaWiki(maybe) ;)
  • 14. All is oneSpecification, design description, testdocumentation, user guides = wiki
  • 15. That’s all.Thank you for attention!
  • 16. ReferencesAgile Manifesto: http://agilemanifesto.org/Planning poker: http://www.mountaingoatsoftware.com/topics/planning-pokerUser stories: http://www.mountaingoatsoftware.com/topics/user-storiesWiki: http://wiki.org/wiki.cgi?WhatIsWiki