Share
Explore
Rayyan Operational Cycle Setup
To improve coordination between teams and speed up delivery, we will follow a clear and structured plan
based on Scrum.
The product team will be organized into focus area squads, each owning a specific part of the product, while the development team will work as one unit using a shared board using sub-tasks and labels .
We’ll connect the product and development work through two linked Azure DevOps boards and use story points to estimate tasks.
This setup will ensure everyone is aligned, features are fully prepared before development starts, and the entire team follows the same sprint schedule with regular planning, reviews, and continuous improvement.
Workflow
From Product Board (PM)
Product planning board (Features)
Backlog
Ideas
In discovery
Design in progress
PM review
Ready for user stories
All ideas and Enhacements
ICE score
PRD (Tchnical feedbak + Wireframes)
High fidelity
Accept disgn
Refine with Tech and set an initial estimation to be ready for Dev
There are no rows in this table
Product planning board (Stories)
Writing user stories
VP Review
Ready for refinement
Writing user stories with adding design link (High fidelity
VP Accept user stories with acceptace critria
Fully refined user story
There are no rows in this table
When the task is refined and ready to be developed it will be sent to the engineer's board
To Dev Board (Engineer-owned)
To do
in progress
Code review
Ready for QA
Testing on statging
Ready for Deployment
Deployed
There are no rows in this table
Scrum Events
Table 1
Event
⏱️ Duration
📆 Frequency
🎯 Objective
Sprint Planning
2 hours
Biweekly (Monday evening)
Align dev & product squads, validate estimate with graping from backlog
Daily Stand-up
15 minutes
Daily (Sun–Thu)
Share updates, unblock issues, stay aligned as a dev unit.
Backlog Refinement
1 hour
Weekly (Wednesday)
Ensure stories are clear, estimated, and prioritized.
Sprint Review/Demo
1 hour
Biweekly (Sunday)
Demo completed features and gather feedback from stakeholders.
Retrospective
45 minutes
Biweekly (Sunday)
Reflect on team performance and identify improvements.
Product Squad
1 hour
Weekly (Tuesday)
PMs + Designers align on designs, priorities, and roadmap flow.
There are no rows in this table
Estimation Method: Story Points
We’ll use Story Points for estimating tasks during sprint planning.
Why Story Points?
Planning Poker
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.