Step 4.2: Manage resources and ongoing product delivery

Manage resources and ongoing product delivery

Now that you’ve set up a clear system for managing projects, sprints, and tasks, you’re ready to support your team’s needs as they build and deliver new features. 

Visualize every task across your team

As you’re assigning tasks, you also want to have a plan in place to showcase high-level resource allocation by person for sprint planning purposes. Here are a few helpful ways to visualize your tasks.

1. By sprint

This grid view allows you to see all tasks grouped by sprint, to easily see all the tasks that need to be completed within a given sprint.

2. By project

This grid view allows you to see all tasks grouped by project, to easily see all the tasks that need to be completed by project.

3. By status

This kanban view categorizes tasks by status, and is a helpful tool that can be used for daily scrums or sprint reviews to discuss tasks and work in progress.

4. Task dependencies

This Gantt view highlights task dependencies for a given project or sprint, which include specific sub-tasks or commitments that are dependent on each other (like specs, code review, code complete, etc.) 

A Gantt chart visualizes a schedule of activities, like tasks or projects, over time horizontally. And with the use of arrows, it also shows you how different activities depend on each other. To designate task dependencies in a new Gantt view, try linking records within the same table.

Use automations to keep work on track 

Automations are a useful way to streamline custom workflows based on conditions. They allow your team to automate repetitive tasks and can be incredibly handy for keeping work on track. 

Here are a few common ways we see teams creating automations to manage product delivery between stages. Click the “Automations” panel to play around with these automations in the team-level reference base.

1. Sprint reminder automation

You can create an automation to notify product owners when a new sprint is on the way so they can prepare accordingly, as well as solicit updates as the end of a sprint is approaching. DRIs can be notified according to their preference, whether it’s through an email or over Slack or Microsoft Teams. 

2. Approval and review automations

Another common use case is to automate reminders to cross-functional DRIs, asking them to provide feedback and approvals of work, or to share out key decisions between product stages.

Create a holistic view of sprint progress with an interface

Another way to stay on top of ongoing delivery is to create a custom interface to collect and curate information on ongoing sprint status, as well as current sprint commitments and updates.

This is a great way to provide curated versions of information, as well as solicit updates from DRIs. Note that this information can also be customized to be specific to the logged-in user.

In this “Sprint Planning” interface, we’ve highlighted key details such as:

With these tips in place, your team can focus in on getting their work done, and the right parties can stay informed—no extra communication needed. In the next step, learn how to streamline tracking sprint progress across your entire organization.