How product managers use Zepel
Product managers take the big picture, distill it into features, break and prioritize them using user stories.
Since product managers work with every team, being able to quickly see what each team is working on and know what’s happening with the feature is key to plan and prioritize for the road ahead.
In this article, we’ll see how a product manager uses Zepel to effortlessly keep track of all the features, prioritize, and work with multiple teams.
1. Create a Project for your team
As a product manager, you’d want to bring all the features your team will be working on under one single project.
A project in Zepel is usually a team, like Engineering. But if you choose to name your project after a product or an initiative, such as Web App or Android or iOS, that works too!
Since you’ll require items to go through statuses to keep everyone updated of progress, you can choose to add one or more Boards while creating your project. Not to worry, you can add them from within the project too.
2. Create a Feature and add items
A Feature houses all actionable items - user stories, tasks, subtasks, bugs, and enhancements - for a specific feature.
Adding items for your feature is as simple as writing on a document. Simply hit enter to create another item. And press
Cmd + Shift + S if you’re on a Mac (Ctrl + Shift + S on Windows) to toggle between item types.
Use Descriptions to add more details to each work item. For example, product managers use description as a place to add acceptance criteria for user stories and attach files below it to share files for further references.
3. Collaborate with the team to get an estimate for your feature
Once you’ve added user stories and enhancements for your feature, bring in the rest of the team to estimate and understand the complexity involved in building the feature.
Have contextual conversations on each work item and get your development team to break down each user story into subtasks.
Breaking down user stories into subtasks helps your team clarity and understanding of what they’ll have to build and hence will be able to add estimations with better accuracy.
4. Prioritize key user stories with Hashtags
Now that you have a rough estimate of how long each user story will take to get built, its time to prioritize them.
Use the advanced filters to slice and dice all items. Sort your items by Estimate and start adding hashtags
# to denote priorities.
That way, you get to know what key areas of your feature needs more attention and delegate it to team members appropriately.
5. Track progress of the feature and plan for the road ahead
Give each Feature:
- An owner who will oversee the specific feature
- A duration to ensure the feature is built within a said timeline, and
- A status to keep everyone updated on progress
As your team makes progress, you’ll see a quick overview of how much work is done. And of course, you can always get a deeper understanding of the progress with reports.
As you add more features to your project, use the Table view or the Kanban view to prioritize and plan your future features.
Ready to plan and prioritize features effortlessly?