Difference between revisions of "Job story"
Jump to navigation
Jump to search
(+= “tell me how you perform this part of your job from the beginning to the end”) |
(+= technical stories) |
||
| Line 3: | Line 3: | ||
To find job stories: | To find job stories: | ||
*“tell me how you perform this part of your job from the beginning to the end” | *“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== | ||
Revision as of 06:46, 1 September 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”.