Creating Tasks for Scrum Masters
According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a Scrum Master, your job is to help your team become self-organizing, and thanks to the Scrum framework, you have what you need to help the team own their tasks in the project.
The Product Backlog
Everything a Scrum Team needs to work on is in the Product Backlog, which is simply a list of the things users and customers want from the product, grouped by epics, features and user stories. A popular format of recording a product backlog item (PBI) is writing down user stories: “As a (user role), I want to (describe action here) in order to (describe value or desired output here).”
A good PBI is understood by everyone: they know what its objective is, what the desired outcome is, and what level of complexity and feasibility it has. The team can opt to use an online tool to manage PBIs or a physical board with swim-lanes – whichever is more manageable. Ensuring that these characteristics are followed will help the development team have a better picture of what they need to do.
Sprint Ceremonies
While the Scrum Master can coach the team at any point during the project, the Sprint Ceremonies are the most important activities in the timeline and also the best venue for managing the work to be done. This is where the team inspects the work done and adapts to changes for upcoming work. While each ceremony has different purposes, they all have an impact on what tasks the team will accomplish.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: