Blog Archives

The Scrum framework is driven by the goal of delivering maximum business value in a minimum time span. One of the most effective tools for delivering the greatest value in the shortest amount of time is prioritization. Prioritization can be defined as “Determination of the order and separation of what must be done now, from…

Well, a User Story is basically what the user is required to perform as a part of his job responsibilities. It gets the data of who, what and why pertaining to a prerequisite in a simple and conscience way on a note-card made of paper. User Stories are written by or for the business user…

A Scrum master plays a crucial role in the implementation of Scrum on software development projects. Click here for the Challenges faced by a Scrum Master A Scrum master is like a leg in the tripod of the Scrum team, with the other two being the product owner and the development team. The relationship of the…

A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge (SBOK™). After the Plan and Estimate phase comes the Implement phase. This phase includes three processes related to the execution of tasks and activities—creating various deliverables, conducting Daily Standup Meetings,…

A Scrum project often goes through a number of phases. Five phases, composed of nineteen processes, are suggested in A Guide to the Scrum Body of Knowledge (SBOK™). The Release phase is the final stage of a Scrum project. This phase includes two processes that emphasize delivering the Accepted Deliverables to the customer and identifying, documenting and…

Before we read about how to be an effective product owner, let us first understand who a product owner is and what he/she does. A product owner is not a separate title but is a role that can be performed by a business analyst or even a representative of an end user. A product owner is…

The fundamental Scrum processes defined in SBOK Guide by SCRUMStudy are valid for all Scrum projects, and concepts mentioned in the SBOK are sufficient for managing Scrum projects with just a few Scrum Teams, typically 1 – 3 Scrum Teams. When we deal with large projects generally involving four or more Scrum Teams, some additional…

The term stakeholder creates a lot of confusion in Scrum. Usually the term is confused with the responsibilities of a Product Owner. Let us now clear all the confusion around it. Best definition of stakeholders is that they have legitimate interest in the project and another important point to be noted is that stakeholders are…

Scrum Team, also referred to as the development team, is responsible for developing the product and they possess all the essential skills required to carry out the work of the project. They have a high level of collaboration to maximize productivity, so that minimal coordination is required to get things done. To minimize dependency, team…

Scrum believes that employees are self-motivated and seek to accept greater responsibility. So, they deliver much greater value when self-organized. The preferred leadership style in Scrum is “servant leadership”, which emphasizes achieving results by focusing on the needs of the Scrum Team. Benefits of Self-Organization Self-organization as an essential principle in Scrum leads to the…