...
- The ticket is marked
IN PROGRESS
and assigned to a developer, who conducts the meeting - A meeting is created in Outlook to contact interested parties (i.e. NDS Labs Dev team, Nebula team, other NDS-affiliated software teams, etc.)
- The requirements are discussed with the development team and any interested parties
- Any information resulting from the discussion is filed into a Confluence wiki page
- The information from the Confluence page generates use cases
- If applicable, a new Epic is created to encompass the use cases presented
- The use cases are filed as Story tickets and associated to an Epic
- The ticket is marked
IN REVIEW
and assigned to another team member for review - The reviewer may make any changes or comments that they desire and discuss with the team
- The ticket is marked
RESOLVED
orCLOSED
- The resulting Epic / Story tickets are then discussed at the next Sprint Planning meeting
...
- The ticket is marked
IN PROGRESS
and assigned to a developer (referred to hereafter as "the developer") - The developer does the work necessary to enable the use case described in the ticket
- Follow the general development workflows defined above
- Comment on the Story with links / updates to any deliverables that
- need to be reviewed / tested:
- Pull Requests
- Docker Images
- Documentation
- The ticket is marked
IN REVIEW
and assigned to a tester (referred to hereafter as "the tester") - The tester reviews the deliverables of the Story:
- Review any related Pull Requests
- Review any Test Cases / Documentation provided
- Review any new tickets resulting from the work done
- Pull and run any new Docker images against the Test Cases provided
- The tester needs to Accept, Reject, or Abort the review based on the results
- If the ticket does not contain sufficient information to decide whether or not the deliverables are acceptable, then the tester
Review Accepted
and the- selects
Review Aborted
- The ticket is marked as
OPEN
and work is stopped on the ticket - The developer adds more detail to the ticket, for example:
- Test Case
- Passing Conditions
- The developer then returns to #2 above and refines their deliverables
- The ticket is marked as
- If the the deliverables are missing, incomplete, or in an untestable state, then the tester selects
Review Rejected
The ticket is marked as
IN PROGRESS
and should then be assigned back to the developer- The developer then returns to #2 above and refines their deliverables
- If the deliverables are tested and in an acceptable form, then the tester selects
Review Accepted
- The ticket is marked as
RESOLVED
- The tester continues the workflow below
- The ticket is marked as
- The tester merges any outstanding Pull Requests related to this ticket
- The developer switches back to their master branch and syncs with the new changes
- If applicable, the developer builds and pushes a new "latest" Docker image for the API / UI incorporating the new changes
- The developer selects
CLOSE TICKET
and the ticket is marked asCLOSED
...
- A Bug or Improvement ticket is filed detailing a potential modification that will have a positive impact on the platform
- If necessary, a Requirement ticket is filed to explore the ramifications of the changes
Improvement Workflow
Improvement tickets follow a workflow that resembles that of a Story ticket
Reporter:
- Developer
When an Improvement ticket is in the Active Sprint:
Deliverables:
Bug Workflow
Reporter:
- Developer
When a Bug ticket is in the Active Sprint:
Deliverables:
Accounting Workflows
Issue Types Used:
...