Adrian Straker

January 15, 2025

Adapting Basecamp's Shape Up for IT Infrastructure Projects: A Practical Guide


Infrastructure projects in IT often feel like a different beast compared to product development. While Basecamp's Shape Up methodology was initially designed for product work, its principles can be powerfully adapted for infrastructure initiatives. Here's how to make it work for your IT teams.


Understanding Shape Up

Shape Up is not just another project management framework; it's a philosophy that rethinks how projects are managed from inception to completion:

  • Shaping: Before any project cycle begins, senior team members "shape" the work by defining the project's scope with enough detail to start but not so much that it stifles creativity or innovation during execution.
  • Betting: Projects are pitched in a "betting" session, during which the team decides which to take on based on their strategic importance and appetite for investment in terms of time and resources.
  • Building: Once a project is selected, it moves into a fixed six-week cycle, during which teams work autonomously to deliver it. If the project isn't completed within this cycle, it's either killed or reshaped for a future cycle.

Adapting Shape Up for IT Infrastructure

1. Shaping IT Projects:

  • Identify Key Constraints: Infrastructure projects often deal with hardware, networks, and systems with specific constraints. Shape Up's concept of "appetite" can be used to decide how much time and resources are available or can be allocated for each project.
  • Define Scopes: For IT infrastructure, this could involve mapping out network changes, server migrations, or security upgrades with clear boundaries on what is in and out of scope to avoid scope creep.
  • Risk Assessment: Unlike software projects, infrastructure might involve physical elements where risks like downtime or hardware failure are significant. Use shaping to outline potential risks and mitigation strategies.
  • Documentation: Create a pitch document that outlines the problem, the proposed solution, and the risk assessment. This document will guide the betting process.


2. Betting on Projects:

  • Strategic Alignment: Gather key stakeholders for a betting meeting where each project is discussed regarding its impact on business goals, urgency, and alignment with long-term IT strategy.
  • Resource Allocation: Decide based on the team's capacity and the importance of each project. This might mean prioritizing a cloud migration over less critical updates due to strategic business needs.
  • Cool-Down Period: Implement a two-week cool-down period post-cycle to address any unforeseen issues or to refine what has been done, which is particularly useful in infrastructure where testing in real-world scenarios might reveal additional tweaks.

3. Building Phase:

  • Team Autonomy: Empower your IT teams with the autonomy to decide how best to tackle the project within the set boundaries. This could mean choosing between different vendors for hardware or deciding on the best approach for system integrations.
  • Hill Chart: Use the Hill Chart to track progress from "unknowns" to "knowns" and "done". This visual can be particularly effective in managing complex infrastructure projects where progress can be hard to gauge.
  • Early Wins: Encourage teams to get one piece of the project done early, like setting up a new server or testing a segment of the network, to gain momentum and validate the approach.
  • No Backlog: Avoid the traditional backlog. If a project doesn't make the cut in one cycle, it's either reshaped for the next cycle or dropped, ensuring focus on what's most important now.

4. Continuous Improvement:

  • Review and Reflect: After each cycle, review what worked and what didn't. This isn't just about project outcomes but also how the team manages the process, tools, and workflow.
  • Adapt Methodology: Since IT infrastructure might have different challenges than software development, continuously adapt the Shape Up methodology. Learn from each cycle to better shape projects in the future.


The Core Concepts: Shaping Infrastructure Work


Unlike product features, infrastructure projects often deal with system stability, security, and scalability. The shaping process needs to reflect these unique characteristics:


1. Setting the Appetite


In Shape Up, the "appetite" isn't just a time budget – it's a commitment to scope. For infrastructure projects, this might look like:

  • Six-week cycles for major platform upgrades
  • Two-week cycles for security implementations
  • One-week cycles for critical performance optimizations

The key is matching the appetite to the risk level and business impact. A database migration might deserve a full six-week cycle, while implementing a new monitoring solution might fit into two weeks.


2. Defining the Solution Space


Infrastructure projects require careful boundary setting. Your shaped work should include:

  • Clear technical constraints
  • Integration points with existing systems
  • Fallback scenarios
  • Performance requirements
  • Security considerations

For example, when shaping a cloud migration project, you might specify: "Move the customer database to AWS RDS, maintaining sub-100ms query response times, with zero downtime during transition, excluding legacy reporting systems."


The Build Phase: Executing Infrastructure Work


Infrastructure projects often require more careful orchestration than product features. Here's how to adapt the build phase:


Weekly Synchronization


While Shape Up traditionally minimizes check-ins, infrastructure work benefits from regular synchronization:

  • Monday planning: Review the week's technical challenges
  • Wednesday check-in: Validate assumptions and catch potential issues early
  • Friday demo: Show progress on measurable metrics

Making Progress Visible


Infrastructure work can seem invisible. Make progress tangible by:

  • Creating dashboards for key metrics
  • Documenting system changes
  • Recording before/after performance measurements
  • Tracking risk reduction metrics

Managing Uncertainty and Risk


Infrastructure projects often carry significant risk. Shape Up can help manage this:


Circuit Breakers


Define clear circuit breakers for your infrastructure projects:

  • Performance degradation beyond specified thresholds
  • Security vulnerabilities discovered during implementation
  • Integration failures with critical systems
  • Budget overruns on cloud resources

Small Batch Deployments


Break large infrastructure changes into manageable pieces:

  • Deploy changes to non-critical systems first
  • Use canary deployments
  • Implement feature flags for gradual rollouts
  • Create rollback plans for each deployment

Real-World Example: A Database Migration Project


Let's see how this works in practice:


The Shaped Work


Appetite
: Six-week cycle Problem: Current database approaching capacity limits Solution Space:

  • Migrate to new PostgreSQL cluster
  • Must maintain current performance
  • Zero downtime requirement
  • Exclude archival data older than 2 years

The Implementation Plan


Weeks 1-2
:

  • Set up new database infrastructure
  • Create migration scripts
  • Establish performance benchmarks

Weeks 3-4
:

  • Run test migrations
  • Build monitoring
  • Develop rollback procedures

Weeks 5-6
:

  • Execute production migration
  • Verify data integrity
  • Monitor performance
  • Decommission old system

Measuring Success


Infrastructure projects need clear success metrics:

  • System performance improvements
  • Reduced incident rates
  • Lower operational costs
  • Improved security posture
  • Decreased technical debt

Conclusion


Shape Up can be a powerful framework for infrastructure projects when properly adapted. The key is maintaining the methodology's core principles while acknowledging the unique challenges of infrastructure work. By clearly defining appetites, carefully shaping work, and maintaining appropriate check-ins, teams can deliver infrastructure projects with the same efficiency as product features.


Remember: successful infrastructure projects aren't just about technical execution – they're about delivering value to the organization while managing risk and maintaining stability. Shape Up provides the structure to make this possible.

About Adrian Straker

Experience Infrastructure Architect and Systems Engineer Specializing in Virtualization Application delivery Technologies and Disaster Recovery. Involved in projects in Large Enterprise environments and small business environments. Certified VMWare Professional with extensive Nutanix experience