Who should be writing use stories?

Home Forums Software Quality Assurance Forum Who should be writing use stories?

Viewing 0 reply threads
  • Author
    Posts
    • H2k Infosys
      Keymaster
      (124.123.175.166)

      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.

      #13886

Viewing 0 reply threads
  • You must be logged in to reply to this topic.