...
Background
Solution
Scope
Actors
Details and Validations
Design Links
Notifications
Acceptance Criteria
Functional
Non-Functional
Stakeholders
Note: We will tag account managers, implementation SPOC, Engineering team, and other required stakeholders so that we are all on the same page about the design and status of a particular feature.
Links in the Issue
Test Cases
Related Bugs
Performance Report (if applicable)
Operations
Running Mission wise operations between Product <> Engineering/Platform <> Programs:
...
TBD Program/Implementation Process:
Looking to capture required Implementation related information in JIRA
Release feature’s implementation status
Reference application and platform related bugs reported during implementation
Feedback
TBD is based on the final agreement with all program managers. Since we want to look at being more open, consideration for the above points
Issue Workflow
Product/Design
...
TBD based on updated Done process
Implementation
TBD
We can set up various workflows depending on the type of work. But for now, this should suffice.
| Note |
|---|
To run multiple sprints and standardize issue information, in RAIN project needs to be migrated to the next-gen JIRA. → Need support here. |
(WIP) Reporting
We will the Dashboards feature of Jira and set up reports for stakeholders. Some Work-In-Progress Sample Reports:
| Note |
|---|
We will need to sync between Product <> Engineering/Platform <> Program to finalize different types of reporting required for respective stakeholders. |