The fundamental Scrum processes defined in the 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…
After justifying and confirming the value of a project, the Product Owner should consider the organizational policies, procedures, templates, and general standards dictated by the Scrum Guidance Body (or similar organizational project board or office) when planning a project; at the same time maximizing Value-driven Delivery. The onus for determining how the value is created…
If an entire project or portions of it are being completed under a contract, the contract defines the scope of work and the specific terms of the contract. The type of contract used influences project risk. Some of the most common types of contracts used in Scrum projects are as follows: Incremental Delivery Contract—This contract…
There are three roles in scrum: Product Owner, Team, and Scrum Master. Together they are called The Scrum Team. The Product Owner is accountable for optimizing return on investment (ROI) by analysing product aspects, converting these into a priority-wise list so as to decide those things which should be at the top of the list for the…
For many of the Scrum practices, high-bandwidth communication is required. To enable this, it is preferred that team members are colocated. Colocation allows both formal and informal interaction between team members. This provides the advantage of having team members always at hand for coordination, problem-solving, and learning. Some of the benefits of colocation are the following:…
As more and more companies are adopting Scrum as preferred project management method over traditional waterfall method, the subject of mapping of the roles is becoming more critical. Probably one of the biggest challenges organizations face when they move to Scrum is where does a Project Manager fit in Scrum? We are so used to…
Because changes are not allowed during a Sprint, the impact and frequency of expected changes may have an impact on the decision related to the length of the Sprint when it is determined. If project requirements are generally stable and major changes are not expected in the near future, the Length of a Sprint may…
What is a Scrum of Scrums and how does it work in the product development process? The first thing to know about the Scrum of Scrums is that it acquires relevance only for large projects where multiple Scrum Teams are involved. In this process Scrum Team representatives convene for Scrum of Scrums Meetings at predetermined…
We normally do not associate companies in the private sector with bureaucracy and reserve that criticism mostly for governments and public sector organizations. But how many times have we waited for a response from a department which never came? How many times have we felt things have taken twice as long as they should have?…
Request for changes are usually submitted as Change Requests. Change Requests remain unapproved until they get formally approved. The Scrum Guidance Body usually defines a process for approving and managing changes throughout the organization. In the absence of a formal process, it is recommended that small changes that do not have a significant impact on…
