Metal Toad Project Manager Profile: Steve Winters
As part of our project manager application process, we ask applicants to respond to a number of questions about themselves focused on their approach...
One of the newer processes we’ve implemented at Metal Toad is that of stage gating.
One of the newer processes we’ve implemented at Metal Toad is that of stage gating. I was going to title this post "Stage Gating for Project Success," but really it’s all about risk avoidance and limiting potential failure on projects by following our tried and true steps to keep projects on track.
What is stage gating, you ask? Simply put, stage gates are approval checkpoints during the life cycle of a project. Depending on the level of complexity involved with a specific stage and the risk of failure of that stage is skipped or completed insufficiently, different levels of experience and seniority within the company are required to approve a stage.
"That sounds like lots of red tape," you say. Yes, potentially, but we’ve worked to implement stage gates in a way that create mental triggers for project “stage” completion rather than outlining a dogmatic list of how things need to be done. The stages also make sure that our senior staff and executive team are never too far removed from projects, forcing them to give gut checks, provide insights, and question assumptions made by project teams.
Confused? Let’s give some visual representation. Since we’re an agency full of engineers, there are plenty of people who wanted to create an app, but for the MVP version of stage gates, we went with plain old paper printouts hung on a wall.
The physical format gives certain weight to their importance, and it makes them hard to ignore or forget. We even gamify things a bit with headshot stickers of staff members placed on circles when a stage is approved.
So many of mini me!
Here’s a single stage for statement of work review:
Interpretation is pretty simple. The two headshot icons indicate that two people need to review statements of work before they go out the door. The “Approval” column is the primary approvers who should lay eyes on the SOW (in this case, director of client services, director of project management, and vice president). “Backup” (office manager and director of development) are the roles that can review if primary approvers aren’t available. The “bypass” column are roles (president or vice president here) that can approve skipping a stage entirely, which for a SOW would either mean closing work without a SOW or sending a SOW unreviewed.
With that, here’s one of the variations of our stage gate document:
We have numerous options when it comes to stage gates, ranging from more traditional plan > build > ship projects to sprint-based agile projects. The project phases are becoming increasingly decoupled in printed form so that multi-phase projects, discovery projects, and design projects can all be accounted for with stages.
With that out of the way, let’s delve a bit into our most important stages and why they exist. Yours may differ a bit, but I suspect that many of the core tasks we need to complete on a project will ring true for you too.
A project can be doomed from the start if the sales process is handled poorly. Here’s what we make sure to always do before closing a project to avoid catastrophe:
Whether you’re talking about a traditional waterfall planning process or agile sprint zero, planning is one area most susceptible to skipped stages and rushed timelines. When those stages are skipped, it can result in massive misses on timeline, budget, and client satisfaction. Make sure you:
Good development practices and established QA and testing will usually avoid producing a lemon. That mean’s you really shouldn’t skip these steps:
By the time you’ve reached deployment, the risks of wrecking a project have lessened a bit, but there are still some stages it’s advisable to respect if you want to have a healthy agency and long-term relationship with a happy client:
Some things are important enough that you’ll want to keep a constant pulse check going throughout the duration of a project:
There are many additional stages and decisions that should be considered during the course of a project, but these are the ones that we count as absolutely crucial. Any one of them could mean significant project failure when it comes to customer satisfaction, agency profitability, or both. We’ll continue to evolve this process over time, but so far so good. If you have other thoughts on important stages with serious negative implications when skipped, we’d love to hear them!
As part of our project manager application process, we ask applicants to respond to a number of questions about themselves focused on their approach...
As part of our project manager application process, we ask applicants to respond to a number of questions about themselves focused on their approach...
Software, like all things in life, grows old. In the world of software, we call this technical debt. Managing technical debt is like managing aging;...
Be the first to know about new B2B SaaS Marketing insights to build or refine your marketing function with the tools and knowledge of today’s industry.