SCRUMstudy - Accreditation Body for Scrum and Agile;Download Free Scrum Body of Knowledge(340 pages)

New blog articles detected

  • Release Planning Sessions in SCRUM

    Release Planning Sessions are conducted to develop a Release Plan. The plan defines when various sets of usable functionality or products will be delivered to the customer. In Scrum, the major objective of a Release Planning Meeting is to enable the Scrum Team to have an overview of the releases and delivery schedule for the product they are developing so that they can align with the expectations ...

New blog articles detected

  • Various Dimensions of Team Specialization

    In a large SCRUM project, Team Specialization may be required. There are three dimensions of Team Specialization. The first dimension is the need for accomplishing specific tasks. For example, one Specialized Team might be an integration team that has specialized knowledge of continuous integration.. That knowledge could be especially important when and if there is a Release Readiness Sprint. The ...

New blog articles detected

  • Who is a Product Owner?

    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 a stakeholder who acts as an interface between the business representatives and the project team. A product owner...

New blog articles detected

  • Maslow’s Hierarchy of Needs Theory and it’s Relation with SCRUM

    Maslow (1943) presented a need hierarchy which recognizes that different people are at different levels in their needs. Usually people start out looking for physiological needs and then progressively move up the needs hierarchy.   To be successful, a Scrum Team needs both core and non-core team members who have reached the esteem or self-actualization levels. The concept of self-organizing teams, ...

New blog articles detected

  • Conflict Management in SCRUM

    Organizations applying the Scrum framework encourage an open environment and dialogue among employees. Conflicts among Scrum Team members are generally resolved independently, with little or no involvement from management or others outside the Scrum Team. Conflict can be healthy when it promotes team discussions and encourages debates, as this usually results in benefits for the project and the re...

New blog articles detected

  • Determining Size of a Scrum Team

    It is important for the Scrum Team to possess all the essential skills required to carry out the work of the project. It is also necessary to have a high level of collaboration to maximize productivity, so that minimal coordination is required to get things done. The optimum size for a Scrum Team is six to ten members—large enough to ensure adequate skill sets, but small enough to collaborate easi...

New blog articles detected

  • All about Time-boxing in SCRUM

    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 a Scrum project. This ensures that Scrum Team members do not take up too much or too little work for a particular period of time and do not expend their ti...

New blog articles detected

  • How AGILE are you?

    To be agile means to be flexible. As simple as that may sound; the Agile framework is little more than an effective way to create business flexibility. Even though the basic Agile concepts are easily understood, one needs high levels of commitment, patience and openness to become a true champion of the Agile philosophy. Some people are inherently agile; they prefer people over technology, believe ...

New blog articles detected

  • What does “Quality” means in Scrum?

    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. There are numerous ways to define quality. 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 constantl...

New blog articles detected

  • Acceptance Criteria and the Prioritized Product Backlog

    The Prioritized Product Backlog is a single requirements document that defines the project scope by providing a prioritized list of features of the product or service to be delivered by the project. The required features are described in the form of User Stories. User Stories are specific requirements outlined by various stakeholders as they pertain to the proposed product or service. Each User St...

New blog articles detected

  • Quality Management in Scrum

    The customer is the most important stakeholder for any project. Therefore, it is important to understand the customer’s needs and requirements. The Voice of the Customer (VOC) can be referred to as the explicit and implicit requirements of the customer, which must be understood prior to the designing of a product or service. Generally, in a Scrum environment, the Product Owner’s focus is on busine...

New blog articles detected

  • Does Agile mean no planning and no documentation?

    It is widely known in the software development industry that Agile values “working software” over “extensive documentation.” This leads to the common misconception that Agile does not believe in documentation. It is true that documentation in Agile does not always mean typing code descriptions or lengthy time consuming information that may come in handy sometime in the future. However, Agile does ...

New blog articles detected

  • All About Cumulative Flow Diagram (CFD)

    A Cumulative Flow Diagram (CFD) is a useful tool for reporting and tracking project performance. It provides a simple, visual representation of project progress at a particular point in time. It is usually used to provide a higher level status of the overall project and not daily updates for individual Sprints. The figure above is an example of a CFD for a large project. It shows how many User Sto...

