Hans Samios' Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools


what_is_a_user_story

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
what_is_a_user_story [2020/06/02 14:21]
127.0.0.1 external edit
what_is_a_user_story [2020/06/10 12:47] (current)
hans ↷ Links adapted because of a move operation
Line 154: Line 154:
 When IT organizations have a strategy to "use third party solutions where possible", agile teams often do some work, then hand it to a third party. Once the third party does their work it is returned for validation of the results we see from the third party. If we tried to convert this work to the “user’s voice” it would cause confusion because the business value is only delivered when the final step is delivered. Separate Stories should be written for the work up to the handover and the work after the third party has returned the results – in effect these are big tasks. When IT organizations have a strategy to "use third party solutions where possible", agile teams often do some work, then hand it to a third party. Once the third party does their work it is returned for validation of the results we see from the third party. If we tried to convert this work to the “user’s voice” it would cause confusion because the business value is only delivered when the final step is delivered. Separate Stories should be written for the work up to the handover and the work after the third party has returned the results – in effect these are big tasks.
  
-Note that it is important that we track the impact that using third parties has on our work both to identify problem areas, to improve how we work with third parties, and to better forecast our work when it involves third parties. When you have this kind of “split” work, as you complete your work and hand it over to the third party, track the amount of time that it takes for the third party to respond. You will use this data to understand how long (cycle time) we are waiting for third parties so we can understand where we have issues that need to be addressed. See [[blog:why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]] for more information.+Note that it is important that we track the impact that using third parties has on our work both to identify problem areas, to improve how we work with third parties, and to better forecast our work when it involves third parties. When you have this kind of “split” work, as you complete your work and hand it over to the third party, track the amount of time that it takes for the third party to respond. You will use this data to understand how long (cycle time) we are waiting for third parties so we can understand where we have issues that need to be addressed. See [[why_should_we_work_harder_to_eliminate_the_effect_of_dependencies|Why Should We Work Harder to Eliminate the Effect of Dependencies?]] for more information.
  
 ==== In-flight Work ==== ==== In-flight Work ====
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_is_a_user_story.txt · Last modified: 2020/06/10 12:47 by hans