Atlassian Evolutionary Service.
We improve, optimize and adapt the Atlassian platform to your organization's changing needs. No over-configuration, no functional debt.
Service Request and Change Request
Standard changes
Included in the Evolutionary Catalog. Defined, demanding SLAs, associated operational documentation and an up-to-date CMDB.
- Analysis and response · High: 1 day · Medium: 2 days · Low: 3 days
- Resolution based on estimated effort and planning
Non-standard changes
Out of catalog. Effort and duration not predictable up front, with a guideline target for analysis and assessment.
- Analysis target: up to 1 month from creation
- No contractual resolution SLA
Four objective axes
- 01
Business value delivered
Contribution to objectives, efficiency or quality improvements, risk reduction, impact on growth or scalability.
- 02
Impact on users and processes
Affected users, processes involved and need for change management or additional communication.
- 03
Implementation effort
Functional and technical complexity, dependencies and estimated hours later compared against actual effort.
- 04
Associated risk
Technical and functional risk, plus potential impact on service stability.
Evolutionaries we already have defined
License management
Provisioning, updates, cancellations, target model and add-ons.
Users and groups
Management model, IdP/SSO integration, onboarding/offboarding flows.
Workflows
Design, structural changes and best-practice consulting.
Automations
Design, refactoring, model and enablement.
JSM Portal
Request types, forms, flows and catalog redesign.
Reporting and governance
Reports, dashboards, KPIs and metrics governance model.
Structure and tooling
Boards, templates, advanced filters and scalable models.
Add-ons
Installation, configuration, integration and strategy.
Controlled changes, no surprises
- 01
Operational documentation in CMDB
Every Service Request becomes a procedure any team member can execute, ensuring continuity and transferability of the service.
- 02
Business-aligned change window
Changes without impact run in business hours; impactful changes are scheduled out of hours so they don't affect operations.
- 03
Communication plan
Communication before, during and after the change, tailored to impact and audience.
- 04
Post-implementation validation
The evolutionary is only closed when validation is satisfactory and documentation is up to date.
Continue the journey →
Methodology →