Model your process
Probably by now if you work in the software industry you heard about the word kanban or already are using a Kanban board with your team.
A Kanban board (usually implemented using a whiteboard, wall with stickies, or electronic version) lets you model the series of steps that as a team you have to take in order to produce working software.
Some of the benefits are that you gain visibility, communication and transparency in one simple step. And if you use it right you will be able to show bottlenecks and cope with them or at least elevate the issue to someone that has the power to solve it.
Most important is that you can focus on working based on your team capacity (Pull) vs. working by demand (Push).
However today I don’t want to do a 101 post on Kanban. There are plenty of posts for that, you can find them here, here and here.
Today I want to talk about what is the result when, once you read that intro, decide to implement Kanban with your team. What happens next?