Process for NEW Enhancements

Step
1 Client enters the requirement in ServiceNow as Application Enhancement
2 Suncor Ops reviews and approves the enhancement in ServiceNow
3 Suncor Ops assigns the estimate task in ServiceNow to IBM Scrum Master

4 IBM Scrum Master receives the task and adds the enhancement item in Sharepoint

1. IBM Business Analyst analyzes the enhancement

2. Creates a D&S document for the enhancement and uploads it to livelink location
(Sample)- http://livelink/ecmlivelinkprd/llisapi.dll?
func=ll&objId=569267420&objAction=browse&viewType=1
3. Adds the estimation in the estimate task and closes it
If the state above is Pending Discovery, the BA sets up a D&S session with the
5 Business, developer and Suncor Ops (optional)
6 Suncor Ops reviews the estimates and provides approval

Setting Up a release - Sample Release Jan 9

Release cycle - 6 weeks

Week 1 (Deciding what goes in a release) - Start Date - Nov 28 - 6 Weeks before Prod Deployment Date of Jan 9

S.No Date

1 28-Nov-18

2 28-Nov-18

3 29-Nov-18

5-Dec-18

Week 2 - Start Date - Dec 6, 2018 - 5 Weeks before Prod Deployment Date of Jan 9

6-Dec-18

11-Dec-18

11-Dec-18
 11-Dec-18

11-Dec-18

12-Dec-18

12-Dec-18
12-Dec-18

Week 3 to Week 4

Dec 13 to Dec 19

Dec 20 - Dec 24

Dec 20 - Dec 24

24-Dec-18

24-Dec-18
25-Dec-18

25-Dec-18

26-Dec-18

Week 5

Dec 27 to Jan 2

Week 6 (Final Deployment week)

Dec 27 to Jan 4

7-Jan-19

7-Jan-19

8-Jan-19

9-Jan-19

9-Jan-19

10-Jan-19
 Move state in sharepoint to

Pending Estimation

Pending Suncor Approval or Pending Discovery if a D&S is required

Pending Suncor Approval (After D&S session is complete)

Approved by Suncor (Or Pending Estimation if not approved)

efore Prod Deployment Date of Jan 9

Task Update in sharepoint

IBM Scrum Master sets up a meeting with Suncor Ops and BA to decide
what goes in Jan 9 release
IBM Scrum Master enters the release date in sharepoint for items as per
the outcome of the above meeting Scheduled
IBM Scrum master or Suncor Ops (TBD) sends emails to business advising
the release items and if any changes are required
IBM Scrum Master finalizes the release of Jan 9 and sends a final
confirmation to Suncor Ops about the release list

IBM Scrum Master sends email to IBM PMO a list of RITMs for which a
new ILC Code is required
IBM Scrum master enters the ILC# for each item of Jan 9 release in
sharepoint as per the ILC activity codes given by IBM PMO Updates ILC# in sharepoint

IBM Scrum Master distributes the enhancements between developers and

assigns enhancements to developers in sharepoint
IBM Scrum Master creates a Peer Review checklist version on livelink for
this release and assigns peer reviewers for each enhancement in this
release
IBM Scrum Master sends a confirmation to DEP Developers to start
enhancement from their start of Day - Dec 12 2018 SN - WIP - Analysis
DEP Developers start analyzing the enhancements and send a
confirmation email about requirements directly to business
DEP Developers send a confirmation to IBM Scrum master about the
estimates and inform if estimates need to be updated SN - WIP - Development
IBM Scrum Master creates a QA change and Prod Change for Jan 9

1. Developers find associated test cases in HPQC and start updating them
2. Developers create new Unit, Integration and Functional Test cases in
HPQC
3. Developers complete the enhancements in DEV SN - WIP - Development

1. Developers complete unit testing and integration testing in HPQC

2. Peer reviewers complete testing and code peer review for assigned
enhancements SN - WIP - Unit Testing or SN -
3. IBM Offshore Technical Lead reviews the test plan of all enhancements WIP - Integration Testing
Developers ensure AID and TDS (if required) is updated for this
requirement
IBM Scrum Masters ensures QA Change is ready and reviews it and then
gets Suncor Ops approval

1. IBM Offshore Technical Lead provides confirmation about review of test

plan for each enhancement to IBM Scrum Master
2. Developers update the QA Change with the update sets
3. Developers update the Deployment Document with change steps and
smoke tests
Operations Oncall resource performs Deployment to QA for UAT

IBM Business Analyst performs smoke testing of each enhancement in QA

1. Developers send UAT Email to Business
2. IBM Scrum Master reports any delays to individual business Pending Suncor UAT

Business performs UAT and reports all issues by Jan 2

Developers report UAT defects in HPQC and fix the defects latest by Jan 4
2. Developers update the Prod Change with the update sets
3. Developers review/update the Deployment Document with change
steps and smoke tests Pending Suncor UAT
IBM Scrum Masters updates final state of enhancement in sharepoint and
ensures all sign offs have been received Pending Production Delivery
IBM Scrum Master defers any enhancement which is not signed off to next
release and informs the business and the developer
IBM Scrum Master reviews the Prod Change and gets Suncor Ops Approval
on the change
IBM Scrum Master prepares the release notes email and gets it reviewed
by IBM Delivery Lead and Suncor Ops Lead

1. IBM Ops oncall resource performs the deployment in Prod and performs
any required smoke tests
2. IBM Ops oncall resource sends a notification to all businsess and
operations about release completion

Developers send email to individual business about Prod sign off and
update sharepoint to close the enhancement and also close the
enhancement in sharepoint Closed