CPS User stories guideline

How to Write a User Story

A Story/user story is a software system requirement expressed in a few short sentences, using non-technical language. A User Story should express needs from the user's perspective. This can be conveyed in a syntax way like the illustration below

Jira Stories are groomed by the team in weekly meetings or on demand as required

Suggested User Story Template

1. The label 'Groomed' will be added when the team agrees there is enough information in the ticket, the scope is clear and acceptance criteria are defined

2. Grooming is not compulsory for Jira (sub)tasks (not affecting source code). All subtasks should be linked to user stories 

3. Select the appropriate release/Fix Version the feature is intended for.

4. Add user stories to the relevant epic or Technical Debt & New Ideas

Technical Debt & New Ideas

To ensure technical debt and improvement items are documented, prioritized, and managed with the same level of attention as standard user stories.

1. All technical debt and New Ideas should be added to the epic [CPS-245] Improvement Ideas & Technical Debt - Jira upon creation

2. Agree on priority with PTL & PO

3. Grooming of the Jira

4. Description and Acceptance criteria shall be set and discussed during the refinement

5. Select the appropriate release/Fix Version the feature is intended for.

6. The label 'Groomed' will be added when the team agrees there is enough information in the ticket, the scope is clear and acceptance criteria are defined

PS: Refer to CPS guideline to definition of done before closing any Jira

CPS Definition of Done (and FSA) - ONAP Wiki - Confluence

JIRA Status Updates