Portfolio ↗

Platform Teams

Reducing other teams' cognitive load, measured by adoption.

4Questions
7Flashcards
2Terms
Drill this topic All of Enterprise Architecture
Questions

4 to work through

  1. intermediate

    A platform team is overwhelmed by requests and product teams complain about waiting. What does the boundary between them need to change?

    2 min answer
  2. intermediate Multiple choice

    A platform team of 9 serving 300 engineers changes model. It stops publishing modules and libraries that teams run themselves and starts operating the runtime: it owns the clusters, the pipelines and the base images, and it holds the pager for them. Within two quarters the share of services on the supported path goes from 60% to 95% and a runtime upgrade that used to take three quarters takes five weeks. What has the organisation given up?

    3 min answer
  3. intermediate

    When should an organisation create a platform team, and what distinguishes one from a service desk?

    2 min answer
  4. advanced

    You run a platform team of twelve serving four hundred engineers. Product teams say the platform is a bottleneck; your team says the requests are unbounded and they cannot do product work. Both are right. What do you change?

    2 min answer
Terminology

2 terms in this topic

practice

Platform Team Product Model

Running an internal platform team with product management disciplines — users, roadmap, support, metrics — rather than as an infrastructure function.

 concept

Platform Teams

Teams providing self-service internal capability to reduce the cognitive load on delivery teams — distinguished from a service desk by self-service.
Enterprise Architecture

Neighbouring topics

Enterprise Architecture

General material on architecture at portfolio and estate scale.

2 quiz 8 cards 7 terms

EA Domains

Business, application, data and technology architecture as viewpoints.

4 quiz 9 cards 4 terms

Application Architecture

The application estate as a designed portfolio rather than an accumulation.

4 quiz 8 cards 3 terms

Technology Architecture

Platforms, runtimes and infrastructure standards across the estate.

5 quiz 9 cards 2 terms

Capability Maps in EA

The stable frame for hanging investment, ownership and health off.

5 quiz 6 cards 3 terms

Application Portfolio Management

Inventory, ownership, cost and health for every application.

5 quiz 10 cards 3 terms

Application Rationalisation

Retire, consolidate, replatform — and why retirement is under-applied.

6 quiz 9 cards 5 terms

Technology Standards

Guidance that teams follow because it helps, not because it is mandated.

6 quiz 11 cards 5 terms

Technology Radar

Adopt, trial, assess and hold — with movement, dates and owners.

5 quiz 10 cards 2 terms

Reference Architectures

Pre-approved templates for recurring solution shapes.

4 quiz 7 cards 4 terms

Architecture Governance

Preventive, automated controls rather than review meetings.

6 quiz 8 cards 3 terms

Architecture Review Boards

Thresholds, early engagement and a real route to accept deviation.

4 quiz 6 cards 2 terms

Enterprise Integration

Estate-wide integration strategy, standards and shared infrastructure.

5 quiz 9 cards 4 terms

TOGAF

The ADM as a checklist, tailored rather than followed literally.

3 quiz 7 cards 2 terms

EA Frameworks

Zachman, FEAF and others — vocabulary rather than method.

4 quiz 7 cards 2 terms

Architecture Roadmaps

Sequencing change across an estate with dependencies and funding.

4 quiz 8 cards 3 terms

Paved Roads

Making the supported path the easiest path, with a way to leave it.

4 quiz 8 cards 4 terms

InnerSource

Open-source collaboration practices applied inside an organisation.

6 quiz 11 cards 2 terms

EA Metrics

Measuring whether architecture work changed anything.

5 quiz 12 cards 4 terms