Download the associated webinar: https://www.cprime.com/resource/webinars/how-to-implement-an-atlassian-jira-align-governance-framework/ Robust governance of your Atlassian Jira Align investment is critical to ensure it can support the overall strategic outcome of your organization. Failing to continuously monitor the business value, technical value, and process value of Jira Align will result in a failure to provide a holistic solution for the market from your federated ecosystem. In this webinar, Jesse Pearlman, Business Agility Coach at Cprime, will guide you through best practices for Jira Align governance to achieve better visibility and optimal results. You will learn: – How to enable your people, processes and systems to scale and align to governance – How to provide autonomy while maintaining the guardrails that govern the use of Jira Align – How to ensure visible change management that promotes collaboration – What are the main governance features of Jira Align

1. ©2020 Cprime, Inc. All rights reserved and no copying without express written permission. WWW.CPRIME.COM | 877.753.2760

2. How to Implement an Atlassian
Jira Align Governance Framework

3. OUR SPEAKER
JESSE PEARLMAN, Business Agility Coach, Cprime
• Helps organizations achieve true business agility by aiding them in
applying Visibility into processes, practices, and market, to better
understand their current state of Predictability and Responsiveness
• An agilist and building high performing teams since the mid 80’s
• Learned the true elements of Servant/Leadership in the Marines
• Has facilitated the Agile success of hundreds of companies across
the globe from the podiums of Rally and AgileCraft (now Jira Align)

4. AGENDA
01 THE PLATFORM TEAM
02 INTAKE AND TRIAGE
03 KEEP THE CONVERSATION GOING/Q&A

5. THE PLATFORM TEAM

6. THE PLATFORM TEAM – AKA GOVERNING BODY
6
The formation of the Platform Team, aka Governing Body, of Jira Align is best when formed
from/around these three elements:
1. Business Voice
2. Tool Administration
3. Framework and Process

7. THE PLATFORM TEAM – BUSINESS VALUE
7
• This person is the Voice of ultimate value for the platform to deliver
• This person (or persons) should be/represent the highest level of the Enterprise being
modeled
• Not always the purchaser
- Has influence/authority over renewal
• Leads platform value outcomes for Enterprise

8. THE PLATFORM TEAM – TOOL ADMINISTRATION
8
The Body of technical practice aligned to keep the platform and all data connectors
performant to ensure the best Sense and Respond for the Enterprise. To include:
• Security
• User Management
• Organizational Modeling
• Technical Knowledge of platform configurations
- Gain and then radiate technical best practices to keep teams and sub admins healthy
• Can be sourced from larger Tool Admin Team
- Should have two backups one from each; Business, Framework and Process
• If Data connectors are in place
- Either tools team admin has tier 2 skills and experience with those connectors
or JA Admin has contact and escalation processes in place with appropriate connector
admins

9. THE PLATFORM TEAM – FRAMEWORK AND PROCESS
9
The Body of Coaches and Practitioners that support, train, and evolve the Framework,
Principles, and Practices aligned to deliver on the Enterprises highest Strategies.
To include:
• Guilds
• Communities of Practice
• Meet Ups
• Retrospectives
• Measurable Data to consistently seek the best Enterprise Predictable Rate

10. INTAKE & TRIAGE

11. INTAKE AND TRIAGE
11
As the user base is trained up and deployed on the platform the Governing Body will start to
collect input from all levels of the Enterprise being modeled.
All of these start off as questions that need to be handled.
As skill and experience increases, oral tradition, checklists, and training will diminish the
volume to a normalized throughput.
These questions will come in through the three elements and are either answered by the
Platform Team or moved to one of the three channels for resolution with Jira Align
1. Questions
2. Defects
3. Enhancements

12. INTAKE AND TRIAGE
12
User Base reports Questions, Issues, and Concerns (QICs)
Team Level Admins and Practitioners attempt to resolve
QICs not handled by Team level passed to Governing Body Representative
Governing Body Reps triage and resolve or bring to Atlassian’s Jira Align rep
Jira Align Rep helps Identify Questions, Defects, Enhancements
QDEs aligned to Success, Support, or Product
Status communicated from Atlassian’s Jira Align
GB Escalates with Atlassian when SLAs exceeded
Atlassian Communicates resolutions
Governing Body Updates processes & docs
Feedback cycles repeat
Success
For All

13. INTAKE AND TRIAGE – BUSINESS VALUES
13
Questions regarding why data is being represented properly, how reports are being calculated,
Jira Align recommendations on:
• Lean Portfolio Management
• Value Engineering
• Intake and Value Stream Mapping
Also being reported are failures in current functionality
All questions and reported incidents that cannot be resolved at the user/team level need to be
reported to the Governing Body for Triage

