Flow for scope documentation

Content

Main folders

• General Info: Contains primary information about the documentation process and other activities on the project.

• Templates: Includes templates for Epics and User Stories.

• CRM: Houses Epics and User Stories related to the CRM system.

• TALENT: Contains Epics and User Stories specific to Rocken Talent.

• Rocken Jobs: Focuses on Epics and User Stories for Rocken Jobs.

• Corporate Website: Covers Epics and User Stories for the Corporate Website.

Guidelines

1) Each User Story must include:

• A general description

• The User Story itself

• Acceptance criteria written in Gherkin format (Given, When, Then).

2) Multiple User Stories addressing a specific functionality should be grouped into an Epic.

An Epic includes:

• A general description

• Links to related Jira tickets

• Associated design documents.

3) All Epics and User Stories must be linked to a Jira ticket in the “Add Description” sprint.

4) Upon completing the description, tickets should be moved to the “Product Owner Review” sprint for review.

5) Once approved, the ticket progresses to the “Ready to Estimate” sprint, where the team discusses it during the Refinement meeting.

6) After estimation, the ticket moves to the “Ready for Sprint” sprint.

• The Scrum Master and Product Owner prepare tickets for upcoming sprints.

• Final sprint commitments are made by the team during the Sprint Planning meeting.

7) Minor changes can be updated within the existing User Stories.

8) Major changes require creating new Epics or User Stories with links to the relevant existing items.