in Agile by

The Product Owner of the team turns stakeholder’s requirement documents into tickets and asks to estimate them. Are you fine with that process?

1 Answer

0 votes
As a Scrum Master, I will not accept this process as it is its sugar coating Waterfall in the name of Agile. Just converting the requirements into tickets will not suffice for the entry criteria of the user stories. The requirements should be finely broken down into finer pieces so that it can be consumed in sprint time. The conversion of stakeholder requirement into tickets should also follow the best practices in the industry like INVEST, 3Cs, etc. to help teams gain confidence into what is to be built.The focus should always be on delivering value to the customers, which requires keeping a health prioritized backlog. The organization adopting Agile use tools like Rally, Version 1, etc. to manage the product backlog and sprint backlog. Hence the requirements should be entered in the tools for the teams to pick.

Moreover, the scrum team should be involved early in the product discovery process so that all the parties involved have a shared understanding of what is to be built. This also helps in curating the requirements which are feasible and have pre-identified risks and challenges. Finally, the Scrum Master should help the teams to be agile and not just allow anti-patterns to grow.