User Tools

Site Tools


how_can_we_improve_collaboration_on_user_stories

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
how_can_we_improve_collaboration_on_user_stories [2021/04/28 11:35]
hans Changed terminology to reflect more modern language
how_can_we_improve_collaboration_on_user_stories [2021/04/28 11:37] (current)
hans Reflect modern usage
Line 3: Line 3:
 > "Everything is vague to a degree you do not realise till you have tried to make it precise" -- Bertrand Russell > "Everything is vague to a degree you do not realise till you have tried to make it precise" -- Bertrand Russell
  
-When it comes to understanding and documenting requirements there always seems to be a discussion and room for improvement. In general we capture a user story in an automated tool with a summary / title and a description that has both the user story (“as a”, “I want”, “so that”) and a section describing the "Conditions of Satisfaction" (aka "Acceptance Criteria"). People wonder “how much is too much detail?” Others wonder whether they really understand the requirement in enough detail to do something useful. Still others think that we should write a complete specification.+When it comes to understanding and documenting requirements there always seems to be a discussion and room for improvement. In general we capture a user story in an automated tool with a summary / title and a description that has both the user story (“as a”, “I want”, “so that”) and a section describing the "Acceptance Criteria" (aka "Conditions of Satisfaction"). People wonder “how much is too much detail?” Others wonder whether they really understand the requirement in enough detail to do something useful. Still others think that we should write a complete specification.
  
 One team I worked with recently ran an experiment using a slightly more formalized approach to capturing Acceptance Criteria (or Conditions of Satisfaction) which helped us understand the requirement, but also did not specify how solution was to be derived. At the time we were trying to solve a problem with the (acceptance) testing of the workflows but found that the solution we worked also helped us improve the discussion and collaboration around the requirements. One team I worked with recently ran an experiment using a slightly more formalized approach to capturing Acceptance Criteria (or Conditions of Satisfaction) which helped us understand the requirement, but also did not specify how solution was to be derived. At the time we were trying to solve a problem with the (acceptance) testing of the workflows but found that the solution we worked also helped us improve the discussion and collaboration around the requirements.
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_can_we_improve_collaboration_on_user_stories.txt · Last modified: 2021/04/28 11:37 by hans