Inputs Required For Creating Large Project Components in SCRUM

January 31, 2017
By
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…

Read more »

Role of Chief Scrum Master in Large Projects

January 23, 2017
By
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…

Read more »

Various Methods for User Story Prioritization

January 23, 2017
By
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…

Read more »

Large Project vs. Typical Scrum Project

January 18, 2017
By
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…

Read more »

Importance of Prioritized Product Backlogs in a Scrum Project

January 16, 2017
By
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…

Read more »

Subscribe

Follow Us On

Post-Plugin Library missing