Difference between revisions of "Job story"
Jump to navigation
Jump to search
(Sources += HBR » Eric Almquist » The 30 Things Customers Really Value) |
(→Sources: += Slideshare » Claudio Perrone » Breakthrough Innovation with Jobs To Be Done) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
The purpose of stories is to facilitate the conversation between users and delivery teams, focusing on the user’s goals, needs, and frustrations. | |||
To find job stories: | |||
*“tell me how you perform this part of your job from the beginning to the end” | |||
Some teams resort to “technical stories” to describe the work that aims at improving code quality and reducing technical debt. The fact that we have to create “technical stories” indicates that there is (still) a big gap between business and IT. Having “technical stories” and “user stories” side by side creates an illusion that “technical stories” can be sacrificed or be worked on later as “user stories”. | |||
==Sources== | ==Sources== | ||
{{WebSourceListItem | |||
|url=http://www.slideshare.net/cperrone/breakthrough-innovation-with-jobs-to-be-done | |||
|site=Slideshare | |||
|person=Claudio Perrone | |||
|title=Breakthrough Innovation with Jobs To Be Done | |||
}} | |||
{{WebSourceListItem | {{WebSourceListItem | ||
|url=https://medium.com/the-job-to-be-done/replacing-the-user-story-with-the-job-story-af7cdee10c27#.k2w5fdfrj | |url=https://medium.com/the-job-to-be-done/replacing-the-user-story-with-the-job-story-af7cdee10c27#.k2w5fdfrj | ||
Latest revision as of 13:52, 26 October 2016
The purpose of stories is to facilitate the conversation between users and delivery teams, focusing on the user’s goals, needs, and frustrations.
To find job stories:
- “tell me how you perform this part of your job from the beginning to the end”
Some teams resort to “technical stories” to describe the work that aims at improving code quality and reducing technical debt. The fact that we have to create “technical stories” indicates that there is (still) a big gap between business and IT. Having “technical stories” and “user stories” side by side creates an illusion that “technical stories” can be sacrificed or be worked on later as “user stories”.