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

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