The world of Software Development is a fast-paced environment. To build a winning development team, you first have to determine how you will track your operations. Without the proper tools to organize every aspect of your development process, very little can be accomplished. But not to worry! We can help.
This guide will introduce you to 5 boards that you can use to kickstart your Software Development operations. With these boards in your toolkit, you can manage anything thrown your way.
Set up your Roadmap board
The first board you'll need to pave the path to success is a Roadmap. The Roadmap board is the most high-level board we'll set up for this workflow. Use the Roadmap to plan and keep track of all of your major initiatives and milestones for each quarter.
Our Roadmap is split into groups for each quarter of the year with each item representing an initiative. On this board, we're using several different types of columns to track each initiative. A few highlights are:
- The Status Column, used to define the level of impact of the initiative.
- The Tags Column, used here to keep track of what Domain the initiative is under.
- And the Dropdown Column, used to choose which pricing Tier this new initiative will impact.
- We're also using a Link to Item Column and a Mirror Column on this board (shown below). These two columns are an incredibly powerful combination. They allow you to see data from another board while viewing your current board.
Get your timing right with the Timeline View
To make sure that you're spacing release times appropriately, you'll want to take a look at the Timeline View. The Timeline View will show you where your schedule contains overlapping initiatives or times that your team is being underutilized.
Automations are simple, customizable processes that you can create in just a few seconds. They can be push notifications of specific updates or automatic actions that are taken once an action item is complete.
To make communication easier on your Roadmap and to make sure the right people stay informed, we've added two automations to this board:
- When the status changes to stuck or done, notify initiative subscribers.
- Three days before the initiative begins, notify the members assigned to the item's Task force column.
Set up your Sprint planning board
Make cross-functional work simple with the Sprint planning board. This board allows you to manage scrum iterations efficiently and transparently. How you build out each iteration is entirely up to you. You can add items from your Roadmap or you can add new ideas. On this Sprint planning board, we've added a group to the bottom of the board for your backlog.
This board includes a Progress Tracking Column which is connected to the Product status, Design status, and Dev status columns. When all three columns are marked as done, the item's progress will show as 100%. It also includes a Numbers Column that you can use to track Story Points.
Keep things moving forward with the Workload View
On this board, we've set up the Workload View. This is a key feature if you're looking to track each team member's contribution and capacity. The Workload View can help you to visualize assignments.
This board has three automations set up to keep your work on track. The first two automations create a waterfall effect, meaning that an individual is notified only once the previous individual has completed their portion of the work. The whole workflow starts with the person responsible for the Product.
- When the Product person changes the Product status to done, notify the Designer responsible for the item.
- When the Design status changes to done, notify the Developer responsible for the item.
And the third automation on this board ensures that all item subscribers are aware when an initiative is set to begin.
- When the timeline arrives, notify all of the item's subscribers.
Connect your boards
As mentioned earlier, we can use a Link to Item Column and a Mirror Column to connect our two boards together. On the Roadmap, in order to track progress, we're using these columns to connect each initiative to its correlating items in iteration on the Sprint planning board. This means that you won't have to switch back and forth to get the full picture. Even better, when you update the connected data on either board, the data will update everywhere that it's linked.
Set up your Bug queue board
The Bug queue board is essential for managing a seamless bug reporting and resolution process. On this board, you can track new bug tickets from creation onward.
This board uses many of the columns we've introduced earlier in this guide to track all of the important details about a bug-- a Dropdown Column to indicate the Source of the bug, a Status Column to track Priority, and a Tags Column to track the Domain.
View the bug status according to the developer assigned
The Chart View is an excellent way to see a breakdown of data on the board. In this case, we're using the Chart View on the Bugs queue board to view the status of the bugs assigned to each developer. This gives us a good idea of how each developer is managing the bugs assigned to them.
There are two key automations set up on this board to keep communication flowing.
- When a new bug report is received, notify the board's subscribers.
- When the status changes to Ready for dev, notify the Dev who is assigned to the bug.
And the last set of automations are designed to keep your board organized.
- When the status changes, the item will move to the corresponding group on the board.
Set up your Incident report board
No one is a fan of incidents, but they happen to all Software Development teams. The Incident report board is designed to help you manage your ongoing incidents in one place. With all of the data you need to take action centralized in a single board, you won't have trouble diagnosing and preventing future incidents.
The most important column on this board is the Severity column. When you choose the severity of the incident, a series of automations will create a new update in the Updates Section. This update is where the Reporter can write a report on the incident.
On the Incident report board, we're also using the Dropdown Column to indicate the Services impacted. And, for the final time in this guide, we're using the Tags Column to track the relevant Domain. We'll discuss the reason for this below.
Take a deeper look with the Chart View
We're also using the Chart View on this board. We have three different views set up. The "Root Cause Chart" allows us to see a breakdown of the root cause of all incidents. The "First Time vs. Recurring" chart tells us whether an incident is being reported for the first time or it's recurring. The "Reporting Status by Dev" chart shows the status of all reports according to the developer.
In addition to the automations mentioned earlier, this board has two automations set up to make your workflow more efficient.
- When a new incident is created, change the Status to Not reported. This is to indicate that a report on the incident has not been written yet.
- Devs will receive a reminder notification for every day that they haven't filled out their report. Once the Dev fills out their report, the notifications will stop.
Set up your On call developer - schedule board
Now that you have your boards set up to manage your workflow, you'll need to keep track of your team's availability. The On call developer - schedule board is intended for you and your organization to know who is available and when.
This board also uses a series of Link to Item Columns and Mirror Columns (pictured below) to connect back to the Bug queue board and the Incident report board. With these connections built into your schedule, you'll be able to see what bugs the developer is responsible for and which incidents took place during their shift.
Get in contact quickly and easily
We've set up one automation on this board. The automation will notify the Developer one day before they're scheduled to be on call. With proper notification, no one will ever forget a shift.
Gaining insight with Search Everything and Dashboards
Remember all of the tags you set up for your Domains? Now that your workflow is ready to go, you can use Search Everything to view all data relevant to a given Domain. Search Everything will show you where a given tag appears on all of the boards across your account.
If you want to gain greater insight, Dashboards are an excellent way to display data across multiple boards in one place. You can customize your dashboard using widgets.
For example, in this workflow, your developers are assigned to incidents and bugs across multiple boards. The Workload Widget can give you an overview of how your team's time is being spent overall. Explore our other widgets for more ideas on how they can help you to gain greater insight into your workflow.
- Your plans for the year are laid out clearly with the Roadmap.
- The Sprint planning board helps you to implement those plans.
- Track and manage any bugs that may come up with the Bug queue.
- The Incident report board helps you to take action on any incidents that may occur.
- To see who is available and when, utilize the On call developer - schedule.
- The On call developer - schedule board connects to the Bug queue and Incident report boards to provide a clear picture of what your developers are assigned to and what they managed during their shift.
You're ready to build your Software Development workflow!
If you have any questions, please don't hesitate to reach out to our customer success team at [email protected]. We're here for you 24/7. 😁