User stories using process

  • User stories by the who, what, value composition
  • Extracted through user stories to meet user stories MVP (E) (the smallest, valuable product (experimental))
  • Back to construct the MVP (E) component activities (Activities), user behavior (Users Tasks), child behavior (sub-tasks) to build a user story map

image-20200401150323728

  • Pair behavior (sub-tasks) to assess priorities, size (affinity estimates, Moscow law)
  • The child behavior may be determined per iteration length may be accomplished by Sprint sprint (sub-tasks) limit, and find a suitable upper limit in the MVP.
  • After completion of the iteration, again to find the right MVP from child behavior (sub-tasks)

Guess you like

Origin www.cnblogs.com/testopsfeng/p/12612742.html
Recommended