Skip to content
PartPlay RoadMap
PartPlay
Teams and Budget
Functions and their work
18 Month Plan
More
Share
Explore
Hey Investor team,
I hope you are doing well. We created this Roadmap for the set of features below along with their priority.
We generally take into account the following factors before prioritising the features for the upcoming quarters:
Impact
Reach
Effort
Confidence
Complexity(Planning, Implementation, Execution, Testing, Iterations)
Backlog
Team Efficiency
Out of the various frameworks available, for these prioritisation, we brought into use the following frameworks
RICE: (Reach X Impact X Confidence)/ Effort
Impact/ Time Quadrant Method
⁠
Object not found!
⁠
⁠
Team Morale and Feature Parallel
Time
Weeks
Hours
1
Total Development Time
100
8000
2
Available Development Time
80
6400
3
Efficiency
85%
​
4
Effective Available Time
68
5440
There are no rows in this table
⁠
We have made the following assumptions for the ease of calculations, would get accurate results during the actual development phase and the marketing efforts:
Total current user base: 10K
Total user base within 4 months: 11K
Working efficiency of the team is 85%
The development time consists of: Planning, Implementation, Execution, Testing, Iteration
The feature for which user data is unavailable will be of low impact at the onset, not considering the role that the marketing team would play when or before the feature launch.
One week is: 5 working days, 8 hours each day.
Two people will be working in parallel on each task, so effective time take will or development time would be halved.
Work Allocation between teams
Team (Content, Product, Marketing...): 10%; for solutioning
Engineering: 70%; for core development and design
Team: 10%; for testing
Engineering: 10%; for iterations
Priority Calculation and Overview
1
⁠

Development results for the next 4 months

Commit: These are all the things we’re going to do. We’re going to write them down as our commitments
69 weeks, will cover all features up to P2; have taken into account additional buffer of a few weeks since complexity for 2 features is high.
Target: If we work at an efficient pace and all goes as planned, we’ll be able to achieve more.
83 weeks, will cover 1 feature of P3
Stretch: When push comes to shove, we know we’re worth it. If the users wants it, we can deliver it.
100 Weeks, will cover all features up to P3.
Work Promise
Pirority
Feature
Development weeks
Commit
6
P0
2
Ability for the users to add their own media and make it public, similar to YouTube's creator studio
27
Fix all known bugs of the backlog. Regression testing of login and subscription flow.
8
P1
2
Build a recommendation engine based on the preferences of the user to be set duing the onboaring process or in the My Profile section.
16
Add advanced rating pop up feature to get better and more ratings
4
P2
2
UI revamp of the Website and Mobile app; the current UI is almost 3 years old.
6
Enhance the accuracy of syncronisation by 10% for a better listening experience.
8
Target
1
P3
1
Support multiple languages - Marketing is pushing hard for this
14
Stretch
2
P3
2
Re-invent onboarding - It’s been 1 year since last update and conversion has not really improved since
8
Introduce animations in all the onboarding screens
9
⁠



Priority Calculation and Overview
Development results for the next 4 months
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.