Sesta puntata del MuleSoft Meetup di Milano - 4 Novembre 2021
Questa volta sarà un meetup speciale, nel giorno del Summit Italia. Parleremo di Training con Elena Ciscato, Training Advisor di MuleSoft per l'Italia, e di quali sono le opzioni e learning paths disponibili. Ed insieme a Gonzalo affronteremo il problema di come creare un modello di supporto per Mulesoft all'interno della nostra organizzazione.
Sito dell'evento - https://meetups.mulesoft.com/events/details/mulesoft-milano-presents-mulesoft-milano-meetup-6/
Milano Meetup #6 - Training & Certification and Internal Support Models
1. How to create your Internal Support Model
Gonzalo Marcos - Senior Technical Architect
MILANO MuleSoft Meetup Group
Training and Certification
Elena Ciscato - Senior Training Field Advisor
4th November 2021
29. Plan for success Establish the foundation Build to scale Measure impact
Business outcomes path
Anypoint Platform path
Projects path
Center for Enablement “C4E” path
Internal support path
Training path
6 paths to focus on
Org
enablement
Technology
delivery
Business
outcomes
30. Plan for success Establish the foundation Build to scale Measure impact
Agree on business outcomes
and KPIs
Develop the overall success plan
Monitor and manage Refresh success plan Measure business outcomes
Define Anypoint platform
vision and roadmap
Design Anypoint platform
architecture and
implementation plan
Deploy Anypoint Platform Scale and refine
Anypoint Platform
Measure Anypoint platform KPIs
Prioritize IT projects
Staff and onboard delivery teams
Define solution architecture
Execute projects
Onboard additional
delivery teams
Launch additional projects
Measure project KPIs
Assess integration capabilities
Establish the C4E
Build and publish foundational
assets
Evangelize
Drive consumption Measure C4E KPIs
Determine the support
operating model
Staff, train and launch team
Publish support guidance and self-
serve materials
Support Anypoint Platform Measure support KPIs
Train the initial team(s) Develop the broader training plan
Launch experiential learning
opportunities
Train additional teams Conduct assessment
Integrated Blueprint
30
Org
enablement
Technology
delivery
Business
outcomes
32. Internal Support Playbook
32
Plan for success Establish the foundation Build to scale Measure impact
Determine the Support
Operating Model
Staff, Train and
Launch Team
Publish support guidance and
self-serve materials
Support
Anypoint Platform
Measure the Impact
of Support
● Set up Introduction Session with the
Customer
● Identify Internal Support Model
● Agree on Roles Required and
Training Required by Role
● Align on the Issue Resolution and
Escalation Process
● Establish Support KPIs and
Measurement Plan
● Identify the Team Members
● Appoint Support Contacts
● Train the Team Members
● Onboard and Launch the Support
Team
● Build and Publish Guidelines to
Interact with Internal Support Team
● Build and Publish Process Flows for
Escalation Process
● Build and Publish Additional
Documentation
● Ensure Broad Access to External
MuleSoft Resources
● Monitor the Anypoint Platform
● Address First Level Support Issues
● Follow the Defined Internal
Escalation Process Flows
● Escalate Issues to MuleSoft as
Appropriate
● Review Recent Deployments and
Fix Supportability Gaps
● Build a Mutual Feedback Loop
between Support and Development
● Review and Modify Support KPIs
● Measure Support KPIs
● Develop Support Improvement
Recommendations
34. Internal Support Playbook
1. Identify Internal Support model: Roles, responsibilities and processes
2. Agree on Roles required and training path by role
3. Align on the issue Resolution and Escalation Process
4. Establish Support KPIs and Measurement Plan
34
Identify Roles,
Responsibilities
and Processes
Agree on Roles
required and
Training Paths
by Role
Align on the
Issue
Resolution and
Escalation
Processes
Establish Support
KPIs and
Measurement
Plan
35. Typical Support Model Overview
35
Level 1:
Help Desk
Level 2:
Organisation’s MuleSoft Support Team
Level 3:
API Dev Team
Level 4:
MuleSoft
Feedback on the
resolution is provided
at all levels.
38. Roles
38
Role Responsibilities Skills
Operations Analyst ● L1
● Network and Infrastructure support
● Inputs for NFRs
● Maintenance of environments
● Oversee knowledge transfer (from dev to
operations)
● Deploy and configure APIs in production
● Configure monitoring and alerting
● Review, triage, and respond to alerts,
notifications, and issues reported by end users
● Assign the issue to a proper team if required (L2,
core system, UI, MuleSoft Support, etc.)
● Maintain the knowledge base (e.g. wiki)
● Educate end users
● MuleSoft Operations
● Anypoint Platform Architecture
● Understanding of business
● Alerting and Monitoring
● Logs and mule messages
● Development practices and methodology
● Java profiling (e.g heap dump, thread dump,
etc.)
● Operating System administrator
39. Roles
39
Role Responsibilities Skills
Support Engineer ● L2
● Provide the assistance to Operations Analyst
with the more critical issues or the issues that are
beyond the capabilities of Operations Analyst to
investigate
● Provide the resolution or assign the issue to
development team
● Help to make a decision if the issue is platform
related and official MuleSoft Support ticket must
be raised
● All the skills of Operations Analyst
● MuleSoft Fundamentals
● Whitebox understanding of APIs
Developer ● L3
● Provide the assistance to Support Engineer with
the more critical issues or the issues that are
beyond the capabilities of Support Engineer to
investigate
● Manage the issues within the sprint - plan for
fixes and go live
● Provide the assistance to MuleSoft Support with
issues raised
● All the skills of Operations Analyst and
Support Engineer
● MuleSoft Professional Developer
● Deep understanding of APIs deployed in
production (usually a developer responsible
for delivery of specific APIs)
40. Roles
40
Role Responsibilities Skills
Support Lead ● Team management (L1 team, partially L2)
● Helps shaping KPIs together with Platform
Support
● Enforces measurement of KPIs
● Incident prioritisation
● Manages escalations from business
● Avoid auto-closing issues due to long response
time or not providing response at all
● Communication and leadership
● Understanding of business, business critical
applications, and priorities
Platform Support ● C4E Team
● Provides technical support and advice to project
and product teams for applications in production
● Comments on exception handling and logging
practices
● Stay up to date with the platform - follow the
release notes, MuleSoft Summits, etc. to get
visibility on the new features and capabilities.
● Plan for new relevant features to be established
within the organisation (activity includes the
enablement of the teams)
● Helps shaping KPIs, collects and presents KPIs
to C4E lead and/or business
● All the skills of Operations Analyst, Support
Engineer, and Support Lead (could be the
same person)
● Cross projects enabler
● Deep understanding of internal organisation
processes
● Deep understanding of MuleSoft best
practices established within org
42. Roles
42
Role Responsibilities Skills Training Path
Operations
Analyst
● L1
● Network and Infrastructure support
● Inputs for NFRs
● Maintenance of environments
● Oversee knowledge transfer (from
dev to operations)
● Deploy and configure APIs in
production
● Configure monitoring and alerting
● Review, triage, and respond to
alerts, notifications, and issues
reported by end users
● Assign the issue to a proper team
if required (L2, core system, UI,
MuleSoft Support, etc.)
● Maintain the knowledge base (e.g.
wiki)
● Educate end users
● MuleSoft Operations
● Anypoint Platform Architecture
● Understanding of business
● Alerting and Monitoring
● Logs and mule messages
● Development practices and
methodology
● Java profiling (e.g heap dump,
thread dump, etc.)
● Operating System administrator
● Getting Started with
AnyPoint Platform
● AnyPoint Platform
Operations - Cloudhub
43. Roles
43
Role Responsibilities Skills Training Path
Support
Engineer
● L2
● Provide the assistance to Operations
Analyst with the more critical issues or the
issues that are beyond the capabilities of
Operations Analyst to investigate
● Provide the resolution or assign the issue
to development team
● Help to make a decision if the issue is
platform related and official MuleSoft
Support ticket must be raised
● All the skills of Operations
Analyst
● MuleSoft Fundamentals
● Whitebox understanding of
APIs
● Anypoint Platform Development:
Fundamentals
● Anypoint Platform Operations -
Cloudhub
● Anypoint Platform Development:
Production-Ready Development
Practices
Developer ● L3
● Provide the assistance to Support Engineer
with the more critical issues or the issues
that are beyond the capabilities of Support
Engineer to investigate
● Manage the issues within the sprint - plan
for fixes and go live
● Provide the assistance to MuleSoft Support
with issues raised
● All the skills of Operations
Analyst and Support
Engineer
● MuleSoft Professional
Developer
● Deep understanding of APIs
deployed in production
(usually a developer
responsible for delivery of
specific APIs)
● Anypoint Platform Development:
Fundamentals
● Anypoint Platform Operations -
Cloudhub
● Anypoint Platform Operations - API
Management
● Anypoint Platform Development:
Production-Ready Development
Practices
44. Roles
44
Role Responsibilities Skills Training Path
Support
Lead
● Team management (L1 team, partially L2)
● Helps shaping KPIs together with Platform
Support
● Enforces measurement of KPIs
● Incident prioritisation
● Manages escalations from business
● Avoid auto-closing issues due to long response
time or not providing response at all
● Communication and
leadership
● Understanding of
business, business critical
applications, and priorities
● Getting started with Anypoint
Platform
● Anypoint Platform Architecture:
Application Networks
Platform
Support
● C4E Team
● Provides technical support and advice to project
and product teams for applications in production
● Comments on exception handling and logging
practices
● Stay up to date with the platform - follow the
release notes, MuleSoft Summits, etc. to get
visibility on the new features and capabilities.
● Plan for new relevant features to be established
within the organisation (activity includes the
enablement of the teams)
● Helps shaping KPIs, collects and presents KPIs
to C4E lead and/or business
● All the skills of Operations
Analyst, Support Engineer,
and Support Lead (could
be the same person)
● Cross projects enabler
● Deep understanding of
internal organisation
processes
● Deep understanding of
MuleSoft best practices
established within org
● Anypoint Platform Development:
Fundamentals
● Anypoint Platform Operations -
Cloudhub
● Anypoint Platform Operations -
API Management
● Anypoint Platform Architecture:
Application Networks
● Anypoint Platform Architecture:
Integration Solutions
● Anypoint Platform Development:
Production-Ready Development
Practices
46. Align on the Issue Resolution and Escalation
Process
- Design the processes needed to act upon issues that cover:
- Issue Triage
- Case Assignment
- Resolution
- Defects
- Escalation
- The processes should support
- Platform Production Availability
- Development
- API/Application
46
48. Support Process – best practices
48
Recommended operational practice when
troubleshooting Production and Non-
Production incidents.
Please refer to
https://support.mulesoft.com/s/article/M
uleSoft-Recommended-Support-Process
50. Support KPIs and Measurement Plan
• Identify and define a set of measurable support KPIs. The KPIs need to be
measured at specific intervals and reported to the stakeholders.
• Plan to measure the following dimensions:
– Internal
• Deployments Support/Change Management (non-prod)
• Production Support (Applications/APIs)
• Platform Support (patch, upgrade, etc)
• Developer Support
– External
• Contacts with MuleSoft Support/Customer Success → tickets/escalations, QBRs…
• Contacts with External Resources (forums, blogs, etc)
50
51. Support KPIs and Measurement Plan
• Recommended minimum
– Initial response time per severity
– % of escalations to MuleSoft Support
– % of tickets accepted (tickets that required fix to be provided by MuleSoft) by
MuleSoft Support per support level
– Reason for support request (knowledge gap, missing documentation, environment
issue, etc.)
– Resolution time
– % of solved issues per support level
51
53. Key MuleSoft resources that your developers
should know
• MuleSoft’s Knowledge Base (https://support.mulesoft.com/s/knowledge) - The knowledge base is a rich resource to
identify various needs based on the category and type of product. There is a search functionality with auto-complete to
help you find the information you need faster.
• MuleSoft Forums (https://forums.mulesoft.com/) - The forums are a great way to source responses to specific or
generic questions, or alternatively review responses to similar queries that you may have had previously.
• MuleSoft Blogs (http://blogs.mulesoft.com/) - Our experts and engineers spend a significant amount of time enabling
our community with blogs to guide the implementation of broadly used resources and use cases
• MuleSoft’s Recommended Support Process https://support.mulesoft.com/s/article/MuleSoft-Recommended-
Support-Process - A basic operational practice that MuleSoft recommends when troubleshooting an incident on the
Anypoint platform.
• Performance Tuning Guidelines (https://docs.mulesoft.com/mule-user-guide/v/3.8/tuning-performance) - A guide that
describes recommend practices to tune the performance of apps on the Anypoint platform
53