Versions Compared

Old Version 4

changes.mady.by.user Taisiya Trunova

Saved on

compared with

New Version Current

changes.mady.by.user Ivan Kryzhanovskyi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

User Story/Bug/Task can be added to Sprint only if it conforms to the following criteria of Definition of Ready:

1. Requirements are clearly expressed by PO or any other reporter

Note:

  • Front-end User Stories to be written (usually by PO) according to the format outlined at "Development Backlogs → User stories" section.
  • Back-end Stories to be written (PO or Dev team) according to the template as outlined below (if applicable) and should contain as many details as possible.
  • Bugs to be written according to the template.


Panel
borderColor#BFD1CD
bgColor#F0FEFB
titleFront-end User Story Template

Purpose: Story context for casual viewers.  What is this story supposed to cover?  If it's just an initial iteration of a larger feature, make that clear here.

User story statement(s): The user story statement is optional and you'll notice that many of our stories don't contain them.  This is because, between the purpose and the scenarios, there is usually more than enough information to go on.  That said, including a user story statement is best practice and if you have them please include them.  They will take the format: As a < type of user >, I want < some goal > so that < some reason >

Scenarios: On FOLIO, acceptance criteria are written as scenarios using the "gherkin syntax" (given, when, then)

Attachments/links:

  • Whenever possible, a UX mockup should be attached or linked to the user story.  If there are elements of the mockup that are out of scope for the story (for example, because the technical prerequisites are not in place), then they should be noted as "out of scope for this story" 
  • If required the following links should be added:
    1. design documentation
    2. back-end story with API description
    3. samples of JSON schema


Preformatted template for pasting into JIRA

*Purpose:*

*User story statement(s):*

As a < type of user >,

I want < some goal >

so that < some reason >

*Scenarios:*

# Scenario:

* Given <preconditions>

* When <actions>

* Then <results>



Panel
borderColor#BFD1CD
bgColor#F0FEFB
titleBack-end Story Template

Purpose/Overview: High-level description of problem.

Requirements/Scope: Requirements to be turned into working product.

Approach: Approach to be followed while development (if already discussed and known).

Acceptance Criteria: Acceptance criteria to assess whether the development of story was done in a proper way and requirements are met.

Attachments/links: Any available links to useful documentation, schemas, etc.

Preformatted template for pasting into JIRA

*Purpose/Overview:*

*Requirements/Scope:* 
# Requirement
# Requirement
*Approach:*   
*Acceptance criteria:* 
* AC
* AC




Panel
borderColor#BFD1CD
bgColor#F0FEFB
titleBug Template

Overview: Optional high-level description of problem, operational system, browser version, environment, time zone of tenant and local time zone (if applicable)

Steps to Reproduce:

  1. Log into some FOLIO environment as User X
  2. Click this
  3. Select that
  4. etc.

Expected Results: What I expected to see happen

Actual Results: What actually happened

Additional Information: Anything else I noticed or tested that might be relevant to this issue

Preformatted template for pasting into JIRA

*Overview:*

*Steps to Reproduce:*
# Log into some FOLIO environment as User X
# Click this
*Expected Results:*  
*Actual Results:*   
*Additional Information:*  


2. Backlog Item must be linked to a corresponding UXPROD feature.

3. Backlog item is reviewed/

groomed

refined in scope of the corresponding meeting and well understood by dev team.

4. Performance requirements are present (if applicable).

5. Acceptance criteria are clearly defined and confirmed by PO and dev team.

5

6. Estimation in Story Points is added.

6

7. There are no blockers, dependencies, prerequisites preventing the team from completion of the item; any dependencies must be clearly identified via linked issues (has to be done before, has to be done after, has to be done together with, is blocked by).

7

8. Story should conform to INVEST requirements (if possible):

    • Independent

    • Negotiable

    • Valuable

    • Estimatable

    • Small 

    • Testable