Optimizing Workflows for Growing Development Teams

Originally published on January 23, 2020. Tools and results reflect that time.

If there’s a common thread among my last few posts, it’s this: optimize, systemize, and automate as much as you can. Your job gets easier. You make room for creative thinking. And you can reinvest that creativity to grow more effectively.

I’ve been wrestling with that over the past year as we ramp up at Veritonic. Roles and objectives are shifting from a small team testing product-market fit to a medium-sized team building a scalable SaaS application for a broader market.

Matt Gagliano Optimized Workflow for Growing Startup Engineering Team

From a Lean Team to a Growing One

When I first joined Veritonic part-time in 2016, we were a close, lean team of six. Along with Kevin Marshall, I was one of a two-person dev team, and it was easy for us to collaborate in real time. We would bounce ideas off one another, take in feedback, iterate quickly, and deliver features our clients valued.

Throughout that early period, we organized tasks in an informal way. We used Trello to aggregate bugs and cards, with no specific workflow. Without many moving parts and with fairly straightforward product goals, that system worked well.

But as the product grew more complex and the team grew with it, we needed a clearer way to organize and manage the workload. The right team needs the right tools.

Structure Before Tools

Toward the end of Q3 2019, we began to lay the foundation for an update. The first objective was to structure a more efficient workflow — one that scales with the team — before jumping to another tool.

We started with our development workflow in Github, revamping the pipeline with best practices for a dev/test site, a beta release stage, and the final production site.

Next, we looked at the tools for organizing our product roadmap and breaking that roadmap into tasks for each feature and sprint. Since our history with Trello was spotty, I looked at other product management tools for a clean slate.

These days, most product management tools do more or less the same thing. Most have kanban boards and lists, Gantt charts and calendars, and the ability to assign tasks or cards to specific people. So the priority was to structure a workflow that fit our team and would scale as we added people, regardless of the tool.

Among options like Basecamp, Monday, and Jira, we settled on Asana for its features, UX, and easy integration into our new workflow.

The Development Queue

This new workflow culminates in a kanban-inspired sprint board that we call the Development Queue.

Engineering Team Development Workflow by Matt Gagliano

The Development Queue is divided into columns that map directly to our development and release stages. Tasks begin in an “Assigned” column, move to “In-Progress” where they are built in a branch and tested on our development site, then move to “In QA” while being merged and pulled to our closed beta site.

After a quality assurance review on the beta site, completed tasks move to “Ready to Release,” indicating they are ready to merge and pull to production. The final column, “Completed,” marks the end of a task’s lifecycle.

Bugs, Feature Requests, and Project Boards

In addition to the Development Queue, we implemented a Bug Tracking board and a Feature Requests board. Both serve as sources for the cards we assign and add to the Dev Queue.

Bugs are sorted by priority, ranging from Critical to High Priority and Low Priority, with an additional column for bugs we could not reproduce.

Critical bugs are often assigned to the Dev Queue immediately. High Priority and Low Priority bugs are discussed and assigned at one of our semi-weekly engineering standup meetings.

Engineering Team Bug Tracking Workflow by Matt Gagliano

The Feature Requests board uses a similar kanban format, with columns for each main section of the Veritonic platform. Tasks are added as cards to the relevant column, discussed at a weekly product roundtable, then prioritized and assigned to the Dev Queue.

To source tasks efficiently, we also created two internal tools for submitting bugs and feature requests. These are forms in our admin area that, when submitted, automatically add tasks to the Bug Tracking and Feature Requests boards in Asana.

The final pieces of the task funnel are the active and long-term project boards — specific boards for particular features or major updates. Since these projects often involve many smaller tasks, it makes sense to split them into their own boards.

Like the Bug Tracking and Feature Requests boards, individual project boards also funnel tasks into the Development Queue. Every card in the Development Queue is sourced from and associated with one of the other boards. That makes it easy to sort and prioritize without a backlog piling up in the main field of view.

Results After Three Months

The new workflow and tools optimize how we add, organize, assign, and complete tasks across the full lifecycle from concept to deployment. After a three-month trial in the last quarter of 2019, we’ve seen strong results and plan to keep going. In that time, we’ve increased our bug resolutions and improved our shared alignment on how each smaller task builds into the larger product vision.

Similar to the product itself, we’ll iterate this workflow as needed. It’s a solid starting point for developing at scale.

I’m always interested in how teams organize and execute. Do you have a workflow that works well for you and your team? Let me know on X.

Follow Along

Subscribe to my newsletter and get notified when I publish something new. Unsubscribe any time!