For each Scrum project, we conduct a business workshop with the client. Together, we set the framework for the project, including the key functionalities of the application or website.
However, it often happens that ideas don't correspond to reality. The original assumptions may not be 100% accurate because market trends may have changed since they were established.
Sometimes you have to see a feature to realize that it doesn't make sense. And vice versa, sometimes you need to recognize that a feature is missing to find out it's necessary.
Scrum consists of a weekly product demo where the project team shows the current version of the product to the client. Together, we think about what is needed, what is redundant, and what is worth improving.
Thanks to this, the client can influence the course of work on an ongoing basis. We avoid a situation where we code something only because we planned it three months ago. Thanks to Scrum, we code only what the client and his clients really need.
An example from a project:
A client from the food industry hired us to recreate old versions of existing websites and build custom cms. After business workshops, we agreed to create all pages from scratch, using content from previous versions.
Thanks to weekly meetings, we learned that some of the old pages contained useless information and outdated sections that we shouldn't include in our scope of work. As a result, we saved time for both the client and ourselves and could think of something new that will be useful for the users.
