Modifying Scrum – is it allowed?

Modifying Scrum is not allowed due to its well-defined nature and potential for a Scrum-isch scenario. However, every team has unique needs and should start by integrating the process as clean as possible and observing feedback. Be selective about modifications and consider the underlying causes of the issues. Scrum is perfect for people who have been using it for a long time, but it may not work for everyone.

Modifications to meeting days, times, and length for sprint kick-offs should be an option for the team to decide on. Initially, 4 hours of meeting time is recommended, but as efficiency increases, it may be possible to reduce it. The message should be that the time invested in Scrum meetings is well spent.

For retrospectives, the team should decide on a format, whether to use a spreadsheet or talk free form. Stand-ups can be a compromise, but it is not always the majority's preference. Tracking velocity may not be an easily desired change, but it is important to consider the team's needs and preferences.

Why do we use a modified Scrum Model?

It's unrealistic to assume that every project will succeed using the same approach because every customer and project is unique.

Study and analyze the circumstances of every client

In order to determine the most effective project management strategy, we evaluate the client's characteristics, including their level of involvement and availability, as well as their expertise and expectations regarding the delivery process. Once we have a better idea about these client and project realities, we then build the process around these realities.

How do roles get assigned?

When taking into account the issue of competence, for instance, a client that has experience with Scrum may be able to use internal product owners and scrum masters. Product owners are occasionally clients, while scrum masters work for TIGOSOFT. In other cases, clients have never used Scrum before, and in these cases, the project manager must take on a hybrid role, contributing to both product ownership and assisting the development team in putting in place a structure like to Scrum.

How do we work around client involvement and availability?

Not every client or member of their team has the time to attend daily standups, review meetings, planning meetings, and retrospectives due to scheduling conflicts. It would be fantastic if the client or other team members who work in the same location as the customer could attend every one of these events. If they are unable to, we will nevertheless find a way to work around these limitations by ensuring that they are involved as much as possible in these Scrum events, which at the very least occur amongst team members at TIGOSOFT to guarantee that work progress is checked on a daily basis, that working software is reviewed following each Scrum cycle, and that efficient planning is being done for the following cycle.

Best practices for developing a Modified Scrum Project

1. Requirement Breakdown and Multi-Role Collaboration

A A A A

[{"displaySettingInfo":"[{\"isFullLayout\":false,\"layoutWidthRatio\":\"\",\"showBlogMetadata\":true,\"showAds\":true,\"showQuickNoticeBar\":true,\"includeSuggestedAndRelatedBlogs\":true,\"enableLazyLoad\":true,\"quoteStyle\":\"1\",\"bigHeadingFontStyle\":\"1\",\"postPictureFrameStyle\":\"1\",\"isFaqLayout\":false,\"isIncludedCaption\":false,\"faqLayoutTheme\":\"1\",\"isSliderLayout\":false}]"},{"articleSourceInfo":"[{\"sourceName\":\"\",\"sourceValue\":\"\"}]"},{"privacyInfo":"[{\"isOutsideVietnam\":false}]"},{"tocInfo":"[{\"isEnabledTOC\":true,\"isAutoNumbering\":false,\"isShowKeyHeadingWithIcon\":false}]"},{"termSettingInfo":"[{\"showTermsOnPage\":true,\"displaySequentialTermNumber\":true}]"}]

Explore more on these topics