Getro Product Meetings
Prioritize, manage, and "groom" your team's tasks during a product meeting with this doc. Associate product requirements and releases with tasks.
RN
Raul San N.H.
on how to use this template.

Product meetings at
use a system of grooming and prioritizing tasks. Some parts of this doc can be used
during the meeting
and other parts can be used
outside of the meeting
. You can add requirements for your next product release and associated tasks for those releases.

At
, we like to prefix Requirements with a “R,” so you’ll see requirements with “R3” or “R5” before the requirement name. This is a formulaic column so that it’s easy to reference that requirement when you are discussing them during and before/after the meeting.

Grooming tasks

During the meeting, we select a product release from a dropdown and view all the requirements and tasks associated with that release. Since the
Tasks
column is a formula, we can add tasks to this column by simply clicking a button in the same table and a new task gets added to the
Tasks
column. This process allows our team to “groom” requirements and tasks so that we are doing everything we can to launch a successful release of the product. The
product owner
is in charge of defining the requirements for each release, and this is done in the
Requirements
section
outside of the meeting
.

Prioritizing tasks

Prioritizing tasks during a product meeting is important because it helps our team to figure out exactly what to work on. This is a more granular view of our tasks and we assign a priority (from 1 to 5 stars) as well as the
Type
of task and the
Owner
. Some tasks are mundane chores while others can be features and bug fixes. A
Status
column is updated by the task owner so that the whole team knows where we stand with a specific task.

The filtered views of the main tasks table allows our team to see which tasks are blocked, done, in QA, and currently being worked on.

Running product meetings at Getro

Product meetings at
use a system of grooming and prioritizing tasks. Some parts of this doc can be used
during the meeting
and other parts can be used
outside of the meeting
. You can add requirements for your next product release and associated tasks for those releases.

At
, we like to prefix
with a "R," so you'll see requirements with "R3" or "R5" before the requirement name. This is a formulaic column so that it's easy to reference that requirement when you are discussing them during and before/after the meeting.

This doc consists of a few main sections:

When to use
Section
Description
During Meeting
All team members view this section to add tasks for a given requirement/release during the meeting
A separate meeting to assign a priority to tasks
Before/After Meeting
Add requirements needed for each release; done by the product owner
Task Views Folder
Custom views to see tasks that are
,
,
, and

From maker Raul San Narciso Holguera

CPO and Co-founder,

Goggle 320 X 132.png
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.