... | ... | @@ -89,6 +89,8 @@ |
|
|
* Gitlab is our main tool for development and project management.
|
|
|
* Work is organised in issues with labels.
|
|
|
* Anyone on the project team can create an issue.
|
|
|
<br>
|
|
|
|
|
|
* Stories are broken down into issues. **When creating issues;**
|
|
|
* Each issue should be documented separately.
|
|
|
* Describe the purpose of the issue clearly.
|
... | ... | @@ -99,6 +101,8 @@ |
|
|
* Mention if the issue is time sensitive or blocking your work in some way.
|
|
|
* If you're logging a bug, include screenshots and the steps to reproduce the error.
|
|
|
* Issues are development tasks to be completed with a working day (max 2 days) that contribute to the completion of a user story.
|
|
|
<br>
|
|
|
|
|
|
* A **stories definition of 'ready';**
|
|
|
1. Business description present in a format of "As a < type of user >, I want < some goal > so that < some reason >".
|
|
|
1. Acceptance criteria are written.
|
... | ... | @@ -109,6 +113,8 @@ |
|
|
1. Story was refined
|
|
|
1. Dependencies eliminated
|
|
|
1. Priority set
|
|
|
<br>
|
|
|
|
|
|
* A **stories definition of 'done';**
|
|
|
1. All workflow steps are done.
|
|
|
1. Unit tests executed.
|
... | ... | |