Your SlideShare is downloading. ×
0
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Requirements and estimating
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Requirements and estimating

1,229

Published on

Estimating and requirements gathering are an important part of all our jobs. Your boss or your client doesn't care about FW/1, CF-ORM or Code Generation, but improving your requirements gathering and …

Estimating and requirements gathering are an important part of all our jobs. Your boss or your client doesn't care about FW/1, CF-ORM or Code Generation, but improving your requirements gathering and estimating skills can make a big difference in how they value your skills.

Learn best practices for more accurately specifying and estimating projects using a range of proven patterns developed from specifying and estimating over 400 web applications over more than ten years.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,229
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
24
Comments
0
Likes
1
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

Transcript

  • 1. Requirements & Estimating Scotch on the RocksEdinburgh, March 3-4 2011 Peter Bell Railo
  • 2. Agenda• Requirements • Intent Driven Design • User stories 201• Estimation • How much? • Estimating scope • Managing commitments • Estimating duration • Fixed duration• Managing risk • Fixed price • Four types of features • Breaking the iron triangle • Dealing with dark matter
  • 3. Division of Labor • My Job: • Present ideas • Your Job: • Discriminate, select, adapt, experiment
  • 4. About you• Consultant/in-house/product development?• Team size?• Number of projects/year?• Agile?• User stories?• Estimates required?• Fixed bid required?
  • 5. Requirements
  • 6. Before user stories . . . What should we build?
  • 7. Intent Driven Design • Business intent • Audiences • Objectives • User stories (tasks)
  • 8. User stories (1) • INVEST • Independent • Negotiable • Valuable • Estimable • Small • Testable
  • 9. User stories (2) • Tracer bullets, not tasks • Splitting stories by ... • Data • Validation • Paths • Edge cases • Isolate cross cutting concerns • Make it work, then pretty/fast
  • 10. Estimation
  • 11. Why estimate?
  • 12. Why estimate?• Good reasons to estimate: • Go/no go based on cost • Market window • ROI comparison
  • 13. Why estimate?• Good reasons to estimate: • Go/no go based on cost • Market window • ROI comparison• Bad reasons to estimate • Because . . .
  • 14. Why estimate?• Good reasons to estimate: • Go/no go based on cost • Market window • ROI comparison• Bad reasons to estimate • Because . . .• Ask whether: • Time, price or both? • Will estimate matter? • Accuracy required?
  • 15. Estimating scope• Ideal days (load factor)• Story points • 1,2,3,5,8 • 0? • 10,20,30,51?• T-shirt sizes• Story count
  • 16. Estimating scope• Planning poker• Keys: • Delphi technique • Independent estimates • 1-3 hours, 1-3 sessions • 2-6 people
  • 17. Estimating scope• Magic/Affinity Estimating • Large number of stories • Experienced team
  • 18. Estimating time• Estimating velocity • Historic rate • Run iterations • Make forecasts• Burn down charts
  • 19. Managing risk
  • 20. Four types of feature • Rocket science • Lab experiment • New to you • with a twist
  • 21. Dealing with dark matter • What you don’t know does hurt you ... • But obviously . . . • The dreaded API and technical risk • Well, that’s almost right . . . • Now that I see it . . . • Mitigate: • Set expectations • Technical spikes • Track and refine
  • 22. Making commitments
  • 23. Fixed duration • Optional features • Team size • Real options • Schedule buffer
  • 24. Fixed price • Optional features • Price buffer • Scheduling flexibility?
  • 25. Breaking the iron triangle
  • 26. Breaking the iron triangle Requirements are never fixed!
  • 27. Q&A Twitter: peterbell• Requirements Email: peter@pbell.com • Intent Driven Design • User stories 201• Estimation • How much? • Estimating scope • Managing commitments • Estimating duration • Fixed duration• Managing risk • Fixed price • Four types of features • Breaking the iron triangle • Dealing with dark matter

×