In Scrum, quality is defined as the ability of the completed product or deliverables to meet the Acceptance Criteria and achieve the business value expected by the customer. To ensure that a project meets quality requirements, Scrum adopts an approach of continuous improvement whereby the team learns from experience and stakeholder engagement to constantly keep…
The product owner is an important part of a Scrum project. He/She represents the interests of the stakeholder community to the Scrum Team. The product owner is responsible for ensuring clear communication of product or service functionality requirements to the Scrum Team, defining Acceptance Criteria, and ensuring those criteria are met. In other words, the Product…
Isn’t it important that each person working in a scrum project know exactly what he/she should do? Undoubtedly, yes. There should be a clear understanding of defined roles and responsibilities to ensure the successful implementation of Scrum projects. Scrum roles fall into two broad categories, Core Roles and Non-core-roles. Core Roles—Core roles are those roles…
The purpose of the Quality aspect is to define quality as it relates to projects and to present the Scrum approach to achieve the required levels of quality. Quality, as defined in the Scrum Body of Knowledge (SBOKTM), is applicable to the following: • Portfolios, programs, and/or projects in any industry • Products, services, or…
As we know, organization is one of the Scrum aspects that must be managed and addressed throughout the Scrum project. It deals with the roles and responsibilities in a Scrum project, which is very important if we want to successfully implement Scrum. So, we have to learn the various facets of a Scrum project organization…
How does Scrum deviate from tradition? The emphasis in traditional Project Management is to conduct detailed upfront planning for the project with emphasis on fixing the scope, cost and schedule – and managing those parameters. Traditional project management may at times lead to a situation where the plan has succeeded yet the customer is not…
How to focus on value creation? The Scrum framework is driven by the goal of delivering maximum business value in a minimum time span. To achieve this practically, Scrum believes in iterative development of deliverables. In most complex projects, the customer may not be able to define very concrete requirements or is not confident…
How to ensure your team does not have too much or too little to do? Scrum treats time as one of the most important constraints in managing a project. To address the constraint of time, Scrum introduces a concept called ‘Time-boxing’ which proposes fixing a certain amount of time for each process and activity in…
Scrum methodology requires a change in mindset from traditional methods. The central focus has moved from scope in Waterfall methods to achieving maximum business value in Scrum. While in Waterfall, cost and schedule are altered to ensure the desired scope is achieved, in Scrum, quality and constraints can be altered to achieve the main objective…
Scrum processes address the specific activities and flow of a Scrum project. In total there are 19 processes which are grouped into five phases. Please take a look at these processes and the activities listed under to them in order to understand the flow of a Scrum Project better. Initiate Create Project Vision—in this process,…