New blog articles detected

  • Benefits of Collaboration in SCRUM

    Collaboration in Scrum refers to the Scrum Core Team working together and interfacing with the stakeholders to create and validate the deliverables of the project to meet the goals outlined in the Project Vision. It is important to note the difference between cooperation and collaboration here. Cooperation occurs when the work product consists of the sum of the work efforts of various people on a ...

New blog articles detected

  • Role of SCRUM in striking balance between flexibility and stability?

    Today almost all industries and markets are exposed to constant changes. Changes come in the form of government policies, new tax rules, everyday advance in technology, consumer psyche, product or service demand, media influence, social media trend, buying motivation and many more. Whatever the reason, ‘Change’ has become an integral part of any business and Scrum helps organizations become more f...

New blog articles detected

  • The Pilot Team in SCRUM

    After a project makes it through feasibility analysis, you select the team that will deliver the project. Ideally, you want to begin with your feasibility team and expand that group as needed. Feasibility team members can share the information from their analysis with the additional team members; this will kick-start the project team.     Assignments are based on the current estimated size of the ...

New blog articles detected

  • Risk Management in SCRUM

    Risk Management consists of five steps: 1. Risk identification: Using various techniques to identify all potential risks 2. Risk assessment: Evaluating and estimating the identified risks 3. Risk prioritization – Prioritizing Risk to be included for specific action in the Prioritized Product Backlog 4. Risk mitigation: Developing an appropriate strategy to deal with the risk 5. Risk communication:...

New blog articles detected

  • Advantages of Scrum training or Scrum Certification

    Although there are many certifications such as ITIL, PRINCE2, which are implemented in organizations for achievement of goals through a project, Scrum training or Scrum certification can be described as one of the many courses where employees are groomed to become self-motivated and become keen to accept greater responsibility. There is a famous proverb, “If you are comfortable with yourself, you ...

  • How to Manage multiple teams in any Scrum Project

    A project is a collaborative enterprise to either create new products or services or to deliver results as defined in the Project Vision Statement. Projects are usually impacted by constraints of time, cost, scope, quality, people and organizational capabilities. The objective of the project team is to Create Deliverables as defined in Prioritized Product Backlog. The logical approach of the guide...

  • 7 C’s of Scrum

    Scrum is an iterative and incremental product development framework which ensures that the highest value is delivered to the consumer or the customer. 7 C’s of Scrum are the characteristics which ensure the highest value delivery through scrum framework. These C’s are discussed below: Consumer Centric: The focus of the Product Owner, Scrum Master and The Scrum Team is to understand the Consumer re...

New blog articles detected

  • Importance of Product Owner in Scrum?

    Responsibilities of a Product Owner include determining the project’s initial overall requirements and kicking off project activities; this may involve interaction with the Program Product Owner and the Portfolio Product Owner to ensure that the project aligns with direction provided by senior management. He represents user(s) of the product or service with a thorough understanding of the user com...

  • Role of Stakeholders in Scrum

    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 not always product owners but product owners are always stakeholders. P...

  • Essential Characteristics of the Scrum Team

    In a Scrum project, it is the Scrum Team members who are responsible for delivering the desired product or service and not the Scrum. Hence, we should be careful in forming the Scrum Teams. The Scrum Team is sometimes referred to as Development Team since they are responsible for developing the product, service or other results. It consists of a group of individuals who the user stories in the Spr...

New blog articles detected

  • Responsibilities of the Product Owner in Scrum Processes

    The Product Owner 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 Owner is responsible for ensuring that the Scrum Team delivers value. The Pr...

New blog articles detected

  • Various Conflict Management Techniques in SRUM Process

    Organizations applying the Scrum framework encourage an open environment and dialogue among employees. Conflicts among Scrum Team members are generally resolved independently, with little or no involvement from management or others outside the Scrum Team.   Conflict can be healthy when it promotes team discussions and encourages debates, as this usually results in benefits for the project and the ...

  • What is Dependency Determination?

    Once the Scrum Team has selected User Stories for a given Sprint, they should then consider any dependencies, including those related to the availability of people as well as any technical dependencies. Properly documenting dependencies helps the Scrum Teams determine the relative order in which Tasks should be executed to create the Sprint Deliverables. Dependencies also highlight the relationshi...

