|
|
# Ways of working
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
*(Updated 2 Nov*)
|
|
|
|
|
|
The Proposal "NCBI Deployment 4" describes the following process, which improves on the current ways of working.
|
|
|
|
|
|
## Working process updated by Proposal "NCBI Deployment 4"
|
|
|
|
|
|
1. We will abide by, and improve upon, the existing documented processes as outlined here.
|
|
|
2. No documents are to be considered canonical documentation of requirements apart from what is included in GitLab issues, Gitlab epics, and the DDWG minutes.
|
|
|
3. Before new development starts on any issues all documentation of requirements listed above must be provided in GitLab and be fully reviewed and updated by the NCBI-Coko development team during a design review meeting, which could be during an existing bi-weekly Coko-NCBI review call. All relevant NCBI and Coko developers necessary to complete the work must be present.
|
|
|
4. NCBI to write acceptance criteria for all issues, these criteria to be summarised in the Epics with reference to specific issues. Acceptance Criteria to be agreed to by Dione Mentis before proceeding. No acceptance criteria to be created without being associated with an existing issue.
|
|
|
5. Deliverables will be broken down into 2-week cycles for testing as per [this agreed process](https://gitlab.coko.foundation/ncbi/ncbi/-/wikis/Project-overview/ways-of-working#testing-agreements)
|
|
|
6. Testing must occur within one week of the delivery for a 2 week cycle.
|
|
|
7. NCBI must continue to focus on simplifying the platform to deliver a product as soon as possible.
|
|
|
8. No changes to deliverables for UI improvements in this period except via change order.
|
|
|
9. Items removed from the development list to be reported to MSCWeb.
|
|
|
10. No changes to agreed deliverables once development has commenced on these issues.
|
|
|
11. No work to be done by Coko in this period (Aug 1–Dec 31) to specify any development work beyond this period.
|
|
|
12. Any changes to current epics, issues and deliverables that are deemed by Coko to increase the amount of work beyond current estimates will be handled under a "change order" process. Dione Mentis will communicate in writing a summary of scope change and corresponding costing adjustments to MSCWeb for approval before work commences on those items.
|
|
|
13. Each week Coko will document an updated confidence level for delivering a product by Dec 20.
|
|
|
|
|
|
|
|
|
## Use case epics
|
|
|
|
|
|
The epic diagrams, provided by NCBI project owner (Stacy) in April 2021 describe NCBI's business uses cases. They include mitigations for a Phase 1 release that excludes supporting users with roles: Data Supplier and Investigator (aka Awardee) and limit existing roles in the PDF and XML workflows to Org Admin and PDF2XML vendor (PDF wf only).
|
|
|
|
|
|
The epics are organised into [parent epics](https://gitlab.coko.foundation/groups/ncbi/-/epics?label_name%5B%5D=parent-epic)
|
|
|
|
|
|
In phase 1 the priority must always be to develop the simplest implementation to meet these use cases, especially the ability to process content in all workflows and allow data migration.
|
|
|
# Managing development sprints
|
|
|
|
|
|
## Scoping development
|
|
|
|
... | ... | |