Who should be writing use stories?

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

Viewing 0 reply threads
  • Author
    • training@h2kinfosys.com

        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.


    Viewing 0 reply threads
    • You must be logged in to reply to this topic.
    cf7sr token not found