Back to resources

Modifying the Shape Up Process

Team Processes

9 March, 2021

Seiji Naganuma
Seiji Naganuma

Director of Product Engineering at Curology

Seiji Naganuma, Director of Product Engineering at Curology, explains how Shape Up is not a one-size-fits-all solution and how they had to tailor it to their organization's structure, product, and people.

Problem

We started implementing Basecamp's Shape Up product development process in November of 2019. In the very first cycle, we came across problems when we implemented Shape Up as is written in their book. As I've come to learn, Shape Up is not a one-size-fits-all solution and needs to be modified based on your organization's structure, product, and people.

One major problem we ran into is that Curology is a rapidly growing telehealth company with a physical product where we handle patient information and support complex workflows for our organization. There is a real possibility that a high urgency issue comes onto our plate that cannot wait. Examples include issues with marketing pixels (costing thousands of dollars to the business) and security concerns.

According to Shape Up, when an engineer is assigned to a project, that is an agreement that they will be undisturbed during the cycle so that they are able to deliver their project. In our first attempt at Shape Up, every urgent item ended up falling onto a free resource, which at the time was me, the Director of Product Engineering.

Actions taken

In order to build in more flexibility around resourcing, we now form a small team of engineers called the Strike Team at the beginning of the cycle, and they are disbanded at the end of the cycle. The Strike Team is generally led by an Engineering Manager and usually has a ratio to the rest of the engineers around 1:4 ~ 1:6. An engineer will rotate through the Strike Team multiple times during their tenure at the company.

When it comes to running the day-to-day operation of the team, it is up to the Strike Team Lead (Engineering Manager). We've run it mostly through a Kanban process where engineers could be assigned smaller bug fixes or high urgency tasks depending on the week.

Lastly, we funnel all of our incoming requests through the Strike Team so we could fulfill a request to assign an engineer to assist in the Shaping Up process.

Lessons learned

  • If you implement a process as it's written in a book, be ready to make some changes.
  • Don't tie up all of your engineering resources in large chunks of time.
  • Having one point of entry for all stakeholders makes it easier to triage and prioritize issues for our flexible resources.
  • The Strike Team is also a great way to onboard new engineers on to your team.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

The Optimization and Organization of Large Scale Demand

4 May

Kamal Qadri, Senior Manager at FICO, drives the importance of setting expectations when optimizing large-scale requirements.

Managing Expectations
Delegate
Team Processes
Prioritization
Kamal Qadri

Kamal Qadri

Head of Software Quality Assurance at FICO

Why Documentation Is the Key to Success

6 April

Henning Muszynski, Head of Frontend at Doist, promotes his ideas on how documentation ensures consistency, efficiency, and standardization.

Alignment
Collaboration
Productivity
Hiring
Team Processes
Henning Muszynski

Henning Muszynski

Head of Frontend at Doist

It's Time to Say 'No' to Manual Business Processes

6 April

Henning Muszynski, Head of Frontend at Doist, talks about the cost of slow and arduous processes that add up over time and how to bring the changes systematically.

Changing A Company
Conflict Solving
Internal Communication
Feedback
Team Processes
Henning Muszynski

Henning Muszynski

Head of Frontend at Doist

Typical Challenge of Scaling Teams: What to Do When Your Process Doesn’t Scale

30 March

Christophe Broult, Director of Test Engineering at diconium, focuses on how he scaled his team while building organization and management teams in place.

Scaling Team
Building A Team
Reorganization
Team Processes
Christophe Broult

Christophe Broult

Director Test Engineering at diconium

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.