The reason why to not modify Scrum

Reading Time: 4 minutes

Remember that Scrum is a frame, not a set of work instructions. The Scrum frame is veritably feather-light, but what it includes is essential. Every piece of the frame is there for a reason. Making the following variations can come with negative consequences.

1)  Not having a Product Owner

There are three accountabilities in Scrum:

  • The Scrum Master is primarily responsible for perfecting the stepping down of Scrum within the association.
  • The Developers do the work of the Scrum Team.
  • The Product holder is responsible for maximizing the value of the Product through the content and ordering of the Product Backlog, which is the squad’s to-do list.

Each of these arrears is critical to the success of the Scrum Team. barring any of these arrears negatively impacts its capability to deliver value to the association.
And yet numerous Scrum teams don’t have anyone fulfilling the Product proprietor responsibility.

The result of not having a Product Owner

The Product Owner ensures that the Scrum Team works on the right effects. Without a Product Owner, the Scrum Team is like a boat without a rudder. They might go nearby. They might do work. But is it the right word, and is it taking the product in the right direction? Scrum brigades without a Product owner warrant a strategic approach and drift from precedence to precedence without anyone charting a course for the product’s overall direction.

2)  Skipping the Daily Scrum

The Daily Scrum is a 15- minute day-to-day event for Developers. Its purpose is to increase the liability of delivering a Done addition that meets the Sprint thing. numerous teams skip the Daily Scrum to save time, increase edge, or reduce interruptions.

The result of skipping the Daily Scrum

Excepting the Daily Scrum significantly reduces the chance of delivering a Done increment that meets the Sprint thing. Without it, the squad identifies impediments more slowly, Developers suffer in silence longer, the Sprint Backlog is less transparent, and Developers don’t unite with the rest of their squad as constantly.

The Daily Scrum frequently eliminates the need for other meetings. Without the Daily Scrum, teams often need further MEETINGS to resolve the issues allowed to break down because they weren’t uniting daily to resolve them rapidly.

3) Skipping the Sprint Review

The Sprint Review is the alternative to the last event within the Sprint. It’s an occasion for the Scrum Team and its stakeholders to talk over the work completed during the Sprint and unite on what to do next. It’s the Scrum Team’s occasion to showcase their work and engage in discussion with their stakeholders. teams might be tempted to skip the Sprint Review for many reasons. Maybe it’s been a lousy Sprint, the squad’s morale is low, or there are pressing deadlines.

The result of skipping the Sprint Review

Short feedback rounds are priceless to the Scrum Team because it allows them to change direction rapidly to concentrate on the most precious deliverables. However, they miss an occasion to get stakeholder feedback on what they delivered during the prior Sprint, and the most precious thing to do next, If a squad skips the Sprint Review.

4)  Blowing the time boxes

Each of the five events in Scrum has a time box. The Sprint is time-boxed to one month or lower, the Sprint Planning event is time-boxed to 8 hours or lower, the Daily Scrum is time-boxed to 15 minutes or lower, etc.

Time-boxing each of the events has numerous benefits. For example, by time boxing the Sprint to one month or lower, learning cycles are more frequent, and the threat is limited to the cost and trouble associated with the shorter time frame. Other benefits of time boxing include reducing waste. For illustration, by limiting the Sprint Planning event to 8 hours, the Scrum frame reduces the waste that might be created by overmuch time spent constructing the Sprint Backlog.

The Daily Scrum has a 15- minute time-box, making it the shortest event. The 15-minute time box for the Daily Scrum is important in order to exclude waste. Still, the Daily Scrum requires focus to stay within the time frame, and it’s easy for this event to run long. For this reason, the Daily Scrum is the one event where it’s most likely for the squad to blow the time box.

The result of blowing time boxes

I formerly had a squad whose Daily Scrum constantly exceeded one hour. After the first time, Developers gave it an alternate chance and still came to the next one. But when we continued to blow the time-box over many days, no one attended the Daily Scrum. It became a drain on everyone’s time, energy, and instigation.

Extending the discussion problem solve an issue rather than simply focusing on identifying the issue as well as those who should later get together to solve it caused a lot of wasted time for the team. Scrum is founded upon empiricism and lean thinking. By blowing the time box of the Daily Scrum, the team was introducing waste – and frustration – which is not in alignment with lean principles.

5) Team size too large

The Scrum Guide doesn’t set a maximum squad size but does say that Scrum teams are normally ten or smaller. The companion countries, “ The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint. ”

Occasionally teams newer to Scrum suppose it’s harder to deal with having multiple, lower teams than one large squad, so they ignore the direction to keep squad members low.

The result of a large Scrum Team

I’ve heard of Scrum teams with 20( or further) squad members, and the result is they struggle with conducting any of the events within the timebox. They engage in minimum collaboration, and the relations they do have are thriftless because collaboration conditioning is unsolvable with too numerous people.

More mature Scrum interpreters have lower Scrum teams supporting a single product. These teams handle their collaboration conditioning by participating in the refinement process or using the Nexus frame to measure.


It can be tempting for those newer to Scrum to suppose that conforming to the frame will make it easier to take up. still, when teams modify Scrum, they don’t witness its full benefits, performing in lower-performing teams and slower value delivery to the association.

If you want to know How to fail as an Agile coach you can refer to this blog.

If you want to learn more about product owners and product managers please refer to this blog.

Written by 

Prince Agrahai is a Scrum Master at Knoldus. He has good skills in Agile Methodology and Scrum Framework. He is also a good team player and likes to achieve milestones together. Also, getting up early motivates him for his work. On the personal front, he loves to travel, play cricket and watch movies.