Agile User Story
(Redirected from Sprint ticket)
Jump to navigation
Jump to search
An Agile User Story is a user requirement in user language that describes what the user needs to perform their business function.
- AKA: Sprint Ticket.
- Context:
- It can (typically) be a member of a Product Backlog (e.g. a sprint backlog).
- It can (ideally) be small enough to be completed within the time frame of a sprint, but also have enough value to the customer or end-user to justify its inclusion in the sprint.
- It can (often) describe the Business Value.
- It can (often) be associated with a Story Test (business facing test).
- It can (often) have an Acceptance Criteria.
- It can range from being a Single-Sprint Story to being a Multi-Sprint Story (like a Epic story).
- …
- Example(s):
As a user, I want to upload photos so that I can share photos with others.As an administrator, I want to approve photos before they are posted so that I can make sure they are appropriate.- …
- Counter-Example(s):
- a Spike Story.
- a Use Case.
- an Integration Test.
- See: Product Management, IT System User, User (System), Agile Software Development, Requirements Management.
References
2023
- chat
- Q: What is a Sprint ticket?
- A: A sprint ticket, also known as a user story, is a unit of work that is planned and executed during an agile sprint. It is a description of a specific feature or functionality that is to be delivered as part of the sprint. A sprint ticket should be small enough to be completed within the time frame of a sprint, but also have enough value to the customer or end-user to justify its inclusion in the sprint. Sprint tickets are usually written in a specific format, such as "As a [user], I want [feature], so that [benefit].”
Sprint tickets are usually created during sprint planning, where the development team and stakeholders review and prioritize the product backlog, which is a list of all the features and functionality that are desired for the product. Sprint tickets are then selected from the product backlog and added to the sprint backlog, which is a list of all the work that will be done during the sprint.
In Agile methodology, sprint tickets are usually split into small manageable chunks that are easy to understand, estimate and deliver, these chunks are called tasks. These tasks are then assigned to team members, who take responsibility for completing them within the sprint. The development team works on these sprint tickets during the sprint, and at the end of the sprint, the completed work is reviewed and demonstrated to stakeholders.
2023
- chat
- Q: What might some criteria be that a ticket must meet prior to being accepted into the upcoming sprint or to be started?
- A: Some criteria that a ticket must meet prior to being accepted into an upcoming sprint or to be started include:
- The ticket is clearly defined and understandable, with well-written user stories and acceptance criteria.
- The ticket is properly prioritized and aligned with the overall goals and objectives of the project.
- The ticket has been properly tested and any identified bugs or defects have been addressed.
- The necessary resources (e.g. team members, equipment, budget) are available to work on the ticket.
- The ticket does not introduce new risks or dependencies that would negatively impact the sprint or project as a whole.
- The ticket is in a state of readiness, and any necessary work such as design or architecture has been done.
- The ticket is estimated to be of a size that can be completed within the time frame of the sprint.
- The ticket is not blocked by any other task, and all prerequisites are completed.
2017
- https://www.smartsheet.com/ultimate-agile-dictionary
- QUOTE:
- Definition: A story, or user story, is a brief, non-technical statement of a software system requirement written from the end-user’s point of view. A story is written according to the following structure: as a <type of user>, I want to <perform some task> so I can <achieve some goal.>
- How it’s Used: The product owner prioritizes the stories to be included in each sprint during the sprint planning meeting. The team assigns story points to each story to estimate workload effort, and then breaks the stories down into tasks to be completed during the sprint. When the iteration or sprint is completed, the team should have produced a functional product or deliverable that corresponds to the initial requirement specified in the story.
- QUOTE:
2015
- (Wikipedia, 2015) ⇒ http://en.wikipedia.org/wiki/user_story Retrieved:2015-12-10.
- In software development and product management, a user story is a description consisting of one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard.
A user story encapsulates the action of one function making it possible for software developers to create a vertical slice of their work.
- In software development and product management, a user story is a description consisting of one or more sentences in the everyday or business language of the end user or user of a system that captures what a user does or needs to do as part of his or her job function. User stories are used with agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard.
2013
- http://searchsoftwarequality.techtarget.com/definition/user-story
- QUOTE: A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.