Scrum is a framework that gives freedom of execution: it is easy to use and contributes not only to the development of the company but also to the customer as well as to the Scrum team. Being able to present the product to the customer at an earlier stage (before it is completed) helps the customer to realize if changes are needed. The sooner these changes are detected, the less will be the potential costs.
Scrum allows the product to be refined and modified during development itself without delaying its completion. Another important thing to note is that Scrum needs to be implemented as a whole to work well as a framework for other techniques and methodologies. While only some parts of Scrum may be implemented, the result will not be like a fully operational Scrum framework. That is, if we want our company to thrive by implementing Scrum, we must use it wisely and as directed.
How Scrum will this improve our business?
Scrum prioritizes providing additional business value to the customer. Scrum is more flexible in gathering requirements and allows the development phase to start earlier. It is very important that all requirements are well defined, but not all requirements are necessarily defined at the beginning of the project. If there are client changes, they can be introduced in the next iteration. The priority of changes can be changed and further development of features with the highest business value for the client at each iteration can continue. This will not only improve the customer relationship but also allow the development of a logically finished and desired product.
Do I have to expect any unexpected problems or costs with Scrum?
There is always a risk of unexpected problems, but Scrum allows them to be “captured” and removed at an earlier stage of product development. As already mentioned, if changes to the movement are needed, they can be applied without affecting the overall rhythm of product development.
If all roles and expectations are properly represented in the Scrum team, it is up to them to organize and work effectively to eliminate any difficulties and problems.
Why is there no project manager in his team and when is he expected to be appointed?
Scrum does not assume the presence of a Project Manager role, although there may be a team leader. This brings the team together and each member can develop professionally in areas where he/she is not an expert. In addition, the efficiency and effectiveness of the Scrum team are optimized. There are other roles that are more important in this case than Product Manager:
- Product Owner: who has a product vision, knowledge of all requirements and their business value to the product.
The team is ideally sized between 3 and 9 members and has a mission to build the product. It is a multifunctional and self-organizing team with all the skills and knowledge needed to develop a product. Each member must adapt to the needs of the team at all times. - Scrum Master: With excellent knowledge of Scrum, its purpose is to assist and support the team and Product Owner in the implementation of Scrum. This includes answering all sorts of questions and doubts about using Scrum and isolating the team from other external issues. He is not a leader, but a mentor. He wants you to meet in person later today, both alone and to answer these questions clearly and in detail.
Scrum and project management discussions are welcome in our Reddit space: https://www.reddit.com/r/ProjectManagementPost/