Scrum is simple; it consists of six time boxes (one of which is optional), three roles, and three ‘official’ artifacts. A sprint, the first of the six time boxes, is an iteration defined by a fixed start and end date; it is kicked off by sprint planning and concluded by the sprint review and retrospective. The […]
As a Scrum Master one should know that preparation of the backlog and the Product Owner’s role in it is very important. With that in mind, a Scrum Master should assist the product owner in the following ways:
- Ensures that the product owner is maintaining the product backlog—knows where to keep it, the appropriate frequency, and depth of updates.
- Helps the product owner write product backlog items and acceptance criteria if needed.
- Encourages a visible product backlog to which everyone may contribute
- Includes the product owner in all Scrum meetings
- Reminds the product owner of the value of grooming sessions and offers to schedule and facilitate these discussions
- Brings the product owner together to directly discuss implementation issues and ideas with the team.
- Influences the product owner to test/accept the team’s sprint features as soon as they’re complete, not waiting until the end of the sprint to see new functionality.
- Encourages the product owner to share important business collateral with the team (product vision, roadmaps, and so on) and assists in preparation, if needed.
- Reminds the product owner to prepare the backlog for the next sprint cycle.
- Regularly checks in and offers assistance to the product owner.
You might be interested in the following courses:
A ScrumMaster must have a deep understanding of the Scrum framework. The job of a scrum master is to help the customer and the team to work very closely ensure expected deliveries. Scrum Master facilitates the team members to reflect upon ways that they can improve their day-to-day communication and processes. It is the responsibility […]
Agile Methodology refers to the software development methodology that is centered around the idea of iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The various Agile Methodologies share much of the same philosophy, many of the same characteristics and practices. But from an implementation standpoint, each of these methodologies has […]