... | ... | @@ -24,7 +24,7 @@ |
|
|
* Ways of working; development coordination and communication.
|
|
|
* Weekly updates; progress against milestones.
|
|
|
|
|
|
### Description (TBC)
|
|
|
### Description
|
|
|
1. Introducing shared/group manuscript reviews.
|
|
|
1. Adding setup configuration in support or alternative workflows, themes and publishing capabilities.
|
|
|
|
... | ... | @@ -103,28 +103,28 @@ |
|
|
* 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 >".
|
|
|
* A **tasks definition of 'ready';**
|
|
|
1. Business description present in a format a feature description or user story "As a < type of user >, I want < some goal > so that < some reason >".
|
|
|
1. Acceptance criteria are written.
|
|
|
1. Expected result (both happy and unhappy path) described.
|
|
|
1. UI mockup prepared (if needed).
|
|
|
1. API definition / endpoints are ready.
|
|
|
1. Documentation attached to the story (e.g. sequence design) is relevant and up to dates
|
|
|
1. Story was refined
|
|
|
1. Task was refined
|
|
|
1. Dependencies eliminated
|
|
|
1. Priority set
|
|
|
<br>
|
|
|
|
|
|
* A **stories definition of 'done';**
|
|
|
* A **task definition of 'done';**
|
|
|
1. All workflow steps are done.
|
|
|
1. Unit tests executed.
|
|
|
1. Automated integration tests written.
|
|
|
1. Test coverage respected.
|
|
|
1. Tooling agreement respected.
|
|
|
1. Story is presentable on prod environment.
|
|
|
1. Feature is presentable on prod environment.
|
|
|
1. Test execution passed (all acceptance criteria are met).
|
|
|
1. Documentation updated.
|
|
|
1. All critical defects related to the story are fixed.
|
|
|
1. All critical defects related to the feature are fixed.
|
|
|
|
|
|
### Development workflow
|
|
|
* Boards;
|
... | ... | |