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

Agile iiba-meetup 30.11.2011

on

  • 1,089 views

 

Statistics

Views

Total Views
1,089
Views on SlideShare
1,088
Embed Views
1

Actions

Likes
0
Downloads
1
Comments
0

1 Embed 1

http://a0.twimg.com 1

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Agile iiba-meetup 30.11.2011 Agile iiba-meetup 30.11.2011 Presentation Transcript

  • 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 Specification. Testcase. User guide.
  • Business process for user stories Media Wiki
  • User story review with clientSystem Requirement Specification: MediaWiki vs Word
  • Development phase In parallel with analysis
  • Priorities from customer Requirement interdependence analysis
  • How much time to finish? 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 oneSpecification, design description, testdocumentation, user guides = wiki
  • That’s all.Thank you for attention!
  • 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