New blog articles detected

  • Scrum of Scrums Meeting

    A Scrum of Scrums Meeting is an important element when scaling Scrum to large projects. Typically, there is one representative in the meeting from each Scrum Team—usually the Scrum Master—but it is also common for other members of a Scrum Team to attend the meeting if required. This meeting is usually facilitated by the Chief Scrum Master and is intended to focus on areas of coordination and integ...

  • The basic principles of Scrum

    Scrum principles are the foundation on which the Scrum framework is based. The principles of Scrum can be applied to any type of project or organization, and they must be adhered to in order to ensure appropriate application of Scrum. The aspects and processes of Scrum can be modified to meet the requirements of the project, or the organization using it, but Scrum principles are non-negotiable and...

New blog articles detected

  • Inputs Required For Creating Large Project Components in SCRUM

    In the process of creating Large Project Components, we need to understand how the multiple Product Owners work together and how the multiple Scrum Teams work together. Also common components and common and specialized resources are to be identified. Following are the inputs required for creating large project components in Scrum.   Project Vision Statement A good project vision explains the busin...

  • Role of Chief Scrum Master in Large Projects

    Scaling Scrum for Large Projects is written from the perspective of a large project team that coordinates activities of multiple Scrum Teams in one big project to produce potentially shippable product increments/deliverables Large projects require multiple Scrum Teams to work in parallel. Information gathered from one team may need to be appropriately communicated to other teams—the Chief Scrum Ma...

  • Various Methods for User Story Prioritization

    At the program or portfolio level, there is normally a smaller number of requirements/user stories than at the project level. The percentage of user stories with a very tangible value/business need/user impact is normally much lower than on project level. That means that the selection of techniques that are useful at a program or portfolio level will be smaller. For example, Kano analysis has limi...

  • Large Project vs. Typical Scrum Project

    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 processes may be required to address the additional coordination an...

  • Importance of Prioritized Product Backlogs in a Scrum Project

    The Product Owner develops a Prioritized Product Backlog which contains a prioritized list of business and project requirements written in the form of Epic(s), which are high level User Stories. The Prioritized Product Backlog is based on three primary factors: value, risk or uncertainty, and dependencies. It is also referred to as the Risk Adjusted Product Backlog since it includes identified and...

  • How to Scale Scrum for the Enterprise

    Scaling Scrum for the Enterprise is usually applicable to the following: Portfolios, programs, and/or projects in any industry Products, services, or any other results to be delivered to stakeholders Projects of any size or complexity The term “product” may refer to a product, service, or other deliverable. Scrum can be applied effectively to any project in any industry—from small projects or team...

  • Roles and Responsibilities in Scrum

    Understanding defined roles and responsibilities in a Scrum project is very important for ensuring the successful implementation of Scrum. Scrum principles can be applied to any type of project in any organization and must be adhered to in order to ensure effective implementation of the Scrum framework. Organization in Scrum can be understood by defining the scrum roles. The scrum roles are basica...

  • What is SCRUM Quality?

    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 Prioritized Product Backlog upda...

  • Effective Backlog Grooming

    A typical Prioritized Product Backlog will contain all User Stories, their time estimates (including any revised estimates), and the status of higher priority requirements. Any new or revised User Stories resulting from changes to business requirements, customer requests, external market conditions, and/or lessons learned from previous Sprints are also incorporated. Product Backlog Review Meeting ...

  • The Lean Kanban Agile Methodology

    Kanban is a method for managing the process of software development with highest efficiency. The Lean concept optimizes an organization’s system to produce valuable results based on its resources, needs, and alternatives while reducing waste. Waste could be from building the wrong thing, failure to learn, or practices that impede the process. Because these factors are dynamic in nature, a lean org...

Out-Market Your Competitors?

Get complete competitive insights on over 2.2 million companies to drive your marketing strategy.

Create Free Account Log in

Out-Market Your Competitors

Get complete competitive insights on over 2.2 million companies to drive your marketing strategy.

Create Free Account

Already a user?  Log in