Digital Transformation engagements are definitely the most complex projects you can work on. And even though we stated many times that it’s possible to minimize the risks through tools for automated analysis and strong skills, it’s still important to keep in mind that collaboration is the key to succeed. Usually the success of a digital transformation project derives from the collaboration of some actors: - Technology vendors - Consulting companies - Customer Let’s discuss the complexity and the methodology for teaming properly and successfully. Presenter: Andrea Battaglia, Technical Partner Development Manager EMEA

1. Address technical risks when
implementing workload
modernization use cases
Andrea Battaglia
Technical Partner Development Manager EMEA
Middleware Evangelist
andrea.battaglia@redhat.com

2. 2
Accelerate your journey to Kubernetes
with the Konveyor Community
A community of people passionate
about helping others modernize and
migrate their applications to the hybrid
cloud by building tools and best
practices on how to break down
monoliths, adopt containers, and
embrace Kubernetes.
www.konveyor.io

3. Watch The Presentation
https://youtu.be/-BmYmay0ejA

4. 4
What we’ll
discuss
today...
▸ Self introduction
▸ Quick Recap
▸ Teaming

5. 5
WHO AM I

6. 6
ABOUT ME
Name: Andrea Battaglia
Email: andrea.battaglia@redhat.com
Base: Italy (Far south)
Role: EMEA Technical Partner Development
Manager - DX and Edge Computing
Experience: Red Hat Technical Head of DX
EMEA
Projects: https://qiot-project.github.io/
6

7. 7
QUICK RECAP

8. 8
8
DISCOVER DESIGN PLAN DEPLOY
METHODOLOGY - MODULES
Prove
Assessment
Pre-sales Consulting
Onboarding
Process
Scale
Discovery
Session
Pilot
1) Analyze / assess the full portfolio
2) Implement the MVP
3) Plan the onboarding (create a blueprint)
4) Iterate over application increments in the “Expand” phase - no big
bang!
Pro: Full view of the whole portfolio,
risks identified up front, planning
decisions founded on complete view.
Con: Long preparation before first
iteration (“waterfall-ish”)

9. 9
TEAMING

10. 10
Common delivery model
Project team structure & collaboration strategy
Knowledge base
(solutions, guides, rules)
A C
B
D E F
Applications
MIGRATION
TEAM
Client / Red Hat / Partners
Architect, developers,
specialists, project manager
● One-person armies
(Dev/Ops/Archi/PM)
● Works for small projects only
● Does not scale with the number of
apps
● Bottleneck on knowledge and expertise

11. 11
Factory delivery model
Project team structure & collaboration strategy
Knowledge base
(solutions, guides, rules)
Challenge
backlog
A C
B
D E F
Applications
MIGRATION
TEAM(S)
Client / Factory
partners
Developer team(s)
STEERING
TEAM
Client / Red Hat /
Partners
Project managers,
technical leads &
specialists

12. 12
Roles and Responsibilities
Technical lead / architect
Drive “DESIGN” phase (Assess, Proof, Pilot, Plan), govern and ensures quality in
“DEPLOY”.
STEERING
TEAM
MIGRATION
TEAMS
Technical specialist / Subject matter expert
Support “DESIGN” phase (Proof, Pilot), catalyze/scale/support the “DEPLOY” delivery.
Project manager
Globally accountable for planning, communication, knowledge and risk management.
Application developer
High throughput application transformation in “DEPLOY” phase.

13. 13
Roles and Responsibilities
Team structure example
STEERING
TEAM
MIGRATION
TEAMS
Application developer
(Customer teams, Application
suppliers, Factory partners)
● Structure and shape knowledge sharing in a central platform
● Define outcomes and contributions from software vendors (format of changes,
updated software packaging), support migration estimations
● Quality review and enforcement (acceptance of deliverables, changes
documentation), review of estimations
● Brief technical enablement and technical alignment workshops
● Overall migration project steering
● Multi-project management (prioritization, status, tracking)
● Coordinate software provider workshops
● Define support structure and communication
● Project-level technical support
● Support “DESIGN” phase (Proof, Pilot)
● Catalyze/scale/support the “DEPLOY” delivery.
Technical lead / Architect
Subject matter expert
Project manager
● Jointly work with architects and specialists in analyze and prove & pilot phase
● Perform application transformation at scale.
1-2
Customer
1-2 Partner
2-3
Customer
1 Partner
1 Customer
1 Partner

14. 14
Factory model
The big picture
Red Hat Consulting
and Partners
Application suppliers /
vendors
Customer
● Different projects
● Requirements
● Roadmap and plans
● Change management
● Technical skills
● Test
● Application
Development
● Updated
deliverables
● Architecture consulting
● Product technology skills
● Project & Program
Management
AMM Factory

15. 15
Communication channels
Clarify and communicate upfront
▸ Backlog, change, and issue management
▸ Support structure (mailing lists / contact persons / on-call duty)
▸ Steering and migration teams

16. Join the Konveyor Community
www.konveyor.io
Chat with us on Slack

17. Thank you!
17
Andrea Battaglia
Technical Partner Development Manager EMEA
Middleware Evangelist
andrea.battaglia@redhat.com