The Product Owner acts as the voice of the Customer and they are accountable for delivering Value to the Business.
The Scrum Master is accountable for removing impediments, enabling the Development Team to focus on delivering the Product Goals and deliverable's.
The Development Team is responsible for developing the product. They work on the product requirements defined in the form of User Stories
Impediments are barricades, hurdles or obstacles and these are recorded in Impediment Logs. In terms of Scrum, they are “blockers” that prevent the Scrum Team from completing work, which in return impacts velocity. Anything that prohibits the team from doing work is considered an impediment and should be included within impediment logs. Examples of Scrum…
Implementing Scrum Programs Scrum Programs represent a collection of related projects. The objective of a program is to produce business results as they have been identified in the Program Vision Statement. The Prioritized Program Backlog includes Product Backlogs for every project within the program. Scrum at the Program level includes five (5) high-level processes. Create…
The purpose of User Story prioritization in Scrum is to determine which user stories deliver the greatest amount of value to the customer. The items that are selected for the Prioritized Product Backlog undergo specific techniques to determine their levels of value. A discussion within the Scrum Team (Scrum Master, Product Owner and Development Team)…
Agile Planning Essentials Agile Release Planning involves quantifying the pace that a team can develop user stories into working software. The team’s velocity is the measurement of its throughput which is used to establish expectations regarding future delivery dates. To establish delivery dates, we examine the total amount of work for the project and divide…
Planning for Uncertainty How do Agile Projects help when Planning for Uncertainty? Agile projects often have a high degree of uncertainty; namely there are absent features and time estimates that have a high probability of adversely impacting the business. To avoid a negative impact, estimates should be buffered to reflect levels of uncertainty that are…
The Scrum Guidance Body (SGB) typically consists of a group of professionals that define the set of standards that pertain to quality, government regulations, and other important organizational considerations. The standards are developed to provide guidance for the Product Owner, Scrum Mater and the Development Team. The Scrum Guidance Body (SGB) is also responsible for…
What are the Agile Leadership Styles? With Agile Methods, leadership styles are diverse and based on organizational specific environments, goals and the human resources on the Scrum project. While many of us are fully aware of the term Servant Leadership, there are other leadership styles that are also relevant. A discussion follows on the variations…
How can you go about Optimising Product Delivery? You may think the focus of this article is going to be on how to Manage the Product Backlog? Or maybe how to speed up Sprints? These are necessary activities to deliver a Product. However, the foundations for getting a successful Product are laid long before defining…
Why Planning Fails and Why Agile Planning Works What are the Agile Planning Benefits and why does Agile Planning work? Producing the Plan for a Project has always been among the key activities undertaken by the Project Manager. The complexities of what has to be Done, by whom, and when are itemised and arranged in…
How do the Scrum Team begin Estimating User Stories and Tasks? While Scrum does not follow Traditional Project Management guidelines, there are some Estimation activities around the Work to be Done. Estimation is Done for:-. User Stories, which are subsets of the overall Requirements, and. Tasks, which are the activities that need to be completed…