Product Development

The main effort should be to transform the Roadmap into actual development and delivery
First, define the product’s Epics which are the main areas of the product (from the product’s perspective and not from a technical perspective)
Each feature should be decomposed into User Stories which should be placed in the Product Backlog
The Product Backlog is usually comprised out of new features, improvements of existing features, bug fixes, and technical debt
Decide on priorities based on the current situation and feedback (for example, at times there is a need to focus on fixing bugs in order to stabilize the product and reduce user complaints or focus on technical debt in order to better structure the product and improve development time)

The User Story should be defined as: As a <user role or persona> I want to <perform some action> so that <I will achieve some goal>
The User Story should focus on the specific persona, what it wants to accomplish and especially why is this important
Each User Story should be opened as a ticket in the Ticket management tool
The recommended structure of the User Story ticket should be:
- User Story - as defined above
- Impact - explain how this will move the needle and how to verify it
- Requirements - a detailed explanation of the solution, including the details of the UX and UI, and addressing all relevant scenarios (both “happy days” and “non happy days”).
  - Good UI/UX focuses the user’s attention and reduces cognitive overload
  - Use a Product design tool
- Acceptance Criteria - what will be considered as a successful implementation
Each User Story should be associated with a specific Epic
Each User Story should be assigned with a business value score which should be based on the impact of that User Story
Each User Story should be assigned with an effort by RnD (also known as Story Points)
Each User Story should be assigned with a Priority by the Product Manager which should take into account the business value and the effort