Structure of a User Story

Updated 1 week ago by Copado Solutions

Overview

The structure of a Copado user story is based on the persona of its users. The fields are logically arranged under separate tabs where each tab is meant for a specific persona. This document describes all the relevant information related to a Copado user story that will enable you to use this feature more efficiently.

Structure of a Copado User Story

Copado User Story shows you the exact stage of development you are in, with the help of a workflow banner.

As seen in the screenshot the compact layout at the top gives informative data about the user story at one glance:

  • Sprint the user story belongs to.
  • Project being worked upon.
  • Name of the release, the user story is contributing to.
  • Record type of the user story (it can be a bug, or investigation, or utility (in case of a US Bundle) ).
  • Progress made in the user story.
  • Overall status of the user story.

The Copado User Story is largely divided into four sections into tabs and each tab is meant for a specific persona. 

Find more details in this table:

Section Name

Persona

Plan

Scrum Master and Product Manager. This tab is also relevant for QA and Developers.

Build

Developer

Test

QA

Deliver

Developer or Release Manager

Related

Applicable for all.

A detailed description of each section is provided for your reference.

Plan

  1. Information

Field Label

Description

User Story Title

Clear and short description of the user story.

User Story Reference

Related User Story.

Record Type

  • User Story
  • Bug
  • Investigation
  • Utility

To know more about each of these record types read Record Types in User Story.

Documentation Complete

This value depends on which documentation your organization wants to consider. It could be developer documentation, or user documentation, or both.

  1. Project Management

Field Label

Description

Project

Project this user story is related to.

Release

Product version or release this user story will contribute to.

Epic

Contains this user story. Epic can have several collections of user stories.

Sprint

Sprint where this user story is planned.

Theme

The group this user story belongs to that collectively achieves a specific goal. 

.

Team

Group of individuals who will work on this user story.

Feature

Feature defines smaller units of functionality related to your User Story.

Owner

Person who created the User Story

Priority

Assigns importance to the User Story. This is an integer value where 1 is the highest level of priority.

Status

Status of the assigned User Story.

  • Draft
  • Backlog
  • Backburner
  • Awaiting Approval
  • Approved
  • Rejected
  • In Progress
  • Ready for Testing
  • Completed
  • Canceled

Order

It can be used together with the Priority field to organize the order in which the User Stories need to be performed.

Progress

Denotes the completion status of the User Story in percentage. Decimal values are not accepted in this field.

Close Date

Expected end date of the User Story.

Progress Status

A graphical representation of the work in progress. The color yellow denotes work is in progress and the color green denotes the work is complete.

  1. User Story Definition

Field Label

Description

As a...

The Persona that this User Story provides value to.

Want to...

Describe what you want to achieve by completing the actions described in this user story.

So that...

What is the benefit of the action?

  1. Acceptance

Field Label

Description

Functional Specifications

Add the functionalities of the feature.

Technical Specifications

Add the technical details related to the implementation.

  1. Estimation

Field Label

Description

Planned Points

The effort your team plans to allocate on implementing, reviewing, testing, and documenting the User Story as soon as it is a part of a sprint. 

Actual Points

The actual effort the team put into the implementation, reviews, testing, and documentation of the User Story.

User Story Tasks

You can break a User Story into multiple tasks that essentially chalk out the road map to the completion of the User Story. It is recommended that each must be an action item that takes no more than eight hours. Tasks are usually defined by the people doing the work (developers, QA, etc). They contain a highly detailed explanation of the job to be completed and are not meant for the end-user. See User Story Tasks for more information.

Build

  1. Information

Field Label

Description

Credential

Credential is used to add or commit metadata, or to promote and deploy the user story to the next environment 

Developer

The person who is currently working on the user story.

Platform

You must select one platform such as Salesforce, Heroku, and so on.

Environment

Current environment of the user story. This value is dependent on the value selected for the credential.

Base Branch

  • Git branch from which the feature branch is created. 
  • This value is auto-filled when you perform a commit in the user story.
  • It is the main branch in the Deployment Flow.
  • Base branch of the Release linked to the user story.

View in Git

Auto-generated link to the user story branch in Git. This is dependent on the base branch URL of the Git Repository record.

Platform

This is auto-populated with the pipeline platform.

Latest Commit Date

The date when the changes were committed last.

  1. User Story Selection
    Metadata types of the components listed in the user story selection. This is automatically updated by Copado.
    Metadata Types in Selection: Auto-populated
  2. User Story Selected Metadata
    Here you must add a Credential set to the user story.
  3. Deployment Tasks
  4. User Story Commits
  5. User Story Metadata
  6. User Story Data Commits
  7. Relationships
    1. Parent User Stories
    2. Child User Stories

Test

  1. Apex Code Coverage

Field Label

Description

Minimum Apex Code Coverage

You must enter this value as a percentage. If this value is lower than the value set in the User Story’s Environment, the Environment’s value will be automatically applied.

Has Apex Code

The check box is selected by Copado whenever there are Apex Classes in the User Story. It remains unselected if there are no Apex Classes. 

Apex Code Coverage

Coverage of the Apex classes added or committed within the user story.

Note: The test coverage is calculated when you click Manage Apex Test, it is the unit test coverage of the code .

Classes Without Coverage

Number of classes without the minimum required coverage.

Failing Methods

Number of Apex Classe methods that failed during the Apex Test Run Execution.

Triggers Without Coverage

Number of triggers without the minimum required coverage.

  1. Compliance

Field Label

Description

Compliance Status

Current status of the User Story compliance scan.

Last Compliance Scan Date

Latest compliance scan execution date.

  1. Pull Requests
  2. Test Scripts (User Story)
  3. Test Runs
  4. Static Code Analysis Results
  5. Relationships
    1. Parent User Stories
    2. Child User Stories

Deliver

  1. Information

Field Label

Description

Ready to Promote

Select this if you want  the User Story to be marked as ready to be promoted. Thereafter user story will appear as 'Ahead' and available to be selected in the Promotion and Branch Management pages.

Promote and Deploy

Select this to initiate the Promotion and Deployment of this User Story.

Promotion Test Level

Select the test level you want to apply in the deployment of the User Story.

Git Merge Status

The Git Merge status between the feature branch and the target branch. This value is provided by the Git Repository. If there is no value, the Git Repository did not provide one.

  1. Validation Deployment Results

Field Label

Description

Last Validation Promotion

Promotion that contains the latest validation deployment.

Last Validation Deployment

The latest validation deployment for the User Story.

Last Validation Status

Auto-populated field that shows the status of the latest validation promotion of the User Story.

  1. User Story Promotions
  2. Relationships
    1. Parent User Stories
    2. Child User Stories
  1. User Story History
    Here the following fields are tracked:
    1. Acceptance Criteria
    2. Actual Points
    3. Close Date
    4. Documentation Complete
    5. Epic
    6. Feature
    7. Owner
    8. Priority
    9. Status
    10. Team
    11. Theme
    12. Planned Points
    13. Progress
    14. Release
    15. Sprint
  2. Notes & Attachments
  3. Result
  4. Bundled Stories
  5. Relationships
    1. Parent User Stories
    2. Child User Stories


How did we do?