Take the tour ×  Let's say I have three user stories A, B and C.
All three of these user stories require a technical task to be
completed before any of them can be done (for example,
developing some new framework), but once this framework is
complete, the 3 stories then become trivial to implement.  The
way I would approach this is to create an additional "story" for
that technical task, even though it doesn't follow the typical
"As a user, I want to..." format. It seems incorrect to add it
on to either A, B or C since that would significantly increase
the time of one of them, making the points incorrect with
respect to their sizing to each other. I also don't to split the
points between the 3 stories since none of them can be completed
without this task.  Thoughts on how to handle this case?
share|improve this question add comment  3 Answers  up vote 4
down vote accepted  One approach is to simply choose one of the
several stories with the shared requirement and estimate it as
including that effort, then es