Agile Implementation of User Stories

What is the Daily Scrum in Cloud ALM's agile flow, and which artifact helps the Scrum master run it?

Chapter 13 opens the realize phase of SAP Activate. What does the requirements-to-deploy approach expect requirements to represent by this point?

Once the explore phase wraps up, what three things together form the baseline of the solution to be implemented?

Who turns confirmed requirements into user stories to build the product backlog, and when does this begin?

In SAP Cloud ALM's agile flow, where do user stories come from and how can they be broken down or linked?

Why would you save a search in SAP Cloud ALM, and does every app support it?

Steps to save a filtered search under your own name in SAP Cloud ALM

After you create user stories from a confirmed requirement, what should you do with the requirement itself and why?

Why is the user story called the central element of agile product development in SAP Cloud ALM?

Beyond a title and description, what kinds of information does a SAP Cloud ALM user story hold?

In the common user story workflow, what do the Open, In Progress, and Finished statuses each signify?

A user story is blocked by an external dependency, and another is no longer needed. Which two statuses apply, and how do they differ?

What are the two ways to create a user story in SAP Cloud ALM, and when does the standalone route make sense?

Steps to create a user story directly from a confirmed requirement

Which user story field is mandatory, and why prefix its title with codes like URS or INC?

When writing a user story strictly by Scrum, what sentence format is used and what question does it answer?

In practice, teams rarely keep user stories in strict As-a/I-want/so-that format. What problem does this cause and how do you contain it?

What three-part structure is recommended for a SAP Cloud ALM user story description?

SAP Cloud ALM has no built-in field for Definition-of-Done criteria. What are DoD criteria for, and what workaround is recommended?

What kinds of checks typically appear in a user story's Definition-of-Done table?

Steps to create a standalone user story that has no link to any requirement or process

What does a user story template carry over, and how do you turn an existing story into one?

You created several user stories from one requirement, plus a manual one you want linked. Where do they show up and how do you attach the extra story?

When you start specifying a user story created from a requirement, which fields are already filled in for you?

What does the Priority field on a user story control, and what values can it take?

Story points and effort both estimate a user story, but they measure different things. How?

In the product backlog, how would you group several user stories that all belong to one broad topic such as an epic?

What does it mean when a user story already carries a value in its Timebox field, and who put it there?

Besides its main fields, what other objects can you cross-reference from the tabs of a user story?

SAP Cloud ALM won't let you link one user story directly to another to show a dependency. So how do you track interdependent stories?

A teammate wants to attach a spec document directly to a user story in SAP Cloud ALM. Why can't they, and what's the alternative?

What must be true before you can run the sprint planning meeting?

How do you assemble a product backlog for sprint planning, and what does a filled Timebox column tell you about a listed story?

After discussing high-priority stories with the team, what's the fastest way to move a whole selection into the next sprint?

Once stories are assigned to a sprint, why create a sprint backlog in addition to the product backlog, and how does it differ?

When the product owner and development team review the preselected user stories to define the sprint goal, which aspects do they weigh?

At what point is a sprint planning meeting considered finished, and what does that produce?

A requirement's meaning is unclear during sprint planning. Why is that the wrong place to sort it out, and where should it have happened?

During sprint planning, what are the two places you can assign the responsible team and developers to a user story?

Once user stories exist for a requirement, what status does the product owner give the requirement, and what does that signal?

In an agile context, what is a feature in SAP Cloud ALM and what role does it play?

Who should create features and when, so developers aren't burdened with it mid-sprint?

As sprint execution starts, what steps does a developer take to begin working a user story?

At the sprint review, how do the Open, In Progress, Blocked, and Not Relevant statuses each dictate what happens to an unfinished user story?

In the sprint review, what must the product owner verify before a user story is finalized?

When test cases are part of a user story in Cloud ALM, what status should they carry at the sprint review and why?

What conditions must be met before a requirement can be handed over to test in Cloud ALM?

In Cloud ALM, what two entities carry developed functions out to the test and production systems?

How does a requirement get from the explore phase to confirmed-complete implementation in Cloud ALM's agile method?

How do features and user stories relate to requirements in Cloud ALM, and how do a feature and a user story differ?

What are the trade-offs of a 1:1 (one feature per requirement) ratio when planning sprints in Cloud ALM?

What do you gain and lose with a 1:n (one large feature covering many requirements) ratio in Cloud ALM?

A user story has several subtasks. Over what span is the parent story counted as In Progress?

How can a developer narrow the sprint backlog to show only their own worklist?

Before a developer can record changes for a user story in Cloud ALM, why must transports on the development system exist first?

Starting from a user story in Cloud ALM, what is the sequence of navigation to create a transport for it?

After transports are created from a feature in Cloud ALM, what status confirms success and what action should follow on the feature?

Why should developers link their user stories to the feature via the Assign button, and when does this matter most?

During a Daily Scrum, how can you surface a user story's subtask completion rate in Cloud ALM?

How does Cloud ALM provide a Scrum board, and which items can you drag across its columns?

What event closes out sprint execution in Cloud ALM's agile flow, and what happens there?

Why break a large user story into subtasks, and what are the two ways to create one?

What naming trick lets user stories appear neatly bundled with their subtasks in the sprint backlog?

What is the sprint retrospective for, and how does Cloud ALM help follow up on it?

How should your testing cadence drive the choice between one feature per requirement and one large feature in Cloud ALM?

What is a sprint in Cloud ALM, and how are sprints set up and staffed?

During sprint execution in Cloud ALM, how do developers record progress and who can see it?

Beyond raw status updates, what does Cloud ALM offer to visualize and manage sprint progress?

How does SAP Cloud ALM realize a product increment down to the transport layer?