Skip to content

Latest commit

 

History

History
80 lines (58 loc) · 2.98 KB

pull_request_template.md

File metadata and controls

80 lines (58 loc) · 2.98 KB

Title

Please provide a title for the pull request.

Implementation date

Include when you plan to deploy this pull request

Description

Provide a description of what this pull request is doing. This should be in plain business language with any acronyms defined. Consider that the audience may not be experts in your field such as auditors or senior management.

Justification

Provide the reason why the amendment is required. eg New service, fix something or decommission. Ensure that if there are regulatory, cost, legal, security or support reasons that this is highlighted here.

MCOM / Service Now References

MCOM and / or Service Now References

Please insert any reference numbers to outside applications i.e. Change Request or Incident number from Service Now, MCOM reference number

Planning

Implementation Plan

List the steps in order of completion that will be worked through when implementing this pull request. Be specific if you are creating or changing objects eg. an Ec2 instance, RDS, code or form, state the name and location.

If the work is divided amongst multiple resources state who will carry out which step and if there are any dependencies on steps.

Risk and Impact Analysis

*Optional field if you would like to add any analysis not captured in the risk assessment.

Back Out Plan

Describe the steps you will take to revert the pull request to its pre-implementation state. Be specific, if particular objects need to be restored provide the name and location of the object.

Revert Pull Request and Redeploy

Test Plan

Populate the test plan with steps you will take to test the pull request

Risk Analysis

What is the business criticality of the item to be changed (If in doubt seek advice)

  • Business Continuity Application or Service e.g. Agresso, Funding Platform, Bloomberg
  • Business Essential (departmental system that can be worked around)
  • Application level impact (e.g. Upgrade)

What is the impact to Wellcome if this pull request fails?

  • Legal / Financial / Reputational
  • Moderate widespread disruption
  • No key systems affected / Back end systems only

How many users will the pull request affect?

  • Wellcome Wide (100+ people)
  • Department Wide (6-100 people)
  • Team / Individual (1-5 people)

Will there be a user facing service outage during the pull request implementation?

  • Yes
  • No

Have you carried out this type of pull request before?

  • No, Never done before
  • Yes, there are many steps and multiple teams involved
  • Yes, many times and it is documented

Is this change approved by you line manager?

  • Not line manager approved / aware
  • Line manager approved / aware

Internal stakeholders advised e.g. Service desk?

  • Yes
  • No
  • N/A

Relevant documentation produced / updated / retired? Confluence etc

  • Yes
  • No
  • N/A

Please provide a link to the Documentation

Replace with link name