In focused build Requirement is backlog, requirement can be used to capture user story, feature, simplification item or even a defect. Requirement can also capture Fit & GAP in SAP best practices.
Requirement to deploy process in focused build starts with requirement gathering and it is a critical activity in SAP implementation.
Requirements in focused build are more than a typical user story in Agile they play a bigger role in focused build. Requirement is the beginning of requirement to deploy process and the relationships with WP/WI makes the process traceable providing high visibility in realization and deployment activities.
Requirement indicates the end user value, effort required and dependencies associated with the backlog.
Requirements are processed as team effort, business and IT work as one team to capture requirements.
It is possible for both IT and business to capture requirements. For example architect can capture requirements during a workshop or process discussions with the business.
Business can use “Analyst” role in focused build delivered roles to create requirement directly in focused build.
It is important to enable business along with IT so that business can create requirements.
Remember, clear and unambiguous requirements are key to the success of an SAP implementation.