T2 Operationalization VF PDF
T2 Operationalization VF PDF
Discussion document
20th February, 2020
1
1 Recap of our discussion
3 Operationalizing T2
2
1 Recap of our discussion
3 Operationalizing T2
3
Recap of our last discussion on 12th Feb
Summary
▪ TCB has delivered a solid performance over the last 4 years on the back of a customer-
centric integrated masterplan, strong management set-up and continued focus on
capability building
▪ TCB has experimented with an ‘agile’ project delivery approach as part of BB business
program and M+ project with encouraging outcomes
▪ Looking ahead, TCB has set bold aspirations for itself, which will require TCB to move on to
the next S-curve of growth and capabilities
▪ To successfully deliver on the next wave of transformation, TCB will need to significantly
shift its operating model
▪ In this context, TCB is now looking to scale up the agile delivery model through T2 - a focused,
customer-centric agile way of executing TCB’s strategy, that reinforces outcome-driven
culture in the bank
▪ As TCB prepares to operationalize T2, “People”, “Process” and “Technology” are the most
important elements – it should look to accelerate hiring of new digital talent, adopt agile as the
new way of working and invest in modernizing IT capabilities
4
TCB embarked on an ambitious transformation program starting 2015
ACCELERATE
Performance Management
UPGRADE
Foundations and Infrastructure
BUILD
People and organizational ▪ Return on Risk weighted assets
capabilities management
▪ BU – IT transformation ▪ Acceleration on Digital and Virtual
▪ Operational effectiveness bank
▪ Customer experience management ▪ Finance Transformation
▪ Business model transformation for ▪
PFS, BB, WB, GTS
HR transformation and leadership ▪ Agile development
development
▪ Data strategy
▪ Corporate Affairs transformation
▪ Customer value management
▪ Basel II
5
TCB has delivered solid performance in the first phase of transformation
1
Total lending
2
Total deposits
3
Total revenues
USD Bn USD Bn USD Bn
6.2
4.8 0.4
3 waves of implementation
7
TCB has experimented with an ‘agile’ project delivery approach
as part of BB transformation and M+
Key elements implemented BB highlights
▪ Physically co-located, cross-functional teams were set-up
~35% improvement TOI
(BB transformation, M+)
per focus customer (from
132 to 180 VND mn)
9
Achieving this aspiration requires a significant shift in TCB’s operating model
Waterfall, targeting “gold standard” – long lead- Agile “test & learn iterations” – quicker to
time to market market
Project team responsible primarily for Design Cross-functional team responsible for design and
scale-up (including Financial goals)
11
With this shift in operating model,
TCB would be very different in 2-3 years
12
12
1 Overall context of T2
3 Operationalizing T2
13
Snapshot of TCB’s Agile@Scale model (T2)
Agile@scale at TCB
10-15 tribes
T2 – Agile@Scale
Engine
14
T2’s target operating model design to achieve the end-state
Structure People
Decision Making Talent Planning
Strategy
15
T2’s target operating model design to achieve the end-state
16
Emerging end-state set-up for T2 COE Segment tribes Channel tribes Journey tribes Enabling tribes
CA
Wealth Management
Retail – Mass, Mass
Finance
Business banking1
Affluent, Affluent
iPMO CoE
HR
Payments
Mortgage
Banca
Cards
Auto
GTS
S&D
People Strategy
Risk
1 Includes Segment Squad; Both Business Banking and WB tribes can be further split into sub-tribes over time depending on the scale
17
Proposed T2 set-up for next 12-18 months COE Segment tribes Channel tribes Journey tribes Enabling tribes
Retail Corporate
Wealth Management
Sales
iPMO CoE
Operations
Payments
Mortgage
lending)
FMCG)
Banca
IT
People
Risk
1 Both Business Banking and WB tribes can be further split into sub-tribes over time depending on the scale
2 Execution cell designed in the context of M+ 18
T2 governance should be designed to ensure faster decision making
Bank
▪ For any decisions to be made ▪ Existing committees1
outside T2 set-up
committees
Technology
20
25 new roles are needed to operationalize the T2 set-up
Business Tribe lead IT Tribe lead Data and Analytics Tribe People Tribe lead
lead
UI Designer
21
Performance management should based on team goals/ KPIs
Thuy, Starting as a
AC Agile coach CL Chapter lead PO Product Owner
junior developer
22
T2’s target operating model design to achieve the end-state
Technology
23
Each tribe should ensure alignment and right prioritization through 9 Agile ceremonies (1/2)
Tue Wed Thu Fri Mon Tue Wed Thu Fri Mon
6 Daily stand-up
24
Each tribe should ensure alignment and right prioritization through 9 Agile ceremonies (2/2)
1 2 3
Annual Planning Quarterly Business Review Supersprint planning
What: Review and align Tribe’s strategic priorities, What: Review Tribe’s OKRs in previous quarter, align What: Review the goal and backlogs for
annual plan, budget and resources next quarter’s priorities and OKR the Supersprint (across sprints in the quarter) including
cross-sprints dependencies
Who: T2 Council, Tribe Lead Who: T2 Council, Tribe Lead
Who: Tribe Lead, Product Owners
4 5 6
Product Owner Synchronization Sprint planning Daily Stand-Up
What: Review and update synchronized product What: Review and prioritize backlog for next What: Review progress and set goals for the day
roadmaps across Squads (incl. any interdependencies) sprint (1-2 weeks)
Who: Product Owner, Squad members
Who: Tribe Lead, Product Owners, Solution Architect Who: Product Owner, Squad members
7 8 9
Squad backlog refinement Sprint review Retrospective
What: Update sprint backlog based on any new What: Review tasks completed in sprint and What: Team talk to discuss improvements in the
development (as needed) discuss progress way the team works
Who: Product Owner, Squad members Who: Product Owner, Squad members Who: Product Owner, Squad members
(no one else to attend)
25
T2 units will need to interact with Support Functions for 58 services
HR Risk
▪ Customer request
handling ▪ Regulatory reporting
▪ Customer complaints 6 5 ▪ Litigation
management
26
5 interaction models have been defined for these 58 services
1 Embedded as part of Fully absorbed as part of T2 tribes/units to deliver on Direct FTE cost
specific parts of customer experience and products, e.g. risk to T2 set-up
T2 tribes/units
Digital Marketing
People
▪ DevOps capability should be built to
enable Continuous Integration /
Continuous Deployment
Strategy Process
Technology
28
TCB should use microservices in order to make its architecture more resilient and flexible
Decision Customer
service service
From: To:
▪ Build from scratch features and core components ▪ Quick-deployable, reusable, and autonomous
every time microservices
▪ Each new feature requires extensive testing ▪ Pre-tested services reduce testing time
▪ Complex upgrades due to high rates of internal ▪ Easily update individual services without
dependency disruptions
▪ Costly scaling to accommodate changes in traffic ▪ Easily scale individual services up or down to
and usage meet new demand
29
A tiered API structure will enable TCB to identify the reusability level of the APIs depending on
its function
New platforms – transfer power direct to business users API catalogue
Current Accounts Credit cards Mortgage Global API catalogue (contracts, design, semantic data
requirements, etc.) managed centrally by service
design team to accelerate reuse where possible
30
TCB should build a Continuous Delivery pipeline that allows frequent releases
FROM: Manual testing, Details of the target picture: automated delivery pipeline
integration, and deployment ▪ Spin up dev and test
activities Automated environments
1 provisioning ▪ Activate storage and
processing capacity
▪ Fix bugs/errors/changes
Test-driven ▪ Agree test cases
2 development ▪ Code test cases Submit code for
Dev Test Deploy- ▪ Code functionality testing and review
ment
Automated Show
3 testing failed tests
▪ Run unit tests Put code in
review queue
TO: Automation of testing,
Automated Specify required improvements in code
integration, and deployment
4 code quality organization and readability ▪ Review code
activities (CI/CD) reviews ▪ Approve code for Commit code to
submission main version
31
1 Overall context of T2
3 Operationalizing T2
32
Operationalizing T2 requires focused effort across 9 elements
Strategy
8 Define a future proof
enterprise IT architecture 7 Test and refine the T2 operating
model through M+ and Banca
Technology Process
9 Build the next generation IT
capabilities (e.g., DevOps) for
Enterprise Agility
33
T2 operationalization plan for next 12-18 months (1/2)
2020 2021
Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul
1 Formalize T2-
setup
Formalize the proposed T2 set-up and governance (incl. policy and process changes)
2 Launch front-
runner tribes
M+, Retail Channel scale-up
3 Operationalize
new roles
Finalize success profiles,
EVP for the new roles
4
Set-up T2 Operationalize Continue hiring for the T2 end-state
Recruiting Execute hiring for
T2 recruiting
War Room front-runner tribes
war room
6 Roll-out
employee BOM T2
BOM Go-See-Learn
34
T2 operationalization plan for next 12-18 months (2/2)
2020 2021
Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul
8 Define future
proof enterprise Define enterprise-wide
IT architecture
Phased roll-out of the end-state, enterprise-wide architecture (incl. micro-services)
IT architecture
Ongoing solution development and implementation for Business Tribes, in line with the enterprise architecture
Technology
9 Build next
generation
Develop road-map for
Continuous Integration Phased roll-out of the automation capabilities to enable Continuous Integration and Deployment
IT capabilities for And Deployment
Enterprise
Agility
Infrastructure upgrade Ongoing infrastructure upgrade as needed
to support
Enterprise agility
35
1.FORMALIZE T2 SET-UP
T2 set-up needs to be formally approved with changes made in TCB’s policies/ processes
model)
▪ Secure approval for the proposed ▪ Secure approval for the proposed T2 ▪ Secure approval on the proposed
interim T2 structure councils interaction model between T2 set-up
▪ Detail out the mandate of each unit ▪ Outline the mandate of each council, and supporting functions
within the T2 structure including participants, agenda, ▪ Detail out the SOPs for each type of
▪ Secure approval for the proposed associated processes service in the context of M+
roles within the T2 structure ▪ Secure approval for the proposed ▪ Detail out the cost allocation
▪ Secure approval on the EVP of each changes in the decision making methodology for each type of
Check-list
role including career path, ▪ Outline the authority for each interaction model
compensation, band structure category of decision making ▪ Secure approval for the process
▪ Change HR policies and processes ▪ Develop SOPs for each type of associated within T2 – resource
to reflect the new T2 roles decisions management, portfolio value
management, budgeting
▪ Update bank’s overall corporate
governance framework with the T2 ▪ Update policies and develop SOPs
governance for the T2 processes
36
2. LAUNCHING FRONT-RUNNER TRIBES
Launching each of the front-runner tribe is an 8-12 weeks effort
Objective Approval to set up a small Proposed customer journey is part of BU’s masterplan
team to:
Tribe Lead has been appointed
▪ Define the scope of the
customer journey 2-3 member working team has been identified
▪ Develop a high-level
business case
1 2
Decision T2 Council
authority
38
2. LAUNCHING FRONT-RUNNER TRIBES 0 1 2
Pre-work phase: Team defines scope of the proposed customer journey and Set-up: Pre-
Exploration
develops a high-level business case work
Key Output
Team setup needed
High level business case and
▪ Tribe Lead (Owner) scope of customer journey
▪ 2-3 CJEs ▪ Market opportunity size
▪ High-level expected financial
impact
Activities
39
0 1 2
2. LAUNCHING FRONT-RUNNER TRIBES
Stage Gate 1: Team secures TECO approval for starting the exploration phase Set-up: Pre-
Exploration
work
Objective Approval of: Scope of the customer journey has been defined
▪ Proposed scope of the Business case for the proposed journey has been developed
customer journey
Exploration phase working team has been identified
▪ Business case
Weekly/ Bi-weekly cadences have been set up to update
▪ Team set-up to proceed progress
with the exploration
phase High-level CAPEX-OPEX budgeting plan
40
0 1 2
2. LAUNCHING FRONT-RUNNER TRIBES
Exploration phase: Team defines the proposed end-state customer journey Set-up: Pre-
Exploration
work
Key Output
Team setup needed
▪ Tribe Lead (Owner) ▪ Architect Solution set
▪ Customer Journey Experts ▪ Data analyst ▪ Solution elements map
▪ CX/ UX Designer ▪ Product roadmap
▪ Prioritized workplan
Activities ▪ Estimated financial impact
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8
▪ Capex and Opex required
41
0 1 2
2. LAUNCHING FRONT-RUNNER TRIBES
Stage Gate 2: Team secures T2 Council’s approval to launch the tribe Set-up: Pre-
Exploration
work
Objective Approval to launch the new Diagnostic and solutions mapped to customer journey
tribe and start “Build-test-
Detailed squad scope, OKR
learn” phase
Detailed squad member requirement for build phase
42
2. LAUNCHING FRONT-RUNNER TRIBES
A clear checklist exists to ensure that first release of any tribe is set up for success
Description
Viability The 1st release is scoped and set up in a way that it provides a decent chance of success
Appropriate
for 1st Release Visibility Unit is highly visible and will act as a ‘lighthouse’ for other units within the organization
Clarity of objectives The 1st Release has a clear set of objectives, which are measurable and agreed upon upfront by leadership
Leadership commitment Leadership is committed to the transformation, including transitioning to the role of servant leaders, role modelling
transformation behaviors and being open to coaching and feedback
Talent Unit is staffed with appropriate functional talent, which is amenable to coaching and open to work differently. i.e. with
“Incremental Delivery” and “Minimum Viable Products”
Organizational Unit is not hindered by organizational impediments (e.g. ongoing transformation initiatives) which might prevent it from fully
impediments engaging in the transformation
Scope Fit Representability The scope is representative (e.g. size, work type), to successfully showcase benefits
Technical feasibility The scope is suitable for delivery in the Agile Target Operating Model
Complexity The scope has moderate complexity i.e. not completely standalone but without numerous interdependencies and no new
technology being introduced
Risk Investing in developing a product or service within that scope has limited critical risks for the business
Setting Environment The release environment is stable (e.g. in terms of location, roles commitment), to avoid mixing results
Team The team is fixed with co-located full-time members and committed 100% capacity
Sourcing The unit has contracts allowing for Agile development (e.g. software developers via a vendor)
Impact Working Agile for this unit has clear advantages vs status quo to justify effort and risks
Business Involvement The unit can dedicate clear Business commitment in terms of resources and respective time commitment (e.g. fully
committed PO working side by side with team)
43
2. LAUNCHING FRONT-RUNNER TRIBES
Setting up iPMO CoE will involve focused effort across several dimensions
1 T2 Governance 2 Mapping of T1
3 Resource management 4 Portfolio value
5 Interaction model
Dimensions
▪ Secure approval of the ▪ Secure BOM alignment on ▪ Set up the processes for ▪ Establish the output ▪ Secure BOM and BOM-1
proposed governance for T2 roadmap resource management in tracking process – commitment towards the
T2 ▪ Detail out the implications the T2 set-up templates to track OKRs proposed interaction
▪ Change bank policies and for each masterplan ▪ Create a catalogue of the and review cadence model
define detailed processes initiative – based on the existing resources and ▪ Coordinate with Finance ▪ Detail out the processes
to reflect the new mapping to new T2 respective skill map to finalize the financial of interaction model in the
governance structure ▪ Finalize the tracking tools reporting of each tribe – context of M+
▪ Detail out the SOPs for ▪ Map out current resources for ongoing resource including revenue, cost ▪ Test and refine the
each of the proposed to the new mapping of T1 deployment and allocation interaction model in the
Check-list
councils initiatives (across T1 set- monitoring ▪ Perform the role of “VC context of M+
▪ Detail out the SOPs for up, foundational initiatives, ▪ Coordinate with respective funding” custodian in the ▪ Finalize SOPs for the
each type of decision initiatives moved to main Business Tribes and quarterly reviews, i.e. interaction models,
making bank) Enabling Tribes to ensuring tribes deliver on applicable for future tribes
▪ Secure BOM alignment on forecast upcoming their initial commitment to
▪ Test and refine secure next tranche of
governance the resource mapping and resource requirement
way forward for each budgets
cadence – T2 councils, ▪ Coordinate with Recruiting
Tribe councils initiative war room to source
▪ Finalize the cadence of T2 adequate profiles to meet
governance for each the forecasted
operational tribe requirement
▪ Facilitate T2 council
44
3. OPERATIONALIZE NEW ROLES
45
4. SET UP T2 RECRUITING WAR ROOMS
TCB needs to set up a T2 recruiting war-room to meet sourcing needs for T2 talent (1/2)
46
4. SET UP T2 RECRUITING WAR ROOMS
TCB needs to set up a T2 recruiting war-room to meet sourcing needs for T2 talent (2/2)
47
4. SET UP T2 RECRUITING WAR ROOMS
TCB could Buy, Build or Rent to secure T2 talent
48
4. SET UP T2 RECRUITING WAR ROOMS
BUY: T2 recruiting war room can accelerate hiring of external candidates
Tracking of the recruiting process along with periodic updates to the leadership team
49
4. SET UP T2 RECRUITING WAR ROOMS
RENT: T2 recruiting war room should also explore a few options to ‘rent’ talent
Activating the
Forming Outsourcing an Contracting out gig economy by Open-sourcing
strategic entire function work to an creating discrete, assets to
partnerships organization or paid tasks for encourage certain
(e.g., JVs) individual free-lancers work
Example: Use Example: Instead of Example: Engage Example: Leverage Example: Open up
academic solving for lowest specific, vetted external task platforms to
partnerships to cost, “nearshore” contractors for providers to effectively
access students with to regions with new, in-demand support surge ‘crowdsource’
agile training to high-skill talent and skillsets (e.g., agile capacity, function and
augment scarce cultural compatibility coaches) including contractors usability testing
mission- (e.g., UX designers) and a two-sided gig
critical skillsets economy market for
delivery tasks (e.g.,
agile coaches,
designers, other
squad members)
50
4. SET UP T2 RECRUITING WAR ROOMS
Key roles for new tribes in T2 set-up are fulfilled through top-down appointment
Inform/ Instruct
Select/ appoint
CEO
Providing resource
New Tribe
51
4. SET UP T2 RECRUITING WAR ROOMS
Squad member roles in Tribes should be fulfilled by competitive selection process
Preferred option
Agile squads
Chapter leads (CL)
Easy to execute, no significant pre-work or Easy to execute, no some pre-work required Provides momentum to change culture
dedicated interview time required and mindset
Provides transparency on overlapping functions
Risk of recreating current organization with new Ensures the “right person at right place”
names of roles, status quo mindset and ways of Transparency of staffing process
The most transparent and fair process for
working Risk of recreating current organization with new names employees
of roles, status quo mindset and ways of working
Lack of transparency and fairness of staffing Requires significant dedication of
process resources from HR and leaders
Relatively higher stress for employees
52
4. SET UP T2 RECRUITING WAR ROOMS
Competitive selection process enables employees to voluntarily apply for desired positions
Application/
Resource request Job posting Selection
Assessment
▪ Tribe lead informs iPMO ▪ iPMO communicates ▪ Candidates voluntarily ▪ Chapter Lead (or Tribe
of the resource open positions (JD, skill apply for open positions Lead) interviews
requirement for the requirements…) to based on personal shortlisted candidates
squads – respective resource pool interest and self- and select best suited
– Number of FTEs for – iPMO pool assessment capabilities members for their own
squad/tribe
respective role (i.e. – Full bank ▪ iPMO conducts
Dev engineer, foundational capabilities ▪ Candidates can choose
Customer journey assessment and shortlist their team if they are
expert…) suitable candidates selected by more than
1 units
– Skills required ▪ Strong candidates can be
encouraged to apply – no
forced allocation
53
5. CAPABILITY BUILDING
Role-based learning journeys need to be defined and operationalized for all key T2 roles –
Illustration of a PO learning journey
Product Owner
Learning Journey
Week 0 Week 1 Week 2 Week3 Week 4 Week 5 Week 6 Week7 Week 8 Week 9 Week 10 Week 11
Test your PO self- 360 pulse 360 pulse Test your Program
knowledge assessment survey1 survey 1 knowledge close
Assessments quiz quiz assessment
a
& reflection
54
6. EMPLOYEE ENGAGEMENT
A comprehensive employee engagement plan needs to be created and delivered across all
levels in the organization
BOM T2
immersion
CEO/ BOM-led
Big Boom
Townhalls
Announcement
CEO/ BOM-led
BOM Go-
See-Learn Townhalls
FEB JUN
Agile Immersion
sessions
APR
MAR MAY
55
6. EMPLOYEE ENGAGEMENT
TCB management should consider Go-See-Learn visit
One of the top-10 private banks ▪ Agile transformation of retail customer ▪ Feb 27, Lisbon
worldwide, with significant presence journey (focused on mortgage) ▪ Mar 27, Lisbon
in Portugal
One of the leading banks in Czech ▪ Agile@scale in the HQ delivery ▪ Mar 5, Prague
Republic and a member of the organization with 1,300+ FTEs ▪ Apr 23, Prague
Société Générale group
One of the top-3 largest banks in ▪ Agile@scale transformation in retail ▪ Apr 2, Utrecht
the Netherlands banking with 3,000+ FTEs
The largest bank in the Middle East ▪ Agile@scale, end-to-end technology TBD
region transformation
Other potential
visits in future
56
7. TEST AND REFINE T2 TARGET OPERATING MODEL
Each tribe will work in an iterative model to bring products to the market
57
7. TEST AND REFINE T2 TARGET OPERATING MODEL
The T2 operating model will be institutionalized as TCB’s new way of working
Courage to try
Daily new things
stand-ups Transparency
MVP thinking
Sprint Learning by
(1-2 weeks) doing
Team ownership
Sustainable pace
▪ T2 teams will be integrated, co- ▪ Based on the initial workplan, ▪ Teams will fully internalize T2
located team sharing end-to-end teams will apply an iterative cycle values that inform their day-to-
responsibility for the of planning, implementing, day activities and behaviors,
transformation and collaborating in testing outcomes, learning and making them a more effective,
an open and creative environment improving the way of working efficient and fun team
58
7. TEST AND REFINE T2 TARGET OPERATING MODEL
Tribes will have the T2 mindset internalized as part of their day-to-day activities
59
7. TEST AND REFINE T2 TARGET OPERATING MODEL
Tribes will set up the Tribe Obeya room, a space to jointly celebrate progress and resolve issues
60
8,9 ENTERPRISE ARCHITECTURE AND NEXT GEN IT
TCB needs to assess the current state of IT architecture and readiness for digital delivery in
the context of T2
Scale-up
(~18-24+ months)
Expand
(~6-12+ months)
MVP release
(~4-6 months)
Objective Setup foundational capabilities E2E for teams with Expanding adoption, talent and performance tracking Scale-up to prove global reuse, adoption and cost
foundational reusable APIs, cloud, release to ensure usage and value unlock efficiencies through retiring solutions
Core banking APIs Customer profile APIs Next-best-action APIs
Channels APIs Know your customer (KYC) process APIs Open API external Fintech integration APIs
1. Bank-as-a-Service
Identity and authentication APIs Electronic signature APIs Global account integration APIs
(BaaS) APIs
… … …
Enterprise notification APIs Fraud monitoring APIs Global payments APIs
Setup hybrid cloud platform and environment Intelligent reliability metrics and monitoring Advanced cloud resource and operational mgmt.
Standardize cloud product catalog for teams Setup SRE operating model Standardized ops process (e.g., error budget, etc.)
2. Cloud platform
… … …
Capabilities
Standardize and automate CI/CD pipeline Mirrored standard environments for testing Majority of platforms through standard CI/CD pipeline
3. Release management
Redesign release process with quality gates, controls Advanced release techniques (e.g., blue/green, etc.) Advanced testing (e.., HA, chao testing, etc.)
Setup of API management platform External marketplace API platform Biometrics platform
4. Enterprise Workflow orchestration platform Chat-bot and AI voice platform Peer to peer transaction platform
capabilities … … …
Wave 1 of legacy remediations Wave 2 of legacy remediations Wave 3 of legacy remediations
Capability “Dojos” on Cloud, APIs, DevOps Portfolio planning, roadmap and governance Evolving enterprise process (e.g., funding, etc.)
5. Transformation core
Operating model “MVP” for program, teams Performance and value tracking via OKRs Multi-BU and geo prioritization and planning
team
Hiring of new engineering talent Continued hiring of new engineering talent Vendor partner ecosystem
62
8. ENTERPRISE ARCHITECTURE
A tiered API structure will enable TCB to identify the reusability level of the APIs depending on
its function
New platforms – transfer power direct to business users API catalogue
Current Accounts Credit cards Personal Loans Global API catalogue (contracts, design, semantic data
requirements, etc.) managed centrally by service
design team to accelerate reuse where possible
63
9. NEXT GEN IT CAPABILITIES
An integrated DevOps tool chain covering all steps of the full software development lifecycle
needs to be deployed
Plan is an ongoing activity where Preprod includes the activities Release includes activities
the application business required once the release is ready to schedule, orchestrate, provision
requirements are included with for deployment and deploy software
ongoing application code change into production
2. Create 6. Configure
3. Verify 7. Monitor
64
End of
Document
65
Appendix
66
3. WHAT ARE THE NEW ROLES IN THE T2 SET-UP?
List of roles in Business Tribes (1/2)
Role Summary of responsibilities
Business
Tribe 1.1 Tribe lead ▪ Leads the formulation of the Tribe and Squads missions and goals and implements them through
developing Tribe product vision and managing product lifecycles, shaping the tribe backlog and
representing the tribe in QBR
▪ As volume rolls-in, tribe leads need to be responsible for the P&L
1.2 Solutions ▪ Responsible for the development of the technology solutions and mapping the business requirements to
architect systems/technical requirements to ensure they are in line with the enterprise architectural plan
1.3 Agile Coach ▪ Responsible for efficiency of Tribe processes and coaching squads across the Tribe
▪ Holds regular Agile ceremonies (Product synchronization, sprint retrospectives etc.) and ensures continuous
improvement of the Tribe on Agile maturity
1.4 Chapter Lead ▪ Responsible to develop competencies of chapter members and balances resources within the tribe
▪ Ensures exchange and communication between similar functions across squads
1.5 Design Lead ▪ Responsible for creating and influencing the creation of elegant user experiences that facilitate the
capture of Business Impact
▪ Supervises product design teams across deliverables such as design specification documents, user flows,
wireframes, etc
67
3. WHAT ARE THE NEW ROLES IN THE T2 SET-UP?
List of roles in Business Tribes (2/2)
Role Summary of responsibilities
Business
Tribe 1.6 Product owner ▪ Responsible for releasing a product that meets the customer's needs (in line with Squads mission and
OKR)
▪ Defines and prioritizes requirements for squad members
1.7 Customer ▪ Holds end-to-end responsibility for the development, management, harmonization and implementation of
journey expert business related requirements (corresponding to respective expertise)
(CJE) ▪ Expertise required differs between journeys – may include credit risk process, pricing, product, partnership,
etc.
1.8 UX/CX ▪ Responsible for UX research and UX design of processes, interfaces and customer communication
designer ▪ Improves processes to ultimately increase customer satisfaction, ease of use and accessibility of the
services
1.9 UI Designer ▪ Delivers consistent visual design elements of the product experience, working closely with the UX
designer
▪ Provides guidance on emerging industry trends, and ensures the desired experience is delivered within
the visual framework
68
ROLES AND REPORTING LINES OF T2 PEOPLE
Tribe Lead
Role Description
Responsible for managing a customer segment/ channel/ journey to achieve the Tribe's business goals. Responsible for the Tribe's key performance indicators depending on
its tasks (such as P&L, NPS, market share, systems availability - uptime, number of incidents etc.)
Solution Architect
Role Description
The Solution Architect owns the technical, architectural decisions for the team – valuing simplicity and not afraid to challenge technical constraints and procedures to achieve agile design. The Solution
Architect works closely with the rest of the team to (a) guide delivery in line with timelines and (b) to create a modular & scalable solution that addresses future architectural changes and designs. This
person drives towards best in-class engineering practices (e.g. test driven development, continuous integration, and automated deployment). A good solution architect is keen to get his/her hands dirty,
actively helping the team to solve the biggest problems. This individual is an executor as well as the visionary force behind the technical solution.
70
ROLES AND REPORTING LINES OF T2 PEOPLE
Agile Coach
Role Description
A member of the Tribe responsible for efficiency of Tribe processes, keeping up continuous improvement momentum at the Tribe level, and coaching squads across the Tribe
71
ROLES AND REPORTING LINES OF T2 PEOPLE
Chapter Lead
Role Description
The Chapter Lead will serve as a guide in the area where he/she is the person with highest level of knowledge in the Tribe, increasing the capabilities of teams. Responsible for looking for transversal
consistency of the knowledge of the Chapter, sharing best practices and common challenges in his/her cell and others
Design Lead
Role Description
The Design Lead is responsible for three core activities: experience design, visual design and research. The Design Lead is able to define requirements for a coherent and winning user experience,
taking into account product and company strategy, brand-fit and data from other channels, creating assets where needed (from task flows to high-fidelity artifacts representing system behavior e.g.,
wireframes, prototypes, etc.) and managing the user research plan and execution, e.g. conducting panels, surveys, interviews, and playing back the results to the team
Product Owner
Role Description
A member of the Squad responsible for releasing a product that meets the customer's needs to achieve the squad goals. Responsible for defining and prioritizing requirements (stories) in the Squad
Backlog and also accepts requirements (stories) as completed.
Role Description
Customer journey expert is a squad member responsible for the new customer journey. The journey expert will take lead in understanding the existing process, detailing out user stories and
acceptance criteria, gathering customer input and identifying a smooth transition to the new journey
UX/ CX Designer
Role Description
The User Experience Designer is responsible for ensuring a coherent product experience across the Customers’ journey. Working in tandem with the Tribe Lead to understand business priorities, the
UX designer works to marry these with Customer pain points to craft a coherent and delightful customer experience and shaping the product strategy. Often working alongside, or doubling as, as UI
designer and/or Design Researcher(s), the UX designer is an important input to user tests – defining what should be tested, in what priorities and using which tools (e.g. wireframes to storyboards) to
elicit the right sort of feedback to help the team.
UI Designer
Role Description
The User Interface designer is responsible for delivering consistent visual design elements of the product experience, working closely with (and often doubling as) the UX design function. While
focused on visual elements, including feeding back best practices and new / emerging industry trends, the UI designer must ensure the desired experience is delivered within the visual framework
they create. Often this role is also responsible for ensuring alignment with a wider organizational ‘design system’ and re-use of assets to ensure Brand consistency etc. The UI designer is also
integral to the research and user testing work, often creating many of the assets and being involved with preparing and conducting user interviews and other types of testing.
77
List of roles in Data and Analytics Tribe
Role Summary of responsibilities
▪ Define vision, target opportunities enabled by analytics and enterprise data & analytics strategy
1.1 Data and
Analytics Tribe
▪ Provide guidance to the data tribe on prioritization and requirements as needed
Lead ▪ Deploy tribe members into the squad, bringing in relevant expertise to support squad goals
Data and ▪ Manage recruitment and trainings of resources on emerging data knowledge, trends, and expertise
Analytics
Tribe ▪ Analyze and monitor relevant customer journeys, customer information, costs, benefits and risks
1.2 Data analyst for customers, within a tribe/squad and provides actionable information and data-driven insights
to the squad
▪ Tackle and solve complex business issues using large data volumes, develop advanced analytics
1.3 Data scientist (machine learning) models, including preparing and combining data and creating (interactive)
visualizations
Role Description
The Data & Analytics Tribe Lead owns the data, governance and analytics for the T2 set-up. He/she will be the executor and the visionary force behind the analytics solutions, data governance, data standards and advanced analytics
innovations. Responsible for looking for transversal consistency of the knowledge of the Tribe, sharing best practices and common challenges across the tribe
79
ROLES AND REPORTING LINES OF T2 PEOPLE
Data Analyst
Role Description
The Data Analyst will work as a key enabler to secure realization of business value from analytics, data and models in the products. They have a strong customer focus, a strong commercial mindset and innate curiosity. They
will work with multiple advanced analytics tools initiatives to analyze, execute and follow up initiatives from idea to industrialization with both analysis of model output and designing of new ways of working.
▪ Implement tools (e.g., Power BI or web-analysis dashboards) that Individual Skills ▪ Align assignments with the strategic goals of the business.
help data consumers to extract, analyze, and visualize data faster and ▪ The ability to analyse, model and interpret data
better through data pipelines ▪ A methodical and logical approach
▪ The ability to plan work and meet deadlines
80
ROLES AND REPORTING LINES OF T2 PEOPLE
Data Scientist
Role Description
The Data Scientist applies strong expertise in artificial intelligence through use of machine learning, data mining, and information retrieval to design, prototype and build next generation advanced analytics
engines and services. The data scientist collaborates with business partners to define the technical problem statement and hypothesis to test; develops efficient and accurate analytical models that mimic
business decisions and incorporates them into analytical data products or tools with the support of a cross-functional team.
Data Engineer
Role Description
Data Engineer works closely with a multidisciplinary Agile team to build high quality data pipelines driving analytic solutions. These solutions will generate insights from connected data, enabling the bank to advance the data-driven
decision-making capabilities. This role requires deep understanding of data architecture, data engineering, data analysis, reporting, and a basic understanding of data science techniques and workflows. The ideal candidate is a
skilled data / software engineer with experience of creating data products supporting analytic solutions. He/she should be an Agile learner, possess strong problem-solving skills, work as part of a technical, cross functional analytics
team, and want to solve complex data problems and deliver the insights to enable analytics strategy.
▪ Demonstrated strong number sense, intellectually curious and willing to adjust position based on additional
Mindset & Behaviors information
▪ Strong work ethic; ability to work at an abstract level and gain consensus
82
ROLES AND REPORTING LINES OF T2 PEOPLE
Data Architect
Role Description
The Data Architect drives the discovery, design, and execution of a wide variety of analytical technology solutions. The Data Architect will provide leadership, strategic decision-making, and
guidance within technical disciplines, responding to disruptive analytical technologies and solving unique and complex problems. S/he researches, architects, and defines Advanced Analytics
& Business Intelligence capabilities and strategies for information delivery and data exploration to support business function needs and goals.
▪ Lead teams to work together effectively. Encourage knowledge sharing and openness.
▪ Make decisions in a proactive, timely manner.
Individual Skills
▪ Continuously challenge and improve current processes and solutions.
▪ Maintain an up-to-date level of knowledge in security and continuously develop one’s skills. Exuding
passion and energy to motivate chapter members
85
List of roles in IT Tribe
Role Summary of responsibilities
▪ Design the overall technological architecture of the systems with the help of the team
2.1 IT Tribe lead
▪ Guide IT on technology strategy related to continuous integration and automated deployment
▪ Deploy tribe members into the squad, bringing in relevant expertise to support squad goals
IT Tribe
▪ Manage recruitment and trainings of resources on emerging IT knowledge, trends, and expertise
2.2
Solutions ▪ Responsible for the development of the technology solutions and mapping the business requirements
architect to systems/technical requirements to ensure they are in line with the enterprise architectural plan
▪ Enhance experience of all business tribes by implementing fully automated CI/CD pipeline
2.3 DevOps expert
▪ Optimize software development to deployment process to reduce TAT
Front-end ▪ Implement visual elements that users see and interact with in a web/application
2.4
developers ▪ Determine the structure and design of web pages, balance between functional and aesthetic design
▪ Compile and analyze data, processes, and codes to troubleshoot problems and identify areas
for improvement.
Back-end
2.5
developers
▪ Collaborate with the front-end developers and other team members to establish objectives and design
more functional, cohesive codes to enhance UX
▪ Build APIs to integrate with other systems
▪ Develop test cases and performance of complex functional testing
2.6 Test engineer
▪ Develop load testing scripts and performance of load testing
Digital project ▪ Manage technical priorities (non-functional) across tribes
2.7
manager ▪ Collaborate with OnT to ensure timelines and quality are met
86
ROLES AND REPORTING LINES OF T2 PEOPLE
IT Tribe Lead
Role Description
The IT Tribe Lead owns the overall IT development capabilities for the T2. He/she is an executor and the visionary force behind the technical solution. He/she values simplicity and is unafraid to challenge
technical constraints and procedures to achieve an agile design. He/she works closely with all the Business Tribes to create a modular, scalable solution that addresses/incorporates future architectural changes
and designs. He/she will drive the teams engineering practices in test driven development, continuous integration, and automated deployment. He/she is a hands-on team member who actively coaches the
team to solve complex problems.
Solution Architect
Role Description
The Solution Architect owns the technical, architectural decisions for the team – valuing simplicity and not afraid to challenge technical constraints and procedures to achieve agile design. The Solution
Architect works closely with the rest of the team to (a) guide delivery in line with timelines and (b) to create a modular & scalable solution that addresses future architectural changes and designs. This
person drives towards best in-class engineering practices (e.g. test driven development, continuous integration, and automated deployment). A good soluiton architect is keen to get their hands dirty,
actively helping the team to solve the biggest problems. This individual is an executor as well as the visionary force behind the technical solution.
DevOps Engineer
Role Description
The DevOps Engineer helps increase speed of delivery, improve quality/security of code, and optimize processes for development team. The DevOps Engineer is responsible for identifying
the bottlenecks of various development and delivery processes, working with team members to improve them, and improving the overall experience of developers. They are responsible for
infrastructure-as-code deployment tooling and supporting services on multiple cloud provides along with metrics and login
▪ Passionate about technology and excited about the impact of emerging / disruptive technologies
▪ Wants to unleash inner self-starter and work in an environment that fosters
Mindset & entrepreneurial minds
Behaviors ▪ Believes in culture of brutal transparency and trust
▪ Open to learning new ideas outside scope or knowledge skillset
▪ Aspirational to become full stack or deep expert
91
ROLES AND REPORTING LINES OF T2 PEOPLE
Test Engineer
Role Description
Tester in an agile team is responsible for more than just testing the software. His or her role is to provide effective communication between team members, and Product owner. He or she has
full responsibility and authority to decide if a feature developed by the team is completed or not. He or she needs to quickly gain intimate knowledge of the product to ensure that his or her
feedback to the team is aligned with the product vision. He or she also needs solid technical skills and be fully dedicated to “automate everything” principle.
Responsibilities Key Skills
▪ Responsible for the environment of QA together with
Test Automation ▪ Bachelors degree in Computer Science, System Engineering or similar
▪ Responsible for implementation and execution of end- ▪ Experience in multiple languages of development and systems (Java, C, C++ etc)
to-end or integration tests ▪ Experience in development of application with Database (DB2, MySQL, etc.)
Domain Expertise
▪ Coordinator for tests with legacy systems ▪ Experience in test-oriented development (TDD or BDD)
▪ Validation of functionalities in sprints, both manually ▪ Experience with writing and automating test cases
and automatically
▪ Knowledge of programming language of automatic tests : Jasmine, Protractor etc.
▪ Error-incidence report to front-end and back-end
developers Agile/Digital ▪ Strong understanding of Agile methodologies
▪ Perform acceptance test of user stories on a day-to- Experience ▪ Experience as a developer on an agile team preferred
day basis
▪ Perform end-to-end tests in relation to larger releases ▪ Strong communication skills with ability to communicate complex technical concepts and align
with external stakeholders organization on decisions
▪ Drive the squad’s test strategy and test efforts, e.g. ▪ Sound problem-solving skills with the ability to quickly process complex information and present
taking initiative to automate where possible and coaching Individual Skills it clearly and simply
others ▪ Utilizes team collaboration to create innovative solutions efficiently
▪ Own the process during test periods where
functionality is tested across several squads and
departments ▪ Ownership mindset – track-record of getting things fixed not simply discovered
▪ Be an active participant in grooming and planning, to ▪ Passionate about technology and excited about the impact of emerging/disruptive technologies
ensure that acceptance criteria are testable Mindset & ▪ Wants to unleash inner self-starter and work in an environment that fosters entrepreneurial minds
▪ Sit together with designers, customer journey experts and Behaviors
Product Owner while user stories are developed, bringing ▪ Believes in culture of brutal transparency and trust
input and helping with the testing angle
93
ROLES AND REPORTING LINES OF T2 PEOPLE
Mindset &
▪ Belief in a non-hierarchical culture of interaction, transparency and trust in squads
Behaviors ▪ Openness to new ideas and desire to develop them together
94