Who should be writing use stories?

Home Forums Software QA Testing Software Engineering Who should be writing use stories?

Viewing 1 reply thread
  • Author
    • H2k Infosys

      A good user story

      • Includes description
      • Has acceptance criteria defined
      • Can be delivered within a single sprint
      • Has all UI deliverables available
      • Has all dependencies identified
      • Has performance criteria defined
      • Has tracking criteria defined.


    • sumanmelut

      Valid point


Viewing 1 reply thread
  • You must be logged in to reply to this topic.