10 Jun Scrum Method in Action: Materializing a Sprint
In last week’s Townhall, Tom Secuya discussed about an integral part of scrum method called sprint planning. Today, is scrum in action: create a sprint plan, assign roles and doing sprints.
As a starting point of scrum method, VAs are grouped and were asked to have a project in mind and create a sprint plan for the selected project. Everyone brainstormed on how to put into action the projects and create a plan (sprint planning) out of that project.
Stories were created out of those projects and roles are assigned for each member. VAs are given a brief introduction to the terminologies and importance of roles assigned to each member of the team.
During the discussion, team leaders presented the project and asked the members for possible items and/or activities needed for it to materialize. During this time, they were able to discuss the process of sprint planning.
Initially, sprint planning is broken down to ‘stories’. In the early phase of the scrum method, the breakdown is creating smaller tasks to bring clarity of tasks involved in a specific project. Once the breakdown is done, it is then categorized to its size: S, M, L, XL (this is discussed under the ‘4 buckets’ in the previous Town Hall). Then, members are asked to select a certain role (or roles) to specific tasks.
During the discussion, as roles are assigned and everyone has polished their projects, daily standups were discussed. Varying groups have varying timelines for their standups. This is a daily meeting to ‘literally’ meet with the team and update on tasks they have for the day and stucks encountered. This is a great way to keep the flow of work running smoother than just a weekly meeting.
As VAs are planning on how to go about the project, team leaders placed all other projects in the backlog. This is the list of projects that are yet to be done. If a project has already been done, product owners would just pick a project that are ‘high priority’. This is a great way to counter the usual ‘stacking’ to maintain.
This is the person that owns and picks the projects that he or she wanted the team to work on.
In the scrum method, a scrum master plays an important role. These are the people in charge that handles the meetings and make sure that tasks are ‘freely flowing’. If the person encounters a stuck because of a certain activity or requirement needed from another team member, the Scrum Master is the one that makes sure that these roadblocks are remedied as soon as possible.
Sprints are the planned duration intended for specific tasks to be done. Not only will results materialize as expected, it makes the output visible.
It’s the transition of a shippable product into a routine for the end user (in this case, the product owner). Releases are products of sprints.
Major Takeaways for this scrum method activity:
- In sprint planning, it’s important to identify the releases and stories of each release.
- Identify and assign values per releases/stories
- Delegate owners of releases/stories