DCP Enhancement Requests

Introduction

An enhancement can bring new capabilities to an existing system. Enhancement projects might also involve correcting defects, adding new reports, and modifying functionality to comply with revised business rules or needs.
‍

Jira is used for DCP enhancements in the following workstreams: Sales, Service & Support, Customer Care and Marketing as of August 2023.
‍

Currently Sales requests are only managed by Sales Ops, but in theory everyone has access to the request intake form and can raise enhancements.

2024 Quarterly Release Calendar

Quarterly Release Calendar: Region-Impacting Milestones

Milestone	Region’s Role	Q2'24	Q3’24
New Requests Due	Submit new requests for consideration. Discuss with POs in grooming calls NOTE: The final date by which all requests that want to be considered for inclusion in the upcoming quarterly release must be submitted. Allows for a month to evaluate, groom, and estimate it before the last sprint of the release starts.	Completed. Now - Jan 26	Completd. Now - April 26
Stories groomed	Attend regular PO grooming calls to provide input	Completed. Now - Jan 26	Completd. Now - April 26
Scope locked (by sprint)	• Attend bi-weekly calls to provide feedback on the proposed scope based on the JIRA backlog ranking. • Attend sprint end-user demos and provide feedback	Jan 11 Feb 1 Feb 22 Mar 14	April 4 April 25 May 16 June 6
UAT Tester Resource	Provide UAT tester names needed to setup JIRA testing and send out UAT meetings	Mar 15 - Mar 29	June 7 - June 21
UAT	• Attend daily stand-ups if there are questions or issues • Update JIRA testing status. Log bugs as needed	Apr 15 - Apr 23	July 10 – 23 (may start as early as Wed July 10th)
Release notes	Review release notes to be aware of new enhancements	April 26 (Send for feedback) Week of May 13th (Post)	July 26 (Send for feedback) Week of Aug 12th (Post)
Go-live	• Log SNOW tickets for any issues. • Attend hypercare calls to discuss	May 20	Aug 19

IAPT Workflow

1. RCL from submitting region to review and complete the following

Review and update the Title, Problem Statement, and Business Issue on the Key Fields tab
‍
Complete Impact Summary, Potential Risks, Dependencies, and OCM Considerations on the Evaluations tab
‍
Provide regional scores for each dimension on the Scores tab

2. RWL from submitting region to review and complete the following

Consider cross functional impact of the request and validate the information provided by the SME in the previous stage
‍
Approve or Reject the Impact Evaluations for the submitting region on the Evaluations tab

3. GCO to review and complete the following

Validate the enhancement request and consider the technical feasibility of pursuing it
‍
Complete Impact Summary, Potential Risks, Dependencies, and OCM Considerations on the Evaluations tab
‍
Approve or Reject the Impact Evaluations for the GCO on the the Evaluations tab
‍
Update the Release Type and Sprint fields on the Key Fields tab

4. If approved by GCO, the remaining 3 regions to review and complete the following

Review all fields completed by the submitting region on the Key Fields tab
‍
Complete Impact Summary, Potential Risks, Dependencies, & OCM Considerations on the 'Evaluations' tab
‍
Provide regional scores for each dimension on the Scores tab
‍
Review the benefit measures on the Measures tab

5. GCO to review and complete the following

Consider the individual Impact Evaluations provided by each region on the Evaluations tab
‍
If rejected, Cancel the request with the appropriate Reason code on the Status tab

6. GWL to review and complete the following

Create a new record in JIRA and capture the JIRA Story link to the Link field on the JIRA tab
‍
Update the Sprint field to reflect what is being used in JIRA on the Key Fields tab
‍
(GCO) Write the user story in JIRA and update its stage to Estimation & Prioritization when ready to be estimated

7. GCO to review and complete the following

Update the Sprint field to reflect what is being used in JIRA on the Key Fields tab

8. GWL to review and complete the following

Update status to Estimation when handed over to Deloitte / GIS for story point estimation

9. GWL to review and complete the following

Capture the Story points on the JIRA tab

10. GCO to review andcomplete the following

Determine which stories should be included in the upcoming release and update Key Fields and Status tabs as appropriate

11. GCO to review and complete the following

Following successful deployment of the enhancement, close the request by changing stage on Status tab

Additional resources from diagram

‍

Other Resources

JIRA Request
Intake FAQ

JIRA Request Intake & Prioritization
Tool Training

JIRA Migration
Go-Live Training

JIRA Request Intake - Regional Capability Owner