1 / 21

Story-driven development

Story-driven development. Useful requirements, engaged customers, and data-driven projects. Carl Erickson, PhD. Ron Jeffries, XProgramming.com. Not-so-simple analogy. Development tasks Simple design Unit tests. Customer stories Simple features Acceptance tests. 1. Customer dependency.

rania
Download Presentation

Story-driven development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Story-driven development Useful requirements, engaged customers, and data-driven projects Carl Erickson, PhD

  2. Ron Jeffries, XProgramming.com

  3. Not-so-simple analogy Development tasks Simple design Unit tests Customer stories Simple features Acceptance tests 1. Customer dependency 2. Testing difficulty

  4. Major Benefit #1 Requirements When you need them In small chunks Actionable, unambiguous, useful With an opportunity to learn-as-you-go

  5. Major Benefit #2 Predictability Stories can be estimated (small chunks) Project velocity can be measured Rhythm is established

  6. Major Benefit #3 Feature management Keeping it simple Staying focused Putting a cost on features Letting the customer steer

  7. Tool Support for SDD • Coordination/Collaboration • Common documents • Messages (emailed, archived) • To-do lists • Iteration Planning and Tracking • Estimates, status, budget, velocity • Predictions • Time Tracking • Estimates, status, budget • Billing

  8. Dynamometer Project • 9 months • 5 pairs of developers (3 @ AO, 2 @ BP) • C#/.NET GUI client - C++/QNX server

  9. Time Tracking+Project Status

  10. But wait, there’s more! Automating acceptance tests gets you… Executable requirements (even more unambiguous) Inexpensive for developers to run Regression testing ability Release process confidence A few more bugs

  11. References Basecamp www.basecamphq.com ExplainPMT www.explainpmt.com Atomic Object atomicobject.com XPwm xpwestmichigan.org

More Related