First slice

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A first slice is an initial end-to-end increment of modernization that delivers usable value while revealing architectural and platform needs.

A first slice is a small, end-to-end modernization increment that delivers usable value while testing technology choices, organizational readiness, and the case for further investment. A quarter is a useful delivery target, although identifying and preparing candidates can take several weeks to a quarter. section 16.2

Shape a first slice through progressive discovery and preparation:

• Listen to diverse stakeholders and map the current system, its problems, and emerging future-state product taxonomy. section 16.2.1
• Compare candidate slices by cost, benefit, and complexity, then use a kickstarter workshop to select and plan the preferred option. section 16.2.1
• Form delivery teams early where possible, and reserve time for learning and upskilling before and during delivery. section 16.2.1
• Build only enough internal developer platform capability to deliver the slice, while validating the path to production and extracting reusable patterns afterward. section 16.2.3

A slice that teaches as it delivers

One initiative can explore a user-facing change while another investigates an internal platform, provided both create different learning opportunities. Platform and software engineers can work together through planning, standups, and mob programming, then turn the resulting patterns into playbooks and golden paths. section 16.2 section 16.2.3

Figure 16.7 Hypothetical roadmap for delivering a first slice within six months

Use the hypothetical roadmap to visualize discovery, option selection, team preparation, learning, and delivery within an evolutionary modernization sequence. section 16.2.1

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes

Explains discovery, option comparison, team formation, learning, platform preparation, and delivery, while deferring detailed implementation guidance.

Examples

Uses stakeholder listening, system-mapping workshops, parallel user-facing and platform initiatives, and a hypothetical six-month roadmap.

What it assumes

Assumes access to diverse stakeholders and teams, while teaching the need for mapping, candidate evaluation, staffing, and deliberate upskilling.

What you can do after

Apply it to select, prepare, and deliver a small modernization increment while generating reusable platform and organizational learning.

How it connects

Connects modernization with organizational readiness, product taxonomy, internal developer platforms, walking skeletons, and golden paths.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Related concepts

• modernization initiativepart of · A modernization initiative is a planned effort to update existing software, technology, architecture, or organizational capabilities to meet current needs.
• thinnest viable platformproduces · The smallest set of platform APIs, documentation, and tools that accelerates teams developing modern software services and systems.
• organizational readinessmeasures · Organizational readiness is the extent to which an organization has the capabilities, resources, alignment, knowledge, support, and willingness needed to adopt and sustain an initiative.
• business caseused by · A business case is a justification for undertaking an initiative that describes its expected value, benefits, costs, risks, and feasibility.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.