The Atlassian Cloud offers a flexible platform that can be customized and optimized to meet your specific needs.
In this webinar we discuss what Atlassian Cloud optimization is, when you should do it, the impact to compliance and governance, and the “cost” of optimization. We’ll explore the importance of mitigating risk, maintaining compliance, ensuring data integrity and quality, and optimizing the returns on your Atlassian investment.
Brandon Huff, VP, Atlassian (Cprime), and Pavel Fomin, Head of Migrations (Cprime), share their experiences, thoughts and best practices on cloud migration considerations.
You will learn about:
- What Atlassian Cloud optimization is
- The impact of not optimizing your configuration
- How governance is enhanced with optimization
6. • SaaS as an offering from outset
• Experiencing significant growth and expansion
• Substantial investment in Cloud Infrastructure
• Microservices, performance, security, pricing structure, etc.
• Accessibility of Cloud
ABOUT ATLASSIAN CLOUD
7. BENEFITS OF ATLASSIAN CLOUD
SaaS Model Availability/Scalability
Latest Releases
User Management
Security
Apps & Extensibility
Performance
TCO
8. THINGS TO CONSIDER
Backend Access
Latest Releases
Functionality
System Admin
Data Residency
Support / SLAs
Compliance
10. WHY OPTIMIZE?
Reduce Complexity
Add Complexity introduces opportunities for issues and challenges as well as impacts the ability for usage across the greater organization
Reduce Cost of Management & Maintenance
Some of the greatest costs associated with the Atlassian Ecosystemcome with the cost of overhead and management – simplify to reduce the need for staff to
just help manage the ecosystem
Easy To Add Complexity, Difficult To Remove It
Simplicity significantly reduces both the complexity and cost associated with the management and maintenance of your systems
Simplicity Is Important
Start Simple & Iteratively Enhance
10
11. HOW DOES OPTIMIZATION HELP?
Enterprise-Wide Reporting Road-Mapping, Dependencies, & More
Strategic architectural planning includes projects, schemes, templates, and access management helping to reduce the time and money associated with
rearchitecting later
Prevent Unintentionally Silo’ing
Standardization enables enterprise-wide reporting and reduces the overall cost and complexity of administration and significantly impacts the reliability and quality
of reporting
Ensure Real-Time, Reliable, On-Demand Reporting Capabilities
Simplicity significantly reduces both the complexity and cost associated with the management and maintenance of your systems
Why Standardization Is Important
Getting The Most Out Of Jira
11
12. WHAT TO OPTIMIZE?
Projects
Architecture Should Be Consistent - Impacts To On Demand Reliable, Real-time, Reporting
Schemes / Templates
Schemes & Templates Help Manage The System– Impacts To Total Cost Of Ownership, Overhead, Management
Impacts To Ecosystem
Evaluation Of Impacts To Ecosystem Are Critical – Without This You Can Inadvertently Silo An Organization Or Negatively Impact Other Area’s
Strategic Architectural Design is Key
Ensuring You Get Out Of It What You Bought It For
12
13. OPTIMIZATION STEPS
Strategic Architectural Planning
Standardization enables enterprise wide reporting and reduces the overall cost and complexity of administration and significantly impacts the reliability and quality
of reporting
Standardization
Standardization enables enterprise wide reporting and reduces the overall cost and complexity of administration and significantly impacts the reliability and quality
of reporting
Simplicity
Simplicity significantly reduces both the complexity and cost associated with the management and maintenance of your systems
3 Keys to an Optimized Configuration
Balancing Customization with Cost
13
15. ATLASSIAN ECOSYSTEM
The good and the bad about the Atlassian ecosystem is its’ flexibility:
Highly Configurable
Easy to Stand Up
Costly & Disruptive to Rearchitect
Governance is Critical
16. GOVERNANCE MATTERS
Mitigate Risk & Maintain Compliance
Ensure Data Integrity & Improve Data Quality
Set, Maintain & Educate On Standards & Best Practices
Evaluate Impact & Manage Changes To The Ecosystem
Maintain Health & Long-Term Continuity While Reducing Ownership Cost
A Robust Governance Framework Is Critical To Protect Your Ecosystem
16
17. WHAT YOU NEED TO SUPPORT GOVERNANCE IN THE CLOUD
STRATEGIC PLANNING
CHANGE MANAGEMENT
COMPLIANCE & MAINTENANCE
18. STRATEGIC PLANNING
The wrong architecture and structure can be costly
• Take The Time To Think About Architecture – Save time and cost
• Information Protection & Access Management – Build it in
• Scalability & Data Architecture - Plan for flexibility and long-term needs
• Get an expert to help you – Leverage best practices, avoid pitfalls
• A little planning goes a long way
19. COMPLIANCE
Regular Updates to Policies and Standards
Custom Dashboards and Reports to Identify Compliance Risks
Clean up and maintain your instances
Manage Human Risk
Maintaining Your Atlassian Ecosystem
(Training, Enablement, Imbedded Governance Team Members)
(Leverage Admin Insights, Scheduled Releases, and Project Archiving)
20. CHANGE MANAGEMENT
• Formal Intake Process
• Formal Committee Discussion
• Within vs Outside of Policy Limits
• Formal Committee Vote
• Objection vs Non-Objection Vote
• Documentation
• Decision vs Recommendation
• Communication
Change Management Process Elements
Intake
Action
Decision
Communication
22. WHY GOVERNANCE MATTERS
There’s a lot at stake – strong governance practices help:
• Mitigate risk and maintain compliance
• Ensure data integrity and improve data quality
• Set, maintain and implement standards and best practices
• Evaluate the impact and manage changes to the Atlassian tools ecosystem
(like clean up and optimization)
• Maintain the health and long-term continuity of the Atlassian tools
ecosystem
• Ensure your users can leverage the features and benefits of the Atlassian
platform for your organization
29. BEST PRACTICES – DESIGN & ARCHITECTURE
Just Because It Can Be Done, Doesn’t Mean You Should Do It
Simplify, Simplify, Simplify
Long Term Costs Are High With Over Customization
Inadvertent Silo’s Are Created With Over Customization
Performance Impacts Are Seen With Over Customization
Key Considerations
Strategic Planning Will Save You Tons Of Time, Money & Headache
29
30. BEST PRACTICES – DATA QUALITY & INTEGRITY
If You Want Quality, Reliable, On Demand Reporting, You Must Streamline
Training On How To Use The Tool Is Critical
Create Cheat Sheets On Data Fields To Ensure Quality Data Inputs
Garbage In – Garbage Out Applies
Write JQL Smart To Avoid Impact To System (Ex: assignee=current user)
Key Considerations
Best Practices For Data Quality & Integrity
30
31. BEST PRACTICES – CONFIGURATION ELEMENTS
Minimize Number Of Custom Fields
Make Custom Fields General For Reusability (Example: ID)
Minimize Number Of Statuses As Much As Possible
Use General Terms When Possible For Reusability (Example: In Progress)
Minimize Issue Type Schemes & Reuse
Key Considerations
Reduce Total Cost Of Ownership & Improve Manageability
31
32. BEST PRACTICES – CONFIGURATION ELEMENTS (con’t)
Minimize Workflow Options When Possible & Reuse
Minimize Workflow Schemes
Minimize Number of Screen Schemes
Minimize Resolution’s When Possible (Use Custom Field For Categories)
Create & Use Templates To Prevent Creation Of Unnecessary Elements
Key Considerations
Best Practices For Best Results
32
33. KEY TAKEAWAYS
• Be deliberate in your optimization approach and
the functionality you need to support your
business processes
• Simplification makes management and
governance easier
• Just because you can, doesn’t mean you should
• Governance can minimize risk and help ensure
quality
• Leverage an expert where needed