Looking for Answers?
Browse our articles to find the answers you need
Status, Planning & Road maps
Our planning is done by gathering information from different groups and management requirements and needs.
We compile all requirements into one list. In this list we try to understand the scope of the project, its urgency and its source of demand. Through this list we prioritize projects.
We compile all requirements into one list. In this list we try to understand the scope of the project, its urgency and its source of demand. Through this list we prioritize projects.
Backlog & Planning
Our backlog and priorities are set according to this Monday Board.
In this list we do not manage tasks, only projects. Whenever we find a new project to be done, we first update this list, and only then move it to continue execution in Jira.
In this list we do not manage tasks, only projects. Whenever we find a new project to be done, we first update this list, and only then move it to continue execution in Jira.
Major task (Epic) plan is prioritized based on:
- Urgency from our team or vertical
- Insights from product reviews and research
- Management strategic change
Tasks are created based on product team requests or product reviews.
New requests
New requests from external teams can be registered using this Google Form.
Execution and monitoring - Jira
Once we have collected all the information, each project opens in Jira and from there you can follow it and understand its status until the development is completed.
Jira is used by us for all stages, everything from backlog to release. The main goal of working with one tool is better communication, uniform visibility for all tasks and full sharing with developers.
All our project/tasks are defined in Jira backlog. Some tasks are small, large tasks are created as epic, which have subtasks.
Jira is used by us for all stages, everything from backlog to release. The main goal of working with one tool is better communication, uniform visibility for all tasks and full sharing with developers.
All our project/tasks are defined in Jira backlog. Some tasks are small, large tasks are created as epic, which have subtasks.
Sprints
Each epic is split into subtasks (e.g.: research, design, zeplin spec, development or other).
Subtask prioritisation happens in this order:
Subtask prioritisation happens in this order:
1. The tasks are prioritised by Shlomi, Ayelet and Domas before the sprint planning.
2. Assign tasks in the sprint planning (biWeekly Wednesday)
3. Completed tasks are presented in demo day (biWeekly Thursday)
Building the Roadmaps
The roadmap is set of 4 quarters each quarter consists of a set of prioritised epics.
It provides a strategy and plan for product development. Roadmap is based on long-term product team goals and need to communicate the process for how to achieve those goals.
Roadmap should focus on:
It provides a strategy and plan for product development. Roadmap is based on long-term product team goals and need to communicate the process for how to achieve those goals.
Roadmap should focus on:
- User needs while solving meaningful problems
- Incorporate key people- PM needs to include: costumer feedback, engineering, company vision and product strategy
- Communicate simple and easy to understand roadmap - goals and development mile stones. Don't need to be included: backlog list, bugs etc.
- Reflecting team contribution effort for company quarterly/yearly goals.
Product roadmap reduces uncertainty about the future and keeps product teams focused on the highest priority product initiatives.
Key elements the roadmap follow:
- Product strategy
- Product goals
- Which features should be focused on
- Timeline for new features
- Responsibilities
Reflect projects planning
Reflecting the plans of the projects should be accessible to every member of the team. here we reflect the projects planning in high level to see when product is done and when development starting. you can see it in the link here.
Was this article helpful?
