Workflows

Create Sprint Backlog Entry (SBE)

SBEs are high level issues based on the results of the "Planning and Estimation Meeting" and "First Team Meeting" (Scrum Development Process). SBEs are decomposed into smaller issues called Work Entries (WEs). This does not exclude an SBE to be a WE if the SBE is small enough. There should be enough initial WEs to get started.

1. Create SBEs at the beginning of the sprint.
2. Choose the affected version (Affects Version/s)
3. Choose the version which will be fixed (Fix Version/s)
4. Insert time estimation (estimation should be done during the "Planning and Estimation Meeting")
5. Activate Checkbox "Is Sprint Backlog Entry"
6. SBEs which are too big to be directly addressed have to be  divided into smaller work entries (=> Create Work Entry to a Sprint Backlog Entry)
7. Otherwise SBE is a Work Entry (WE)

There is a special SBE for each project in jira called "Wild Card, Sprint #". This special SBE is for general or unexpected issues, which sould be solved during the sprint. The amount of time has to be defined in the "Planning and Estimation Meeting".

Create Work Entry to a Sprint Backlog Entry (WE)

 A WE should be small. If it's possible to split a WE, where each resulted WE is greater than 1h, then do the split.

1. Create an issue (WE). 
2. Choose the affected version (Affects Version/s) and fix version (fix Version/s)
3. Estimate time for this issue incl. time for reviewing
4. Each issue belongs to a SBE. That means the Reporter of an issue has to link the created issue to a SBE (SBE depends on this issue)
5. DON'T mark it as SBE
6. DON'T insert the name of the reviewer

• Affects Version(s) - this is the version(s) in which the issue is manifesting. For instance, a software bug might affect versions 1.1 and 1.2.

• Fix Version(s) - this is the version(s) in which the issue was (or will be) fixed. For instance, the bug affecting versions 1.1 and 1.2 might be fixed in version 2.0. Note that issues which do not have a Fix Version are classified as 'Unscheduled'

How the team works with jira

Assignee

1. Choose an issue (discussed in the daily standup) and assign it to yourself (consider Committing, versioning and code reviewing)
2. Work on this issue (Start Progress)
3. Log work done on this issue.
4. If finished, change state of issue to resolved (consider Committing, versioning and code reviewing)
5. [optional]: Make suggestions who should review the issue

Reviewer

1. Enter your name in the form field "Reviewer" (Start Reviewing)
2. Log work done on this issue.
3. Reopen or close the issue (consider Committing, versioning and code reviewing)
4. If you reopen the issue you have to remove your name from form field "Reviewer" and add a comment what should be done. (=> Assignee: Work on this issue)

Comments:

• If you can't resolve the issue change state to open (Stop Progress)
• After a Sprint all current SBEs will be marked as resolved (check resolution: if SBE is not fixed choose incomplete) and than marked as closed (if necessary SBE will be cloned for the next sprint)
• WEs, which are not SBEs, don't have to be closed after a Sprint

State Transitions

• Open -> Start Progress -> In Progress (Assignee)
• Open -> Resolve -> Resolved (Assignee)
• In Progress -> Stop Progress -> Open (Assignee)
• In Progress -> Resolve -> Resolved (Assignee)
• Resolved -> Reopen -> Open (Assignee)
• Resolved -> Start Review -> Under Review (Reviewer)
• Under Review -> Close -> Closed (Reviewer)
• Under Review -> Reopen -> Open (Reviewer)
• Closed -> Reopen -> Open (not assigned)