Sign Up

Captcha Click on image to update the captcha.

Have an account? Sign In Now

Sign In

Captcha Click on image to update the captcha.

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Captcha Click on image to update the captcha.

Have an account? Sign In Now

Sorry, you do not have permission to ask a question, You must login to ask a question.

Captcha Click on image to update the captcha.

Forgot Password?

Need An Account, Sign Up Here

Sorry, you do not have permission to add post.

Captcha Click on image to update the captcha.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

Ask Agile

Ask Agile Logo Ask Agile Logo

Ask Agile Navigation

  • Home
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Community Help
    • Kanban
    • Scrum
    • Scaled Scrum
    • Liberating Structures
    • Culture
    • Small Talk
    • Team Dynamics
    • Job Opportunities
    • Self-Promotions, Selling Services, Tool Promotions
  • Home
  • Blog
  • Contact Us

Samatha

0 Visits
0 Followers
0 Questions
  • About
  • Questions
  • Polls
  • Answers
  • Best Answers
  • Groups
  • Questions
  • Polls
  • Answers
  • Best Answers
  • Groups
  1. Asked: December 21, 2022In: Scrum

    What do you include in a User Story?

    Samatha
    Samatha
    Added an answer on December 21, 2022 at 11:04 am

    Yes this is the format even we follow for a user story. Customer requirements are written as User story in simple English so that it's understandable in fact as how customer perceives it.for example customer is looking for software to manage leave management for their employees.user stories for thisRead more

    Yes this is the format even we follow for a user story. Customer requirements are written as User story in simple English so that it’s understandable in fact as how customer perceives it.for example customer is looking for software to manage leave management for their employees.user stories for this requirement could be
    1.As an employee i would like to apply leaves so that manager can approve
    2.As a manager I would like to approve leaves so that employee can avail leaves.
    Building entire leave application requirement we call it as epic and epic is set of all user stories -epic broken down to small size,buildable requirements.
    Inside each user story we must write Acceptances criteria, so that becomes a checkpoint for user story completion.acceptance criteria is referred by entire team to see if they have built as per expectation.

    See less
    • 1
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp

Sidebar

Ask A Question

Stats

  • Questions 145
  • Answers 77
  • Best Answers 3
  • Users 0

Top Members

  • Popular
  • Answers
  • Danny Vallee

    Is Kanban Agile?

    • 5 Answers
  • Anonymous

    What is one thing you wish you could know when ...

    • 2 Answers
  • Anonymous

    Testing generate a lot of bugs and the sprint never ...

    • 2 Answers
  • GuyM
    GuyM added an answer "The product backlog items are too big for one sprint"… March 5, 2023 at 12:45 am
  • GuyM
    GuyM added an answer I'd suggest two things. - the surface issue is seldom… March 5, 2023 at 12:36 am
  • Danny Vallee
    Danny Vallee added an answer Thanks GuyM! January 31, 2023 at 9:38 am

Trending Tags

agile (6) book (4) metrics (4) po (5) scrum (10) scrum master (14) sprint (4) story (5) story points (4) team (9)

Explore

  • Community Help
    • Kanban
    • Scrum
    • Scaled Scrum
    • Liberating Structures
    • Culture
    • Small Talk
    • Team Dynamics
    • Job Opportunities
    • Self-Promotions, Selling Services, Tool Promotions

Footer

About Us

  • Blog
  • Contact Us

Help

  • Knowledge Base - FAQs

Legal Stuff

  • Privacy Policy
  • Terms of Service

© 2023 GaliléSolutions.com. All Rights Reserved
Crafted with Love by Agile Lovers at GaliléSolutions.com.