Basic presentation

Deliverables PI-planning 2020Q2

• Objectives
• Planning
• Dependencies & Risks
• Confidence & retrospective

Objectives

JIRA "RAINBOFEAT PIObjective Kanban Board"

• Issue Type: Objective
• Expected Value: x/10
• Summary
• Description: SMART
• Component: Team
• Fix Version/s: "2020Q2"
• Stretched: Yes/No

Objectives: SMART

Planning: Team level

• Physical planning board
• Features & high level stories
• Detail stories for first sprint
• Jira team board for consolidations
• Post-it app can be used to share within distributed teams

Planning: Program Level

• All features on JIRA "ART Rainbow (PI Planning)"

• Issue Type: Feature
• Summary
• Description
• Component: Team
• Fix Version/s: "2020Q2"
• Labels: "PI"

Planning: Product Group Level

• All target dates in template assigned to product group

Dependencies & Risks

• All Dependencies and Risks on JIRA "ART Rainbow (PI Planning)" as feature

Risks

• Description: what is the risks?
• Component: Team
• Fix Version/s: "2020Q2"
• Labels: "PI" + "RISK"
• Default column: Risks

Dependency

• Copy of dependent feature
• Extra suffix in title: XXX_YYY_Z
• XXX = Team as requester
• YYY = Team as assignee
• Z = expected sprint
• Description: what is expected?
• Component: assigned team
• Fix Version/s: "2020Q2"
• Labels: "PI" + "DEP"
• Default column: Dependencies

Confidence & Retrostective

• A survey will be sent by WhatsApp at the end of the PI-planning

• Cockpits
• Permanent Skype sessions
• Sharepoint
• Jira
• Mobile phone

12/03: PI-planning 2020Q2 – Day 1

09:00 - 11:00: General info session

• For: everybody
• Medium: War room Skype

11:15 - 15:00: 2 breakouts

• For: Teams
• Medium: Cockpit + Team Skype

15:30 - 17:00: Plan Review

• For: everybody
• Medium: War room Skype

13/03: PI-planning 2020Q2 – Day 2

09:00 - 09:30: Adjustment planning

• For: everybody
• Medium: War room Skype

09:30 - 12:15: 1 breakout

• For: Teams
• Medium: Cockpit + Team Skype

13:00 - 15:30: Plan Review & closure

• For: everybody
• Medium: War room Skype

Preparations

• Prepare capacity for your team per sprint (Scrum Master)
• Create WhatsApp group of your team (Scrum Master)
• Assign team member responsible for digitalizing deliverables
• Try SMART objective based on a known feature
• Prepare your features as good as possible: Benefit, Acceptance creteria, Dependencies, risks, workload

Agreement & fair warnings

• Due to the Corona virus all gathering in groups should be avoided
• For the same reason all flights and catering have been canceled
• Collaboration through digital devices become even more important.
• Test them before the PI-planning starts
• All Skype links should be open at all times
• Time boxing is key. respect the timings
• During the first break out a lot of dependencies are not known yet
• Start to plan according to the best, yet realistic scenario
• For the local entities this means to get feasible target dates both for business requirements as for data delivery
• It's the first time a PI-planning is done this way. We may expect some hicups

Organization

• Chat session should opened by at least the country representatives
• Collaboration can be in all directions
• A WhatsApp-group need to be made of all participants in order to capture their confidence vote and feedback.

Chat Sessions

Who should be involved?

• Country Spocs
• Dataproject representative at local side
• Standby of 4 business domains to discus feasibility
• Standby of data team to discus feasibility

Chat Sessions

Agenda

• The local entities are expected to participate to all events.
• General sessions should be followed via the War room Skype
• At the end of each breakout a dedicated moment is foreseen to capture questions and deliverables which replaces the SoS

Mission: 14 new pipelines

• Static Reference Data
• Debt Securities V2
• Party + including HM and CCG enrichment
• IR Swaps (IR + CCIR)
• FX Trade (FX Spots + FX Forwards)
• Simple Loan Agreement
• Facilities
• FX Swaps (addon IRS)
• Party Risk Metrics
• Agreement Risk Metrics
• Options (IR & FX)
• GL Balance
• GL Chart of Accounts
• Collateral (only for credits)
• IFRS9 ECL

What is expected: target dates

• Base yourself on the prioritized list of product groups as presented at the start of the PI-planning. The current view can be seen in previous slide.
• Imagine you receive each 2 weeks input of 3 product groups following the priority
• The input comes from group function for the completion of the information requirements
• The input comes from the Data Integration Teams as model of the IC + documentation)
• Plan time for local business to complete information requirements and put target dates per product group
• Plan time for local data teams to capture the sources, do some prototyping and complete the mapping document both functional as technical.
• Forward retrospective survey to all participants

Build:

Manual

Deliverables 2020Q1