Do you need a quick way to check and share project status? Use an extended Kanban board for planning and status. Move items from one work queue to the next, from planning to released. You’ll be more organized and always ready with product status.
Here’s the extended Kanban queuing technique.
All ideas begin in the Planning stage. Here, you’ll attach personas, problems, critical dates, outcomes, needs, constraints, and other relevant context as you flesh out the story. This will probably have the largest list of stories.
Stories are moved from Planning to Ready as a result of a formal discovery session. That is, your product team agrees that these stories are ready to be pulled into development. In this queue, you adjust priorities continually and provide more context. You can add and revise until the story has been turned over to the product team.
To feed the developers, you’ll consider only the items in the Ready queue. These items are prioritized for business value but always take into account your own judgment. Just because something has a high priority, it may not be the most important thing to work on next. Look at your ready queue from the standpoint of “What is critical to be done in the next 90 days?” Or, “What must we do to survive?” These items are the ones you’ll want at the top and ready to pull into the Development queue.
The Development stage is only for work in progress—all stories being actively worked by your team currently. Using the “pull” approach, the product team pulls work from Ready to Working only when they have the resources to take on more work.
Ensure your team is cautious to limit work in this queue—the team can easily get overwhelmed by too much work or paralyzed with indecision on what to do each day.