14. INTAKE AND TRIAGE – BUSINESS VALUES KEY AREAS
14
ADMIN BUSINESS FRAMEWORK AND PROCESS
Key Areas Needs Value/Concern Value/Concern
Lean Portfolio
Management
Configurations based on
evolution of processes
Predictability and Visibility into
Portfolio Epics Approvals and
Lifecycle
Guardrails and Growth
Value Engineering
Configurations based on
evolution of processes
Enhanced value tracking at the
Portfolio for greater Pivot or
Persevere decisioning
Guardrails and Growth
Intake and Value Stream
Mapping
Configurations based on
evolution of processes
True planning and traceability for
Funding, Execution, and Capacity
Guardrails and Growth
Strategic Planning
Configurations based on
evolution of processes
Clear Strategic Planning and
Insight to Cost, Capacity, and
Values
Guardrails and Growth

15. INTAKE AND TRIAGE – TOOL ADMINISTRATION
15
Questions regarding users, security, roles and permissions, configuration, organizational
management, integrations will come to the Admins; as well as:
• Data loss
• Performance
• Loss of Access
Also being reported are failures in current functionality
All questions and reported incidents that cannot be resolved at the
user/team level need to be reported to the Governing Body for Triage

16. INTAKE AND TRIAGE – TOOL ADMINISTRATION KEY AREAS
16
ADMIN BUSINESS FRAMEWORK AND PROCESS
Key Areas Needs Value/Concern Value/Concern
Connectors Tier 2 support
Sense and respond
Data integrity
Progress against plan
and best practices
User Management
Add and remove
Import or manual
Roles and Team assigning
Cost effectiveness and adoption
Organizational model and
team configuration
Roles and Permission
Security and Data Access
Module and Report Access
Licensing costs
Security regulations
Process and practice alignment
to users' roles and access
Platform Configuration
Alignment of org & data
Portfolio – Team configurations
Platform Terminology
Data integrity
Organizational alignment
to Enterprise delivery
Aligns and supports framework
and process
Accurately reflects operational and
delivery streams and lexicon
Organizational Model
Security and Access
Enterprise Model –
BU>LOBs>Portfolios>Programs
Regions, Cost Centers, Cities
Products, Customers
Enterprise alignment of
Org>People>Work
Regions>Products>Customers
Accurate representation of
Enterprise delivery as aligned
to Mission Vision Values

17. INTAKE AND TRIAGE – FRAMEWORK AND PROCESS
17
Questions regarding functionality, reporting, access, team and organization configuration, and
practice alignment; key elements of which are :
• Planning
• Retrospectives
• Assessments
Also being reported are failures in current functionality
All questions and reported incidents that cannot be resolved at the user/team level need to be
reported to the Governing Body for Triage

18. INTAKE AND TRIAGE – FRAMEWORK AND PROCESS
18
FRAMEWORK AND PROCESS BUSINESS ADMIN
Key Areas Needs Value/Concern Value/Concern
Strategic Execution
Mission, Vision, Values
Goals, Themes, Epics,
Enterprise Alignment
Budgets, Timeframes
Platform Terminology
Theme linking to Goal type
Connectors
Framework and Practice
Taxonomy, Timeframes, Roles,
Permissions, Users access,
Organizational model, Training
and Enablement, Reporting,
Team Configuration
Executive Stakeholder-ship
Budget, Security, Regulatory
Compliance, Visibility and
Reporting
Platform terminology, Roles and
Permissions, Security, Organizational
Hierarchy, Regions, User
management
Planning
Ceremonies, Backlogs,
Estimation, Roadmaps,
Forecasting, Reporting
Confidence, Predictability,
Reporting, Budgets, Estimate,
Actual
Roles and Permissions, technical
processes and practices, Connectors
Team Execution
Ceremonies, Boards, Reporting,
Retrospectives, Assessments
Enterprise Alignment Costs
Connector, Roles and permissions,
technical processes and practices
Communities of Practice
Retrospectives, Blogs, Forums,
Assessments, Innovation
Engagement, Value,
Alignment, Innovation
Connector, Roles and permissions,
technical processes and practices

19. KEY TAKEAWAYS
• Maintaining your investment for maximum value delivery
• How to organize the Platform Team for best outcomes to
support the investment in Jira Align
• Where your Partner works for you and where Atlassian works
for you

20. KEEP THE CONVERSATION GOING…
• Connect:
• Jesse Pearlman: https://www.linkedin.com/in/jessepearlman/
• Check out Cprime upcoming webinars, read our blog, download whitepapers/case
studies & more:
• www.cprime.com/resources
• Share with us what topics you are interested in, ask us questions or give us feedback!:
• learn@cprime.com
• Follow us on Social Media, share in the conversation & keep updated on thought
leadership, events & more.

21. QUESTIONS?
WWW.CPRIME.COM | 877.753.2760
QUESTIONS?

22. QUESTIONS?
WWW.CPRIME.COM | 877.753.2760
THANK YOU
WWW.CPRIME.COM | 877.753.2760