Basecamp 1

  1. /
  2. Basecamp 1
In the presence of extreme dependencies, it is often very difficult, if not impossible to achieve true agility. At Basecamp 1 you’re typically looking at ​interactive and incremental team-based development. You can likely use Scrum or Kanban at the delivery level, but teams are often heavily orchestrated by a program or integration team. They’re operating under a heavier governance model. Ideally, these governance bodies are using a Lean/Kanban-based program and portfolio system—that’s the goal—but​ roadmapping, rolling wave planning, and progressive elaboration should be the rule. Teams lose some decision making at this Basecamp for the sake of receiving highly coordinated backlogs that are aware of system constraints before the teams take stories into planning.
Basecamp 1     |    Basecamp 2     

 

The pilot is a special case of the first Expedition to Basecamp 1. It involves getting a subset of the organization—a single Expedition—to a stable, reliable, and predictable state. They need to be a beacon to the rest of the organization for how the Transformation may proceed. 

The mechanics of the Transformation involve the mundane execution of the plan. Forming and possibly collocating​ teams. Getting the teams into training sessions and workshops. Getting tooling setup and configured, in addition to helping the teams get started using the tools. Backlogs are built and estimated, rolling wave planning is established, progress is assessed, and the pilot teams are hardened and stabilized over a period of several months as they move to Basecamp 1. ​

 

Basecamp 1 Outcomes

Form Teams     |     Establish Flow of Work     |     Make & Meet Commitments   |     Improve the system     |     Stable Throughput     |     Road Map     |     Release Plan     |     90 Day Rolling Backlog