Focused Build - Requirements are more than user stories

This article explains the role of Requirements as backlog and in connecting business and IT.

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.

  1. Requirement captures Priority and Value of a user story. Priority and value can rank a requirement uniquely but importantly they can convey what is important / valuable for the business. Business should be engaged to prioritize requirements. Value points indicate the value of the requirements from the business perspective. 
  2. Architect analyzes the dependencies and provides an effort estimate which has to be captured in the requirement. Since requirements are usually captured during the Prepare phase clear effort information may not be available, an estimate should be used instead.
  3. Approval is needed for a requirement, usually the business provides the approval. Approved requirements can be connected to Work packages and Work item.
  4. Requirement connects the requirement to deploy cycle and provides traceability back and forth. Requirements connect the business and IT, it is important for IT and business to collaborate to capture requirements effectively.