Welcome to the second sprint planning in the series. With the lessons learned from the last sprint, I’ll attempt to plan for the next sprint more accurately. We’ll do backlog refinement, planning and define our goal for the sprint and the deliverable we want to have by the end of it. Let’s get started!
For those that haven’t been following us since the beginning go check out the introduction post to find out what this whole series is about! 😉
Alright, let’s start with our scrum board - we’ll keep using Trello, because of its drag and drop simplicity and various integrations.
As you can see, this is the board as we left it after our review. In order to move further, we need to do some refinement:
- Remove tasks from done and freezebox
- Re-evaluate the effort of the tasks in the pipeline
- Move undone tasks from the sprint back to the backlog
- Add technical debt tasks
- Add any subtasks that arose after the review
So let’s get started with the refinement!
As you can see, I have changed values for various tasks, due to previous experience with deploying the in-house PHP framework. Now you I’ve completed the refinement part and planning can begin. The next sprint will have 9 days of work. So we need to find the ideal amount of work to be done.
As mentioned in previous planning, we are using the t-shirt size method - S/M/L meaning:
- Small (= an hour of work)
- Medium (= a half a day of work)
- Large (= a day of work)
So back to our knapsack problem, but in fact the logical order of the tasks dictates the order in which they should be done. Only some tasks can be interchangeable in the order.
There, I think that’s about it. The main focus is clearly the API services:
|Deploy Auth Service to single VM||Ops||Large|
|Create git repository for Billing Service||Ops||Small|
|Create container for Billing Service||Dev||Large|
|Create DB for Billing Service||Ops||Medium|
|Deploy Billing Service to single VM||Ops||Large|
|Create git repository for API Service||Ops||Small|
|Create container for API Service||Dev||Large|
|Create DB for API Service||Ops||Medium|
|Deploy API Service to single VM||Ops||Medium|
|Create git repository for Data Eater and Data Feeder||Ops||Small|
|Create container for Data Eater||Dev||Large|
|Create container for Data Feeder||Dev||Large|
Total: 7.8 man/days
So, that’s all for the planning, ready for action (again). But let’s hear from you now - How do you do your sprint planning? Do you do backlog refinement in a separate meeting or do you do it as part of sprint review? Let me know on any social platform - facebook, twitter or instagram!
This post is a rewrite of the contents of the video that was published on YouTube and Facebook! 😎