Documentation
SolutionDeveloperComplianceProjects
  • Introduction
  • Gitbook Guidelines
  • PRELIMINARY ANALYSIS
    • Project Initiation
    • Business Goals
    • Information Analysis
    • Solutions Evaluation
    • Risk Assessment
  • APPLICATION DEVELOPMENT
    • Scrum Framework
      • Scrum Values
      • Scrum Roles
      • Scrum Compliance
    • User Requirements
    • Product Backlog
      • User Story
      • Story Mapping
      • Grooming
      • Roadmap
      • Best Practice
    • Sprint Planning
      • Planning Inputs
      • Task Definition
      • Task Sizing
      • Sprint Backlog
      • Best Practice
    • Sprint Execution
    • Sprint Review
    • Sprint Retrospective
    • Process Control
      • Sprint Burn-Up
      • Sprint Burn-Down
      • Sprint Velocity
      • Source Control
    • Risk Assessment
      • Data Privacy & Security
      • Postpone the release
      • Lack of participation or engagement
      • Incomplete backlog items
      • Project Scope Creep
      • Third-Party Dependency
      • Integration Issue
      • Outdated Technology
      • Budget & Time Constraints
      • Inadequate Testing
    • User Acceptance
    • Release and delivery plan
    • Literature
  • SERVICE MANAGEMENT
    • Service Lifecycle
    • Receiving Ticket
    • Ticket Management
      • Maintain Attributes
      • Ticket Assignment
    • Troubleshooting
    • Escalation
    • Monitoring
    • Evaluation
    • Risk Assessment
      • Support and Maintenance
      • Insufficient information
      • Misinterpretation of attributes
      • Insufficient Testing
      • Delayed deadline
      • Lack of continuous improvement
      • Lack of Stakeholder involvement
  • REVIEW & IMPROVEMENT
    • Dashboard Analysis
Powered by GitBook
On this page
  1. APPLICATION DEVELOPMENT
  2. Product Backlog

User Story

PreviousProduct BacklogNextStory Mapping

Last updated 1 year ago

A user story is a component of the Agile software development methodology for gathering the requirements of a need from the viewpoint of the end user. Simply defined, a user story aids in the creation of a simple and brief description of a need from the viewpoint of the user. The Product owner often creates user stories, which belong in the product backlog. These user stories are added to the sprint backlog depending on priority during the Sprint Planning meeting. For creating a user story, the Product owner typically complies with a straightforward process using the Azure DevOps platform:

1. Go to Work Items -> Click on Create a new work item

2. Write a description of the task. Include at least these three categories of description – Navigation, Instruction, and Acceptance Criteria.

  • Navigation: This is showing how we can find the task in the product backlog.

  • Instruction: This is a description for the developer. What should he do to solve the task?

  • Acceptance criteria: Specific requirements that must be met in order to the task to be solved.

3. Save and close the item.