We are used to create multiple sub-tasks for each user story and provide each sub-task with an estimate in hours and assignee (back or front-end).
With the following outcome:
- Total estimated time needed in hours for user story divided over back and front-end
- The availability of both back and front-end developers can be taken into account when user stories are placed in sprints
- Developers are scheduled accordingly in Harvest Forecast based on their availability and back or front-end role
Despite, we are unable to provide an accurate estimated time. That is why we want to adjust our project management:
- Estimate user stories based on story points instead of hours
- Estimate no more sub-tasks, only the user story
- Switch to Trello or Jira instead of Redmine
- Planning to do more Scrum activities
- Daily stand-up
- Sprint review
- Estimate story points for user stories with entire team
When we apply all this, we will most probably achieve a more accurate total estimate for a sprint and plan a feasible amount of work in a sprint based on the velocity.
We only have one problem. If we no longer use sub-tasks for the estimation, we also do not know how many hours a back or front-end developer needs to be scheduled in Harvest Forecast.
Hence the question: how to schedule back and front-end developers based on story points?