We are often left to address the gaps from architectural principles (which stay at a pretty high and abstract level) to the actual implementation detail. Here is an attempt to bridge that gap by providing a set of Lightweight Architecture Decision Records (LADRs) which are simple to follow and can be implemented in a given team/project by the developers
Taxonomy for issues to ensure efficient tracking and governance of PMC projects
- Under review
Context & Scope
The proposal can be found here for review.
It is suggested that after a first pass review of the proposal to refine, that this is put to trial for the System and Data flow projects using the proposed methodology.
The taxonomy guideline can be further refined based on practical application in these projects and then baselined.
Stage-1: Review with CSP leads, program managers and OSDU lead to get first pass feedback.
Gitlab issue list and boards are very generic and we need to be able have visibility at program level for macro tasks and be able to define, assign and manage micro level tasks within a repo or sub-project level as well using the same system.
The current issue list is unwieldy and therefore becomes a management and governance challenge. A working model is in order to get us to a productive environment in Gitlab.
When to revisit
Suggest 3 sprints of practical application in System and Data flow projects and to review after that
Tradeoff Analysis - Input to decision
Alternatives and implications
Decision criteria and tradeoffs
- Ability to manage and track ADR record lifecycle
- Ability to manage and track macro backlog items for program level reporting, detailed backlog and defect items at project level for assignments
- Ability to define CSP specific issues and defects and track their assignments and progress