Feeding The Scrum Engine

1,622 views

Published on

How to decompose the work so that a sustainable flow of work can be feed into the team. Scrum teams flourish when there is a flow of work that does not choke them with too much volume. Agile analysis is the key to achieving that flow.

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

  • Be the first to like this

No Downloads
Views
Total views
1,622
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
42
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Feeding The Scrum Engine

    1. 1. Transitioning to Agile: Feeding the Scrum Engine Derek Wade [email_address] and Douglas Shimp [email_address]
    2. 2. Two Views of Work* <ul><li>Goals – Management View </li></ul><ul><ul><li>“ What do I want built?” </li></ul></ul><ul><ul><li>High-level </li></ul></ul><ul><ul><li>Difficult to structure appropriately </li></ul></ul><ul><ul><ul><li>too high-level  not useful to team </li></ul></ul></ul><ul><ul><ul><li>too detailed  directive vs. adaptive </li></ul></ul></ul><ul><li>Tasks – Development View </li></ul><ul><ul><li>“ What do I have to do today?” </li></ul></ul><ul><ul><li>Work queue </li></ul></ul><ul><ul><li>Forest vs. trees problems </li></ul></ul><ul><li>Needed </li></ul><ul><ul><li>Begin with the end in mind </li></ul></ul><ul><ul><li>Encourage agility </li></ul></ul><ul><ul><li>Bridge the gap </li></ul></ul>* from Managing the Work in an Agile Project, Dr. Daniel Rawsthorne, PhD.
    3. 3. Managing the Work: WBS View* Business Value / Product Centric The Product Backlog Product Team Org Function Structure Feature 1 Function 2 Feature 3 … Conversions Rewrites Refactorings … Training Dev Environment Tools … Sales Support Marketing Support User Docs …
    4. 4. Managing the Work: “To Do” View* <ul><li>Now </li></ul><ul><ul><li>a.k.a. “Sprint Backlog” </li></ul></ul><ul><ul><li>Stories </li></ul></ul><ul><ul><ul><li>Deliverable chunks of value </li></ul></ul></ul><ul><ul><ul><li>“ Validate-able” </li></ul></ul></ul><ul><ul><ul><li>Estimated / “Right-sized” </li></ul></ul></ul><ul><ul><li>Tasks </li></ul></ul><ul><ul><ul><li>Complete them to deliver the stories </li></ul></ul></ul><ul><li>Next </li></ul><ul><ul><li>Uncommitted, Next Sprint Backlog, or next Release </li></ul></ul><ul><ul><li>Stories </li></ul></ul><ul><li>Someday </li></ul><ul><ul><li>Stories? </li></ul></ul><ul><ul><li>“ Buckets” (story generators) </li></ul></ul><ul><ul><li>Possibly just “bright ideas” (need further investigation) </li></ul></ul>Decreasing Precision Task Centric
    5. 5. Stories – Bridge Between WBS and To Do <ul><li>From XP </li></ul><ul><ul><li>use-cases, scenarios, bits of features/function </li></ul></ul><ul><ul><li>not just for users anymore </li></ul></ul><ul><li>Discrete piece of ROI </li></ul><ul><ul><li>end-to-end, incremental value </li></ul></ul><ul><li>Format </li></ul><ul><ul><li>Required: name, description, validation criteria </li></ul></ul><ul><ul><li>Also: ID#, “story boss,” priority, size estimate </li></ul></ul><ul><li>Good Stories: </li></ul><ul><ul><li>“ bite”-able ( ~10 in a 30-day sprint ) </li></ul></ul><ul><ul><li>validate-able (no partial credit) </li></ul></ul><ul><ul><li>discrete (avoid dependencies) </li></ul></ul>
    6. 6. Perhaps an example would help? Stories The Product Backlog Product Team Org Function Structure Feature 1 Function 2 Feature 3 … Conversions Rewrites Refactorings … Training Dev Environment Tools … Sales Support Marketing Support User Docs … Now Next Someday
    7. 7. Example – Structure the WBS The Product Backlog Product Team Org Function Structure Login Withdraw Cash Deposit Checks … Conversions Rewrites Refactorings … Training Dev Environment Tools … Sales Support Marketing Support User Docs …
    8. 8. Example – Feed “To Do” View with WBS <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Decreasing Precision Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs
    9. 9. Example – Analyze / Add Stories <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Decreasing Precision Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs
    10. 10. Example – Analyze Stories (detail) Login Unfold to software elements Develop unit / integration tests Code up login UI Update DB with UID / PW Develop login module Integrate Analysis for Login Use-Case Login “Happy Path” “ 3 strikes” scenario Name: Login “Happy Path” Description: Primary success scenario for Login. Validation Criteria: -- login using UID and PW which are stored in DB is given access -- login w/ UID or PW which is not in the DB is not given access -- works for DEV and INT Unfold story into tasks “ when it’s time”
    11. 11. Example – Analyze / Add Stories (cont.) <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs Analysis for Login Use-Case Login “Happy Path” “ 3 strikes” scenario xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx
    12. 12. Example – Prioritize / Unfold Stories <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs Analysis for Login Use-Case Login “Happy Path” “ 3 strikes” scenario Unfold to sware elements Develop unit / Integration tests Code up login UI Update DB with UID / PW Develop login module Integrate xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx
    13. 13. Example – Do The Work <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs Analysis for Login Use-Case Login “Happy Path” “ 3 strikes” scenario Unfold to sware elements Develop unit / Integration tests Code up login UI Update DB with UID / PW Develop login module Integrate xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxxxx xx xxx x xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx Notice how work outside sprint just appears
    14. 14. Example – Clean Up for Next Sprint <ul><li>Now </li></ul><ul><li>Next </li></ul><ul><li>Someday </li></ul>Login Withdraw Cash Deposit Checks Rewrites Conversions … Training Dev Env Sales Support User Docs “ 3 strikes” scenario xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxxxx xx xxx x xxxxx xx xxx x xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx xxx xx xxxx xxxx xxxxx
    15. 15. Keys to Success <ul><li>Be validation-centric </li></ul><ul><ul><li>done / work complete </li></ul></ul><ul><ul><li>verified / tested </li></ul></ul><ul><ul><li>validated / demoable or accepted </li></ul></ul><ul><ul><li>no partial credit </li></ul></ul><ul><li>“ Right-size” stories </li></ul><ul><ul><li>don’t be afraid of small bites </li></ul></ul><ul><ul><li>stories are not tasks </li></ul></ul><ul><ul><li>let the product lead </li></ul></ul><ul><li>Adapt </li></ul><ul><ul><li>unfold complexity </li></ul></ul><ul><ul><li>deal with difficulty </li></ul></ul>
    16. 16. Reminder! <ul><li>Staying Agile is an Agile process </li></ul><ul><li>Agile is about people </li></ul><ul><ul><li>Play to win vs. playing not to lose </li></ul></ul><ul><li>You don’t “do an agile process…” </li></ul><ul><li>…you are the agile process! </li></ul>
    17. 17. Thank You!

    ×