1 / 13

Project Planning: Detailed Task Breakdown

http://flic.kr/p/8nvY6c. Project Planning: Detailed Task Breakdown. Now you have a bunch of user stories with estimates , so what ’ s next?. Iterative Development Process. We are here. Analysis Design Implementation. Requirements Planning. Initial Planning. Testing. Evaluation.

kwaltrip
Download Presentation

Project Planning: Detailed Task Breakdown

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. http://flic.kr/p/8nvY6c Project Planning: Detailed Task Breakdown

  2. Now you have a bunch of user stories with estimates,so what’s next?

  3. Iterative Development Process We are here Analysis Design Implementation Requirements Planning InitialPlanning Testing Evaluation Deployment

  4. Customer Developer Requirements Create USs USs Check USs Corrections/Clarifications Fix USs Add Estimates USs + Estimates Add Priorities USs + Estimates + Priorities Choose USs for Iteration Divide Chosen USs into Tasks Estimate Tasks Assign USs to Workers Get to Work!

  5. Principle: Customer sets priorities • Ensures alignment with customer goals • Helps customer feel in control • Project isn’t going “off the rails” • Estimates help customer maximize cost-benefit

  6. Priority Numbering Scheme • Multiples of 10: • 10 - Highest priority • 20 • 30 • 40 • 50 • … - Lowest priority • Non-multiples of 10 may be used if helpful

  7. So now you have… • Collection of user stories • With estimates • And customer priorities What’s next?

  8. Customer Developer Requirements Create USs USs Check USs Corrections/Clarifications Fix USs Add Estimates USs + Estimates Add Priorities USs + Estimates + Priorities Choose USs for Iteration Divide Chosen USs into Tasks Estimate Tasks Assign USs to Workers Get to Work!

  9. What’s next… • Choose subset of USs to implement this iteration • Based on customer priorities • Based on time constraints • Breakdown subset into tasks • More detailed estimates • May affect iteration plan • Assign people to tasks

  10. From USs to Tasks User Story Estimate

  11. Incremental Development Principle • Each task produces running code • Unit tests count

  12. Task design strategy • Make tasks build upon one another • First task makes subset of US work (e.g., partial form) • Second task makes bit more work (e.g., add persistence) • Etc…

  13. 2-Part Activity • Part 1: Collect customer priorities • Enter into Seedpod • Part 2: • Choose USs for Alpha Iteration • 6 days of work per person • 4 weeks • Create tasks for Alpha USs only • Include estimates • Assign to team members (6 days per person) • Enter into Seedpod • Finally: Submit Alpha Plan in Seedpod

More Related