# data[].attributes.headline
Devs: To have CoP every other week (5-15 mins presentation + 20 mins discussion). Devs to facilitate. Rotating setup.

# data[].attributes.subject
Devs: To have CoP every other week (5-15 mins presentation + 20 mins discussion). Devs to facilitate. Rotating setup.

# data[].attributes.headline
SM: Create JIRA dashboard for tickets (parameters need to check w/ sir david)

# data[].attributes.subject
SM: Create JIRA dashboard for tickets (parameters need to check w/ sir david)

# data[].attributes.headline
Devs+TSO: Create and maintain centralized location for helpful links (previous bugs resolved, testing procedures, scripts) in Confluence.

# data[].attributes.subject
Devs+TSO: Create and maintain centralized location for helpful links (previous bugs resolved, testing procedures, scripts) in Confluence.

# data[].attributes.body
Perhaps fixes on previous incidents can help provide insights on how to prevent future similar incidents.

# data[].attributes.headline
Devs to update confluence pages (share screenshots, updates etc)

# data[].attributes.subject
Devs to update confluence pages (share screenshots, updates etc)

# data[].attributes.headline
Have initial discussions before committing or starting tickets

# data[].attributes.subject
Have initial discussions before committing or starting tickets

# data[].attributes.headline
Template improvement. Add comments in JIRA about SLA compliance to improve prioritization.

# data[].attributes.subject
Template improvement. Add comments in JIRA about SLA compliance to improve prioritization.

# data[].attributes.body
Best if everyone is calibrated when it comes to which tickets are urgent, which ones are about to fall off SLA that would need prioritization. This can be done by having clear SLA details when assigning tickets and possibly ticket comments too.

# data[].attributes.headline
If a ticket has been replicated or there is a demonstrated possible cause, e.g. error logs match a Stack Overflow post very closely, mark it as a ticket that was "responded to."

# data[].attributes.subject
If a ticket has been replicated or there is a demonstrated possible cause, e.g. error logs match a Stack Overflow post very closely, mark it as a ticket that was "responded to."

# data[].attributes.headline
Share testing procedures or scripts when possible. E.g. Postman queries stored in a repository or Google Drive folder.

# data[].attributes.subject
Share testing procedures or scripts when possible. E.g. Postman queries stored in a repository or Google Drive folder.

# data[].attributes.body
Provide clear acceptance criteria.

# data[].attributes.body
Clarification of tickets with client

# data[].attributes.body
Provide consistent updates on tickets.

# data[].attributes.body
For ticket allocation: Availability in at least initial review/assessment of the ticket. From there, a realistic assessment is given when it comes to how complex the ticket is and if how much time is needed.

# data[].attributes.headline
Escalate ticket if needed to address within timeline

# data[].attributes.subject
Escalate ticket if needed to address within timeline

# data[].attributes.headline
Assigning advanced tickets so incase a blocker is encountered on current ticket dev could work on other tasks

# data[].attributes.subject
Assigning advanced tickets so incase a blocker is encountered on current ticket dev could work on other tasks

# data[].attributes.headline
Find a way for a manager to review tickets and suggest improvements or to find examples to share with the team. These may be code-related, best practices, or resources such as websites or Udemy courses.

# data[].attributes.subject
Find a way for a manager to review tickets and suggest improvements or to find examples to share with the team. These may be code-related, best practices, or resources such as websites or Udemy courses.