Teams
IT organisation from the perspective of the people
Visualise and manage your people cognitive load
Teams / Service Owners
There is only one thing in the enterprise software landscape which is more important than the software itself. It is the people. The team which builds and maintains this landscape. The team, without which this whole enterprise landscape would not exist.
Service360 uses insights gathered from the code to build up beautiful and comprehensive Service Owner pages and personal Developer profiles.
Features
- People registry:
- Individual contributors list
- Service Owners list
- Service Owners overview Available in Alpha
- Service Owner profile:
- Team members list
- Owned services
- Tech stack
- Cognitive load of the team Available in Alpha
- Performance overview: release frequency of the services across of the full landscape
- Team risks
- Individual team members contributions
- Incidents/MTTR stats (OpsGenie/PagerDuty integration) Available in Alpha
- Team documentation: agreements/norms, meeting summaries, resolutions, etc Available in Alpha
- Individual contributor profile:
- Name, email, github login
- Service Portfolio
- Currently works on
- Tech stack
- Developer journey: history of the involvement into the organisation services
- Custom data of your choice Available in Alpha
- Individual contributors history:
- Historical overview of all individual contributors ever contributed to your application landscape
- ServiceRegistry integration:
- SME computation: automatically determine SME for the Service
Individual contributors' overview
Individual contributor profile
Individual contributor portfolio
Individual contributor journey
Service Owner profile
Individual contributors history
Questions answered
- Which teams do exist in the organisation and what are they responsible for?
- How a team member has contributed to an organisation?
- Are teams loaded evenly or some are under-/over-utilized?
- Which team has the most maintenance risks?
- What are team main KPIs (release frequency/MTTR) and how do they evolve over time?
- How many developers we have which know this specific tech (nodejs, golang, java, etc)?
- What people risks are imposed on the organisation?
Very soon
We are working hard with our alpha testers to make sure you will get the best in class product. Subscribe to our newsletter to stay informed about the progress and to receive an invitation to our beta test!