methodatlas
Session Builder

Plan adoption

Plan the kickoff that clarifies fit, pilot area, roles, and review for the method.

Adoption kickoff60 to 90 minFramework

Plan the adoption kickoff

Plan a kickoff that checks fit, defines a pilot area, and prepares the next review loop.

Derived automatically

Variant for Framework. The plan is derived from method form, profile, and runsheet.

Runsheet
Fit
Make fit and limits visible

Use the kickoff to check Komplexe Produktentwicklung against Reine Support- oder Wartungs-Workloads and keep the pilot intentionally small.

Pilot logic
Pilot first, then roll out

A pilot area makes roles, cadence, and success signals testable before the method is adopted more broadly.

  1. 1

    Orientation

    15-20 min

    Introduce core elements and principles of Scrum. Use profile and runsheet for preparation.

    Owner and participantsShared baseline
  2. 2

    Check fit

    15-25 min

    Check where Scrum helps concretely and where the method does not fit the current context.

    Owner and participantsUse boundaries
  3. 3

    Define pilot

    15-20 min

    Define pilot area, time span, and success signals. Keep the scope small enough for fast learning.

    Owner and participantsPilot scope
  4. 4

    Define responsibilities and cadence

    10-20 min

    Clarify owner, involved roles, working rhythm, and review points.

    Owner and participantsRoles and cadence
  5. 5

    Secure next steps

    10-15 min

    Capture concrete follow-up actions with owner and date.

    OwnerNext steps
Usable artifact

Kickoff Brief

For invitation, kickoff board, or preparation note.

kickoff-brief.md

Kickoff Brief: Scrum

Reason and Scope

open

Pilot Area

open

Roles

One Product Owner (backlog ordering, maximizing value); one Scrum Master (protects process); 3-9 Developers (cross-functional, deliver Increment); stakeholders as reviewers in Sprint Review.

Current State

open

Kickoff Setup

  • Duration: 60 to 90 min
  • Owner: open
  • Review date: open

Agenda

  1. Orientation (15-20 min) Owner: Owner and participants Action: Introduce core elements and principles of Scrum. Use profile and runsheet for preparation. Output: Shared baseline

  2. Check fit (15-25 min) Owner: Owner and participants Action: Check where Scrum helps concretely and where the method does not fit the current context. Output: Use boundaries

  3. Define pilot (15-20 min) Owner: Owner and participants Action: Define pilot area, time span, and success signals. Keep the scope small enough for fast learning. Output: Pilot scope

  4. Define responsibilities and cadence (10-20 min) Owner: Owner and participants Action: Clarify owner, involved roles, working rhythm, and review points. Output: Roles and cadence

  5. Secure next steps (10-15 min) Owner: Owner Action: Capture concrete follow-up actions with owner and date. Output: Next steps

Usable artifact

Adoption plan

Keeps pilot area, roles, cadence, success signals, and review date together.

adoption-plan.md

Adoption Plan: Scrum

Pilot Area

open

Roles

One Product Owner (backlog ordering, maximizing value); one Scrum Master (protects process); 3-9 Developers (cross-functional, deliver Increment); stakeholders as reviewers in Sprint Review.

Cadence

open

Success Signals

  • Product Backlog
  • Sprint Backlog
  • Increment
  • Sprint Goal

Current State

open

Ownership

  • Owner: open
  • Review date: open

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision