...
Code Coverage
New code must have a coverage of 80% or greater unless explicitly noted otherwise in the story's acceptance criteria.
Static Code Analysis
All reported code smells, security vulnerabilities, and lint errors identified by SonarCloud and other CI pipeline tools must be fixed before merging code to the master branch.
There should be no code smells bugs or security issues should be reported by SonarCloud upon merging.
Code uniformity
All new code should follow Code Uniformity standards
...
PR Descriptions
Every PR should include a detailed description with:
Purpose: The intent and objectives of the changes and a link to the User Story (if available).
Approach: The methodology and reasoning behind the implementation.
Open Issues: Any unresolved questions or potential problems.
Approval Requirements
A minimum of two developers must approve each PR.
At least one approver must be a team lead or architect.
...
Jira Workflow Columns
Todo
Blocked/Questionable
In Progress
In Code Review
In Deployment
In QA
In PO Review
Done
Status Transitions
Todo: User stories are placed here when ready to be picked up. The user story is estimated and has a “Fix Version”.
Blocked/Questionable: Move the story here if some impediments or uncertainties need resolution.
In Progress: Move the story to In Progress when development begins.
In Code Review: After development is complete and a PR is ready, move the story to In Code Review. If it is a bug, the RCA field should be fulfilled by the developer.
In Deployment: Once After deploying the code has been merged and is being deployed to the Kitfox Dev Rancher Environment for developer testing and validation, move the story to to “In Deployment” and merge the PR to the master branch. All comments in pull requests should be marked as resolved before the merge.
In QA: After deployment to the Kitfox Testing Environment, and when the QA team begins testing, move the story to In QA.
In PO Review: Once QA has verified the story and it's ready for Product Owner (PO) review, move the story to In PO Review.
Done: Move the story to Done after the PO has accepted the story and there are no critical issues remaining.
Acceptance Criteria
All acceptance criteria outlined in the user story must be fully met.
Critical Bugs
Ensure there are no open critical bugs associated with the user story before moving it to Done.
...
6.
...
Critical Bugs
Address all critical bugs associated with the user story before closure.
...
Demos
Demo Environment
All features eligible for demonstration should be demoed from the shared Kitfox Testing Environment.
Team Presentation
The story must be presented to the team during a demo session(if demoable).
The Product Owner (PO) moves the story to Done if there are no critical issues.
...
7. Spikes / Proof of Concepts (PoCs)
Documentation
Document all spike findings on the wiki and present them to the team.
Place PoC findings in the team's space on Confluence.
Code Accessibility
Check PoC code into GitHub to make it accessible to the entire team.
Follow-up Actions
Create user stories to implement or formalize the preferred approach or solution, if applicable.
Share the resulting Jira issues with the PO for awareness so they can ensure the issue metadata (labels, features, etc.) is accurate and complete.
Acceptance and Recording
The PO, and the architects' team if necessary, are responsible for accepting the PoCafter spike findings are presented and discussed.
...