Feature tracking is the process of staying updated on the progress of feature development in every discipline involved.
Feature tracking helps keep every member aligned on a common goal, handover work easily, and ship quality features.
Instead of tracking issues that make you run after teams for updates, feature tracking lets you bring members from every team together, so you can get a full blown picture of the feature’s progress across every team, in real-time.
There’s a problem with the way we build features today - it no longer matches with your end goal.
Think about it - every product team wants to ship quality, bug-free features. When a feature needs to be built, members from different functions start tracking work assigned to them.
This works well when each member cares about fixing only a specific issue.
But you aren’t just fixing issues, are you?
You are building features and capabilities that help your customers solve their problems.
You need to plan features, prioritize it, and bring in designers, developers, and QA team to build it. We ask for updates to gauge when the feature will ship and its current status.
And yet, we spend our day tracking issues when we should really be tracking features.
Building features is hard enough already. It gets ridiculously hard to align team members on a single goal when everyone is thinking in issues.
And when members aren’t able to view the progress of the feature as a whole, they resort to simply walking up to each other to handover work, leaving everybody else in the team with outdated, stale updates.
Teams need to go past simple issue tracking.
Feature tracking aligns members across disciplines on a common goal, gives a bird’s eye view of the development, and helps build quality features.
Issue trackers are great when you want to track, well… issues. But if you want to go beyond simple issue tracking and build products and features, issue trackers just fall short.
Sure, issue tracking lets you wring a list of issues together and track them. But you can't get your team aligned and care about the feature unless you pester them with updates.
Getting your team to start tracking features instead of issues doesn’t force you to change your current process upside down. It’s simple and the easiest way for you to keep everyone aligned on shipping your feature.
The best part?
Irrespective of which process you use - scrum, kanban, or even simple task management - you can switch from issue tracking to feature tracking today.
Let’s jump in and see how you can do it step-by-step.
What happens when you bring every member involved in building your features together?
For most teams, it keeps everyone updated on everything needed to build the feature, show which discipline is working on which aspect, and keep all members aligned.
Now that you’ve brought members from every discipline together, you are probably wondering how the workflows would look like and how your team can move work forward.
Most tools oversimplify this into assigning specific tasks, adding deadlines, and having conversations with teammates. And when you’re working on solving some of the hardest problems, simple collaboration features aren’t going to cut it.
They forget that at the core of every team is a group of people who are different and have their own unique ways of working. So, when it comes down to getting everyone to work together on a feature, teams find it hard to adopt new workflows, collaborate, and handover work.
Zepel lets you add a board for each discipline involved in building the feature. That way, every discipline gets to work just the way they want.
When you need to see what’s happening in a specific discipline, you can simply open up their board and get a quick overview of their progress. And when a team needs to handover work to another team, you can move an item from one board to another by simply changing its status.
By now everyone involved in building your feature should be making progress either using their Board or from within a Sprint. But how do you make sense of all the updates they made?
You need to distil all the progress your developer, designer, and QA team made while building the feature.
With Progress in Zepel, you can go from tracking the status of a single user story to knowing how far away you are from completing an entire feature. That means no more outdated comments or endless meetings.
Irrespective of what process you use - you could run sprints, use kanban, scrumban, or even just a simple task management - with Progress in Zepel, it’s all there. In real-time. Across disciplines.
With feature tracking, your team is no longer working in silos without clarity. Now you can actually communicate everything needed to build the feature and finally deploy to production without hiccups.
Feature building is a team effort. You need to bring members from every team together to build quality features. With a Board for each discipline, not only can everyone work with a workflow they are comfortable in, but you get to view their progress with every update. And watch your feature come to life literally.
At Zepel, we shipped three features, fixed countless bugs, and redesigned our entire app in less than two months. And they weren’t even small enhancements!
Going from simple issue tracking to feature tracking let us ship more features to production without dropping the ball.
Knowing just the status of a single issue or user story is hardly enough if you want to take important decisions.
When you are a week away from deploying, you need to know if you’ll be able to ship to production on time, where your feature stands, and how far away you are. And Zepel gives you just that across every discipline.
As your team grows, the process you use to build features will change. You’ll switch from having a continuous deployment policy to running sprints and shipping features on a specific period.
But no matter what process you use or change to, you will always want to know the status of your feature. Zepel is process agnostic, so you can choose to run sprints or track on a kanban.