Requirements Management

Within an SAP Cloud ALM implementation project, what does requirements management let a team do with business needs?

On a solution process's Create dropdown, how does a Requirement differ from a User Story?

What does requirements management in SAP Cloud ALM produce, and how does a requirement get reused later in testing?

Trace a requirement's journey across the SAP Activate phases in Cloud ALM, from where it enters to how it gets built.

In Cloud ALM terms, what actually qualifies as a requirement?

When are requirements typically gathered in an implementation, and what kinds of needs can they represent?

What are the three phases of the requirements workflow in SAP Cloud ALM?

What does a requirement's status express in Cloud ALM, and how many status values exist?

A requirement sits at In Realization versus In Testing versus Confirmed - what does each status actually mean?

A colleague assumes requirement statuses must advance in a fixed order - what's the catch?

Why does a requirement carry a separate Approval attribute in addition to its status?

What general functions can you invoke directly on a requirement in Cloud ALM?

How do the Copy, Comment, and History functions each help you manage a requirement?

What happens to a requirement when you Set it to Inactive, and can you undo that?

Both Inactive and Obsolete take a requirement out of play - what can you no longer do once it's Obsolete?

What must be true before Cloud ALM will let you delete a requirement, and is deletion reversible?

A requirement's Approval attribute is set to Approved - why can't it be deleted anymore?

What are the four technical ways to get a requirement into SAP Cloud ALM?

Where should you create a requirement so it is captured well, and why avoid the solution activity level?

When would you create a standalone requirement instead of one tied to a solution process, and which is preferred?

On which structural elements can a requirement be created directly within a solution process?

Walk through the steps to create a requirement from within a solution process in Cloud ALM.

SAP recommends a naming convention for requirement titles - what is it and why bother?

What state does a new requirement start in when it surfaces during a fit-to-standard workshop?

How do you create a standalone requirement that isn't tied to any process?

You captured a requirement as standalone, but later realize it belongs to a specific solution process. Are you stuck recreating it?

Why is the requirements backlog in Cloud ALM not the same thing as the Scrum product backlog?

How does SAP suggest mapping a requirement's four priority values so teams choose consistently?

There are no dedicated fields for a requirement's description, comments, and estimated effort. Where do you put that information?

When estimating requirement effort, what does choosing Fibonacci numbers buy you that T-shirt sizes do not?

Beyond the free-text description, which three attributes does SAP recommend filling in on a requirement's Additional Information tab?

How do the Assigned Role and Responsible fields on a requirement relate to each other?

How does a product owner build a reusable confirmed requirements backlog to convert into user stories?

Where is a requirement's approval status set, and what does SAP recommend for consistent quality?

If a requirement needs no approval, what are your options, and what happens when you set it to Ready for Approval?

An approver thinks a requirement is not ready but wants to allow a later resubmission. Why should they avoid clicking Rejected?

Once a requirement is formulated (and approved if needed), which follow-up elements can carry it into implementation, and how do you create them?

Why does a requirement, rather than an individual user story, act as the collection point for test cases?

Besides typing one in by hand, what other sources can a requirement in SAP Cloud ALM originate from?

What does the Workstream attribute represent, and where do its values come from?

Why might the Scope, Timebox, Start date, and Planned Completion date already be populated on a new requirement?

You want to attach a link to a company SharePoint page from a requirement. How do you add it?

Before your team starts tagging requirements, what should you settle first and why?

When is a requirement actually ready to hand over to implementation, and does the final review change its status?

How does the product owner use a requirement's priority when preparing it for handover, and what else should be filled in?

What are the two ways to plan the next steps after a requirement, and when does the leaner one break down?

Why is it advisable to let the product owner create user stories rather than spawning them directly from the requirement?

During implementation, how can a requirement or user story be extended to carry the actual configuration work?

After go-live during the deploy phase, what must you do with requirements and which status marks a fulfilled one?