0% found this document useful (0 votes)
113 views

Agenda: Blockers (Risks, Issues, Assumptions, Dependencies)

The weekly agenda covers 4 topics: 1) Weekly progress update 2) Upcoming week milestones and activities 3) Blockers such as risks, issues, assumptions, and dependencies 4) Any other business

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
113 views

Agenda: Blockers (Risks, Issues, Assumptions, Dependencies)

The weekly agenda covers 4 topics: 1) Weekly progress update 2) Upcoming week milestones and activities 3) Blockers such as risks, issues, assumptions, and dependencies 4) Any other business

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

AGENDA

WEEKLY PROGRESS
1

UPCOMING WEEK MILESTONES/ACTIVITIES


2

BLOCKERS (RISKS, ISSUES,ASSUMPTIONS,DEPENDENCIES)


3

AOB
4

2
OPEN BANKING ENABLEMENT : WEEKLY TASK PROGRESS - ICUBE Reporting Period: 25 May– 29 May 2020
Partner Lead: [Ailton Miguel] RAG Status: GREEN – (per definition in annexure)

Back Log   On Track   On Schedule by next report   Behind Schedule  


B
B G I II
Tasks Accomplished (This Week)
(Most Important)
(Most Important)
Tasks Planned (Next Week)
(Most Important)
C Number were created by SBM for Innovation Cube resources. Focus on the following:
VPN connectivity was established between Innovation Cube resources
device and SBM network.
Innovation Cube resources we onboarded on to Innovation Cube  Getting the putty connecting into SBM network servers.
Emails System.
Socialization and Email communications between SBM and Innovation  Allocation of ACE server with prerequisite done.
Cube resources has started.
 Get the ACE binaries and licence to install on the allocated server.
 Get access to Confluence for documentation upload.

Milestones Target Completion Date Status


(Major / Key Activities) (Original Target Date in Brackets)
Main Open Issues and Risks
(Most Impactful Implementation Blockers)
Kick-Off 19-May-2020 (-) G
G
1 Onboarding and Email creation of Innovation 20-May-2020 (-)
Cube resources for open banking enablement
2 project. G
3
Key Decisions
4

2
OPEN BANKING ENABLEMENT: Actual PROGRESS vs. PLAN Reporting Period: 25 - 29 MAY 2020
Technical Lead: DHIRAJ CHAUHAN
Back Log   B On Track G  On Schedule by next report   Behind Schedule  
B G II II

Partner Person/s Work Items Planned End Date Actual % Projected Status Action required to address
Responsible Progress End Date backlog

SBM Jacob C-Numbers 28 May 2020 100% 28 May 2020


G
SBM Lazaro VPN Access 28 May 2020 80% 29 May 2020 Need to fix the Putty and RDP error.
G
SBM Jacob & Raja APIs List 02 May 2020 50% 02 June 2020
I
SBM Jacob Access to confluence 01 May 2020 0% 01 June 2021 I Haven't got any traction on this Item

SBM Anibal Server allocation as per 29 May 2020 100% 03 June 2020 Innocence need to verify so that
pre-requisite specs I sever can be replicated.

SBM Ricardo Provide software binaries 29 May 2020 0% 01 June 2020


I

3
OPEN BANKING ENABLEMENT : Risks
Period: 25 - 29 MAY 2020
Technical Lead: DHIRAJ CHAUHAN RAG Status: Amber

Accountable Risk Impact Owner Target Resolution Risk Rating


Partner Date

1. Server allocation as per 1. Progressing to the next phase of installation of ACE will be 1. Chemane 1. 29/05/2020 1. M
pre-requisite specs delayed If the servers not made available. Action: Need to Anibal 03 JUNE 2020 2. L
come together if need be and push this with SBM.
SBM

1.Provide software binaries 1. At a risk of missing Installation deadlines. 1. Ricardo 1. 29/05/2020 1. M


Actions: 2. Ailton 01 JUNE 2020
SBM a. Ricardo need to provide the binaries

4
OPEN BANKING ENABLEMENT : Issues Reporting Period: 08 - 15 MAY 2020
Technical Lead: DHIRAJ CHAUHAN RAG Status: GREEN

Owner Issue Impact & Mitigating Actions Assigned To Target Resolution Impact
Date Severity

5
OPEN BANKING ENABLEMENT : Annexure I
Technical Lead: DHIRAJ CHAUHAN
OPEN BANKING ENABLEMENT : RAG Definitions

RAG Definitions
• Not all activities for delivery have been planned and / or resourced
• Activities planned has not been initiated or has been initiated, but progress is not on track to meet planned target dates
• All required resources and logistics to support the planned activity are not going to be in place on time to meet delivery target dates
• There are gaps in accountability assigned and timelines are not trackable
• No action plan or mitigation actions in exist / visible to address risks
• Decision required with regards to contractual, financial, process or delivery issues to meet delivery
• Delivery impact due to inability to gather information and produce documentation
• There are applications impacted by OBE, for which allocation to the relevant partner will be completed by next reporting period
• Activities required for delivery have planning & resource gaps which will be completed by next reporting period
• There are actions in place to ensure that for activities planned which are lagging in progress, those activities will be back on track by the next
reporting period
• Process articulation and documentation is in progress, however assistance is needed to ensure OBE requirements are met.
• There is evidence of accountability and actions are in place to close gaps by next reporting period
• Status is expected to return to green within next reporting period
• All applications impacted by OBE have been identified and allocated to the relevant partner
• All planned activity for the period has been initiated and is progressing to plan
• All required resources and logistics to support the planned activity are in place
• There is accountability assigned and timelines are trackable

26
OPEN BANKING ENABLEMENT : Risk Rating
Technical Lead: DHIRAJ CHAUHAN

Impact Severity Description Probability Description


[value]

High [3] An event that, if it occurs, will cause significant scope,


resource and/or schedule increases (e.g., increases of more High [3] High likelihood of risk materialising i.e. almost
than 5 percent) on the project. certain to occur, 70% – 99%

Moderate [2] An event that, if it occurs, will cause noticeable scope,


resource and/or schedule (e.g., increases of not more than 5 Moderate [2] Fairly likely that risk will materialise i.e. i.e. 30% –
percent) on the project. 69% chance

Low [1] An event that, if it occurs, will cause small scope, resource
and/or schedule that, in most cases, can be absorbed by the Low [1] Risk unlikely to materialise i.e. less than 30%
project. chance

Impact Severity
Range Risk Rating
L M H
1-3 Low
L 1 2 3
4-6 Moderate
Probabilit

M 2 4 6
7-9 High
H 3 6 9
y

27

You might also like