Nothing like going a long time in between posts, but I recently started a new job and taking everything in has been exciting, but it has also taken a lot of my free time. But I think things are on track now and the good news is that as a Project Manager in a digital solutions agency, I hope to be able to continue to share thoughts here on project management, methodologies and best practices as I go about my daily work.
This post is more of a continuation from last time and I may add one more after this. Or should I just be honest and say when I get time next to add to it? Let’s go for the honest answer!
But I did want to wrap up with two other important scrum terms, the Sprint Backlog and the Definition of Done.
The Definition of Done (DoD) is actually a main concept behind the scrum. It contains the exit criteria to determine whether the product backlog item is complete. Everyone must agree with what “done” means, even before the work begins.
The Sprint Backlog (much like the Product Backlog) is a prioritized list of tasks from the product backlog that need to be completed during a specific sprint. It includes a plan for how to achieve the sprint goal, and only the dev team may update the sprint backlog during a sprint.
Now on to some more details about the Scrum Team (the Core Team):
- The Development Team – This is a cross functional group of people responsible for building the product in deliverable increments or iterations (the sprints). Usually this is less than 10 people, but depends on the scope of the project. The dev team is responsible for estimates, work capacity and technical decisions.
- The Product Owner (PO) – This is the person solely responsible for maximizing the value of the product the dev team creates. The PO manages and prioritizes the product backlog as well as constantly keeping in mind interests of the stakeholders.
- The Scrum Master (SM) – This is the person responsible for ensuring the Scrum process is understood and used correctly. They are often referred to as “servant leaders” for the dev team where they facilitate, coach and remove barriers the team may encounter.
There are two broad categories of roles in this Agile environment.
- The core team – the PO, the SM and the cross-functional dev team.
- Non core-roles are the stakeholders, vendors etc.
The scrum framework is adaptable to small or large projects. The larger the project, then more than one cross-functional team is used.
That’s a nice basic overview between the last two posts on this topic. I believe next post I will hit on the scrum principles and then put it all together by a quick outline of the scrum process as a whole.