- Ensure it is kept up to date and relevant.
- Chase people (Onshore and Offshore) who are not filling it in before the daily meeting.
- Use it to drive topics for discussion in the daily call.
- Look for opportunities for continuous improvement.
- Manage Jira Board.
- Manage#fpa_change_management Slack channel.
- Ensure tickets are assigned to the right people.
- Chase progress on open items.
- Ensure Jira tickets are kept up to date.
- Present current progress and blockers at least weekly to the FP&A team meeting or in a separate session.
- Ensure there is bigger-picture thinking so that changes do not contradict each other and are appropriately prioritized.
- Centrally coordinate changes that impact multiple teams or applications.
- Plan changes while understanding dependencies
- Perform UAT unless otherwise agreed.
- Should not test own development work.
- Ensure testing is appropriate and provides sufficient assurance.
- All changes must be tested before release/rollout.
- Evidence of testing must be recorded in Jira.
- During ticket creation/allocation, agree on appropriate reviewers and approvers.
- Ensure changes receive approval before implementation.
- Approval evidence must be recorded in Jira
- Ensure it is kept up to date and relevant.
- Chase people (EXL and Convex) who are not filling it in before the daily meeting.
- Use it to drive topics for discussion in the daily call.
- Look for opportunities for continuous improvement.