02 Jun Scrum Foundation: Sprint Planning
In today’s Townhall, it’s all about sprint planning. Tom Secuya already touched some details about the other aspects of scrum. Today, it’s all about building from the ground up.
How to Plan a Sprint
A simple illustration of sprint planning is similar to learning a new skill. Whether bicycle riding or playing a new instrument, it’s similar to sprint planning. No one is exceptionally good in the first few tries. But with consistency and time, it becomes easier to manage and sprints gets easier to implement.
What a Sprint Does
The sprint is essential to making work visible. In order to assess whether the product or output is successful, it should be measurable and manageable. These are the two factors that makes work visible through execution. In creating a Scrum, there’s a timeline to it to make it more measurable. `
In creating these stories (tasks under Scrum), there are still some mini-decisions that only the product owner can answer. In the client-VA relationship, there are some tasks that only he or she will be able to answer.
What Happens During a Sprint
In a literal sense, this is the fastest speed a runner will run for a certain period of time. With work, it’s the fastest way to get results in a limited period of time. With sprint, you can do tasks faster and get clearer instructions.
Importance of Sprint Planning
The team decides on which projects that needed to be ‘sprinted’ on. From here, the team then breaks them down into smaller tasks where roles are assigned. This is the foundation on which the scrum will be based on.
Here are Three Things Needed to Planning a Sprint:
a.) Create User Stories
User stories are the tasks placed on the scrum. The end user of these stories are the client’s or the clients’ clients.
b.) Assign Value to Each Story
In the previous talk, tasks are categorized by shirt sizes (S, M, L and XL). From here, the projects are broken down into smaller pieces that the team can sprint on. During this phase, a story may have several associated tasks and drawing estimates for a release will be discussed during this time.
c.) Assign roles for the story
Once the tasks are broken down for ‘sprints’, roles are then assigned for the tasks.
Question: Is it okay to assign roles to a client? The answer is yes.
There are certain things (e.g. passwords, contact details, accounts) that only the client knows.
Sprint planning is a crucial phase of scrum. It’s important that clients and VAs know how to plan using this method to be ablet to deliver quantifiable results thus making work visible.