One feature of Conveyor that will benefit teams is visibility. Most agencies understand the pain of finding the best way to share the progress of a project with a client. So too for teams who have non-technical team members. How do you give people in these roles insight into your projects without confusing them or showing more than you want to?
Conveyor can help.
Keeping your customers up-to-date is one of the most important things agencies can do. It gives a positive impression and is a sign of how professional your team is. But providing those updates can suck up a lot of your time.
What if you could give the same insight without having to manually review your projects or ask your team for estimates? That’s what Conveyor will provide. Here’s how:
- As your team works on a project, Conveyor syncs all their commits automatically to our web app (and then to all other team members in the workspace)
- As tasks are finished, their status is also synced to the Conveyor web app
What does that mean? Simply this: a senior dev or project manager never has to go around to the team to ask teammates for status updates or to push their recent commits. They can log into the Conveyor web app to see the progress on a specific project. Or all projects.
Now, Conveyor is not designed to give time estimates. However, as each project is comprised of tasks, accurate status updates are available based on the number of tasks completed and tasks remaining.
As well, you can create a user account for a customer without hesitation. Your clients would be able to see all the projects your team is working on for them. If they’re curious how things are going with the new shopping cart for their online store, they can log in and see what’s up.
Teammates who are not developers
Agencies who are a little bigger also face this issue within their team. They tend have at least one person who is not writing code but requires insight into project status. Usually, this results in pain for both sides.
Project managers or those in charge of “business development” have to ask someone for an update. Or, a senior developer has set a recurring task to send out status updates once a week to all those who need it. And both those people have enough other tasks and responsibilities that this part of the process is a pain in the backside.
We designed Conveyor to make this easier for the entire team.
Task-based. Rather than having to guess at the name and purpose of all the branches in a repo, Conveyor is based on tasks. Each task can have a name that relates to the work the client needs, plus a description field that can include any necessary details. If a team lead has questions, they can ask them directly in a task with Conveyor’s comments.
One place to rule them all. Rather than have to review projects across various services, all the work your team has done is in one place. There is a clearly visible status for each project at all times.
These two factors make it easy for all members of a team to quickly get a sense of where things are at, regardless of their role.
We’ve stated one of the core purposes of Conveyor in this way:
Communication is a by-product. Instead of using multiple tools or steps, Conveyor conveys progress to your team as you work with your code.
Our tools should make our jobs easier, not more fragmented. Visibility into your projects is one way we want Conveyor to be a tool teams rely on!