01 Jun Carve GA: How Scrum Makes Work Visible
As previously discussed by Tom Secuya, Scrum has already been implemented by some departments in Carve and has gotten significant results. But before going deeper to the roles and activities, let’s take a step back and understand the ‘How’ of this process.
What is Scrum?
Scrum is part of an Agile movement. It’s predominantly used by programmers and their teams in developing software through releases of projects. This is in response to various project management systems (such as the Waterfall Method) using 4 values and 12 principles. With Agile, the emphasis lies heavily in communication, collaboration and self-organization among the team that can adapt to the changes in the business.
Compared with lengthy time duration to get results, scrum ‘trickles’ these results. Time is divided into short periods, typically known as ‘sprints’, in one or two weeks span. However, this will vary per team and the type of project to be done.
Assigning roles with corresponding responsibilities and meetings are constant. Constant collaboration and meetings lessens the unpredictability and speculation to leave room for improvements and discovery. These incremental releases are then sent out to the user (product owner or client’s clients).
The Scrum Ceremonies
These are the processes being done in the Scrum:
a.) Sprint Planning
c.) Sprint Review
d.) Sprint Retrsopective
Sprint Planning is a run for execution. In this session, the product owner, scrum master and execution team plan on how to go about with the projects on hand. They itemize these into small, medium, large and extra large projects. From these projects, they then break down specific tasks and assigned to the people fit for the job. The product owner would be the one to decide on projects needed to be sprint on.
Sprint is the actual work of the project. During this period, the execution team will focus to work on this specific project and deliver it in a given period.
Sprint Review meetings are held when an output has already been produced. During the meeting, the scrum team, customers and management meet up and talk about what they’ve done during the sprint. The project is then assessed with the sprint goal pre-determined during sprint planning.
Sprint Retrospective is when the team have their session and review what worked, what didn’t and what needs improvement. This is a good way to assess if the sprints were effective or needed more time to polish.
Standups are daily meetings within the team to talk about progress, tasks done, future tasks and stucks. This is to eliminate delays in making decisions to get traction to finishing a project.
What are the processes involved with Scrum?
Also known as the Sprint Backlog, this is where all the ‘future projects’ are placed. From the previous discussion, it was mentioned that tasks are being broken down into ‘chunks’ and deliver results in a given period of time. These are usually in the form of stories or identified tasks needed to complete a story.
Here’s a video from Axosoft Introducing the Scrum Method:
This is the introductory details for Scrum and the activities involved in using it. Not only will this make work visible, it also organizes the team and gives out satisfying results, less miscommunication, more collaboration and improvement.