It was January 10, 2026, and the temperature in my suburban Minneapolis garage was a crisp 20 degrees. Standing under the buzzing shop lights, I felt the sharp, metallic scent of the space heater warming up, clashing with the sweet, heavy aroma of freshly sawn white oak. I realized my 'Honey-Do' list wasn't just a list; it was a poorly managed product backlog destined for a project failure.
Before we get into the sawdust and spreadsheets, a quick heads-up: This site uses affiliate links. If you buy something through these links, I earn a commission at no extra cost to you. I only recommend plans and tools I have actually used in my own workshop, like the ones that kept this specific project from crashing during the deployment phase.
The Backlog and the Bench
In my day job as an IT project manager, I spend my life staring at Jira boards and managing 'sprints.' In my garage, I usually spend my time making expensive firewood and wondering why my joinery looks like it was done by a caffeinated squirrel. But this winter, the mudroom bench project was different. It wasn't just a request from my wife; it was a high-priority feature request for our home’s entry-way infrastructure.
I decided to treat the build like a software rollout. I started by sourcing 22 board feet of white oak. If you aren't from the Midwest, you might not know that white oak is the gold standard for moisture resistance—essential when you're dealing with the salt-crusted, snow-covered boots we wear six months of the year. I budgeted $342 for the project: $215 for the lumber, $85 for heavy-duty hardware, and $42 for finishing supplies. I was determined to stay on budget and on schedule.
Setting Up the Kanban Board
I literally stood there with a clipboard and a pocket protector in a garage, wondering if I'd finally lost my mind or just found it. To keep the project moving, I cleared a spot on the wall next to my table saw and created a physical Kanban board using blue painter's tape and Post-it notes. My columns were simple: Backlog, In Progress, Testing/Sanding, and Shipped.
My wife walked into the garage on a Tuesday evening, saw the Kanban board, and asked if she needed to submit a 'ticket' to get the kitchen chair fixed. I told her the chair was currently 'out of scope' for the current sprint. She didn't find it as funny as I did, but she did appreciate that I finally had a plan that didn't involve me aimlessly wandering around Home Depot for three hours every Saturday morning.
I planned for 6 active weekend sprints, totaling 48 labor hours (8 hours per weekend). My 'Sprint Velocity' was pegged at 3—meaning I aimed to complete three major tasks per weekend, such as 'Mill carcasses,' 'Cut tenons,' or 'Apply first coat of finish.'
The Technical Documentation: Why Plans Matter
One thing I’ve learned since my first lopsided bookshelf is that 'winging it' is the woodworking equivalent of writing code without a compiler. You need technical documentation. For this bench, I relied on a set of blueprints I found through TedsWoodworking. Having a pre-vetted cut list acts as your technical spec; it tells you exactly how much material to buy so you don't end up with $50 worth of white oak scraps that are too small for anything but coasters.
I’ve checked out a lot of resources, and while some are hit-or-miss, I’ve found that having a massive library of 16,000 plans makes the 'planning phase' much less painful. You can read my full TedsWoodworking review to see how I filter through the noise, but for this mudroom bench, the detailed measurements were my North Star.
The Deployment Error (A.K.A. The Boot Crisis)
By February 14, 2026, I was deep into Sprint 3. The carcass was assembled, and the joinery was tight. I was feeling like a pro. Then came the 'User Acceptance Testing.' I asked my wife to bring out her tallest winter boots to make sure they fit in the cubbies.
They didn't. Not even close.
I had measured the 'standard' boot height, but I hadn't accounted for the 'Minnesota-Extra-Tall-Insulated' variety. It was a classic deployment error: I built what I thought the user wanted, not what the user actually needed. Because I was working in an Agile framework, I caught it before the glue was dry on the face frames. I had to pivot, adjust the shelf pins, and sacrifice one of the smaller storage cubbies to create a 'high-clearance' zone. It was a mid-sprint adjustment that saved the entire project from being a functional failure.
A Critical Bug in the Finishing Phase
Woodworking has a way of humbling you just when you think you've mastered the workflow. During the final sanding phase, I fell into a trance. I spent two hours meticulously sanding a board only to realize I’d used the wrong grit sequence, skipping from 80 straight to 220. I’d left deep swirl marks everywhere that only became visible once I wiped it down with mineral spirits.
In IT, we call this 'technical debt.' I tried to shortcut the process, and I ended up having to go back and redo the work correctly. It pushed my 'Shipped' date by a full day, but you can't rush the UI (the finish) if you want people to actually use the product. If you're struggling with the cold like I was, you might want to check out my Minnesota Winter Survival Guide for Unheated Garage Woodshops to see how I kept my wood glue from freezing during these long sanding sessions.
The Agile Woodworking Limitation
I have to be honest about where this workflow falls apart. My garage is half of a two-car space, meaning I have enough room to leave my tools out and my Kanban board taped to the wall. This Agile approach fails for apartment woodworkers with limited storage. Agile's focus on frequent iteration and ongoing inventory management is nearly impossible when you must clear your entire workspace and pack every tool into a closet after every single session. If you can’t leave your 'work in progress' (WIP) out, the mental overhead of 're-starting' the sprint every Saturday morning kills your velocity.
Final Delivery and Retro
I 'shipped' the bench on March 21, 2026. The total cost held at $342, and the labor clocked in exactly at 48 hours. It’s not perfect—there’s a small gap in the left-hand shoulder of one tenon that I filled with a mix of sawdust and glue—but it’s functional, it’s white oak, and the boots actually fit.
Applying project management to the garage didn't make me a master carpenter, but it did stop the 'scope creep' that usually leaves my projects half-finished for six months. If you're tired of having a garage full of half-started 'legacy systems,' I highly recommend grabbing a solid set of plans to act as your project roadmap. I’ve had great luck with the variety in TedsWoodworking for everything from these big furniture builds to small shop organizers that keep my 'sprint' workspace clean.
Now, if you'll excuse me, I have a 'ticket' to address regarding a squeaky kitchen chair. The backlog never truly clears, does it?