Project Setup & Scope Definition

Within the SAP Activate framework, what role do SAP Best Practices play, and where do they resurface in a Cloud ALM project?

Which guided configuration tool does SAP Activate use for S/4HANA Cloud Public Edition versus Private Edition, and what is their job?

How is the SAP Activate roadmap organized, and how do its tasks actually get executed during a project?

In SAP Activate terminology, how does a deliverable result differ from a working group (workstream)?

Where can you browse the implementation roadmaps, and how is that view laid out?

Name the six project phases of the SAP Activate methodology in order.

What is the goal of the discover phase, and what environment supports it?

The prepare phase is the first point where SAP Cloud ALM enters the picture — what happens to the project there?

What kind of work happens in the realize phase, and what quality bar must its output clear?

The run phase marks the end of the implementation project — so what is the ongoing job during run?

What is SAP Central Business Configuration, and which SAP solution does it currently configure?

How does SAP Central Business Configuration guide you through a configuration, and where do you begin defining what's in scope?

Why does process scoping in SAP Central Business Configuration feel familiar if you already know SAP Cloud ALM?

After defining scope in CBC, where do you build your organizational structure, and what happens when you later change it?

Once scope and organizational structure are set in CBC, how do you find the configuration work that applies to you?

When you work a CBC configuration activity, how do the actual settings get made and kept in sync?

Is SAP Central Business Configuration only used during the initial project, or does it stay relevant after go-live?

Is using SAP Central Business Configuration optional for an S/4HANA Cloud project?

What is the key advantage of CBC's tight link to the S/4HANA Cloud configuration activities?

Why would surfacing SAP Central Business Configuration activities inside SAP Cloud ALM be an advantage?

After you connect CBC to a Cloud ALM project, what changes in the task lists, and how do you tell CBC tasks apart?

Beyond just linking to CBC, what can you actually do on a roadmap task in SAP Cloud ALM?

What comes with the SAP Activate roadmap once assigned, and how are you expected to use the tasks?

How do SAP Cloud ALM's roadmap templates tailor a project to a specific SAP product?

What characterizes the cloud-centric scenario, and why does it tend to be agile?

Why is an ad hoc product update from the cloud supplier especially tricky during an ongoing cloud-centric project?

How does a single deployment strategy add new capability after the solution first goes live, and what runs alongside it on-premise?

Why would a company build one global solution and roll it out to its plants and countries instead of building each unit's system separately?

In a template approach, how are a single plant's own requirements handled, and what is the rule before changing the template itself?

Why is the template itself usually not run productively, and what risk appears when local adaptations flow back to it only late?

A defect appears at a plant running the template. What must you determine first, and where does the correction belong?

SAP Cloud ALM lets you set up projects very flexibly. Why is that freedom also a trap, and what should you settle first?

Which app do you use to configure project naming, timeboxing structure, and team setup in SAP Cloud ALM?

Why does the initial template release follow SAP Activate phases while the later minor releases do not?

When a completed template is handed to a plant for rollout, how do the SAP Activate phases differ between the template's view and the plant's view?

Once a localized release is running productively at a plant, which SAP Activate phase does that represent from the template and rollout perspective?

While a plant rollout is still in full swing, why is minor release R2.1 not imported on its own, and when does the template's run phase end?

What naming scheme is recommended for an initial template development project, and what does the resulting name look like?

How is a project scope named so it can be recognized and filtered easily across Cloud ALM's functional areas?

For an initial release, why create your own realize phase in the timebox settings instead of just using the predefined SAP Activate realize phase?

You added an SAP Activate roadmap template to a project but a phase's tasks are missing, and you want to rename a phase. What is going on?

When several projects run at the same time, why include the release number in the sprint name, and what does the full sprint naming look like?

In the example, a one-year solution uses four-week sprints. How many sprints result, and what can you do with them ahead of time?

What is further template development, and how is new capability delivered to the units consuming the template?

Why manage each subsequent template release in a new Cloud ALM project, and what is the catch with standard tools?

In the example, minor releases are delivered every four months. How many minor releases per year is that, and what happens to sprint length?

Why does the maintenance phase generally not use sprints, and when would maintenance sprints actually make sense?

A template error surfaces during a plant's productive operation and consumers need the fix fast. Is the only path to fix it centrally in the template first?

Subsequent template releases drop the SAP Activate phases, but when should you reconsider using them again?

After a template is completed, what happens next, and why do local requirements matter at this stage?

What are the three options for managing a rollout in SAP Cloud ALM, and which does the example scenario use?

How are rollout projects and their scopes named, building on the template naming convention?

In the AriHana rollout example, why give each business unit (e.g. Dresden vs Madrid) its own scope inside one joint project instead of sharing a single scope?

How are the phases of a rollout project structured when several rollouts run one after another?

During ongoing productive operation of the rollouts, what phase runs alongside the run phase and what is it for?

When one project covers several rollouts and you activate SAP Activate roadmap tasks, what's the catch, and how do you assign those tasks to rollout-specific phases?

Rollout projects can be run in parallel, time-delayed, or sequentially — what's the advantage of running them sequentially?

What two options exist for rolling further template deployments (release 2) into the rollouts, and how do they differ in effort?

At a high level, what does creating a project in SAP Cloud ALM give you as a starting point?

Where do you go in SAP Cloud ALM to start creating an implementation project?

What five pieces of information does SAP Cloud ALM require in the first step of creating a project?

In the Projects and Setup app, where do existing projects live and how do you create a new one if the Create button isn't showing?

You need to audit exactly who changed what in a project and when — which control gives you that?

What does the SAP Activate Roadmap selection list do when you set up a project?

What happens to your available tasks if you skip selecting an SAP Activate template, and why does that matter?

What's the difference between Single Roadmaps and Combinable Roadmaps in SAP Activate?

When a project involves several SAP products, which SAP Activate template should the project manager pick, and does the catalog stay static?

What does the Integration Scenario section of project setup let you activate?

What are the three possible statuses of an SAP Cloud ALM project, and what practical purpose do they serve?

How can a single rollout project hold more than one scope, and how do you get to where scopes are edited?

SAP Cloud ALM offers predelivered tags that came from your SAP Activate roadmap — can you rename or delete them, and what are tags mainly good for?

Which entity types can currently carry custom tags in SAP Cloud ALM?

When should you plan your tagging scheme, and how do you actually create a new tag such as risk_high?

Where do you get a central overview of every tag, including who created each one?

When would you use a tag group, and what limitation applies to merging tags?

In SAP Cloud ALM, what is the act of defining a project's scope called?

Conceptually, what is a scope in SAP Cloud ALM?

What makes it sensible to put several processes into the same scope?

Which tabs does each project display in the Projects and Setup app?

At what point in project setup do you define scopes, where do you do it, and how can the work be documented?

A colleague opens a brand-new SAP Cloud ALM project and asks where the existing scopes are. What do you tell them, and how do they add one?

In SAP Cloud ALM scoping, why does choosing a solution scenario decide which processes you can put in a project?

Why should you think twice before selecting and saving a solution scenario for a scope?

You activated a scenario but several of its processes do not apply to your project. Since you cannot deselect the scenario, what is the intended way to exclude them?

Before your team can start working on processes in SAP Cloud ALM, which two prerequisites must already be in place?

Name the two ways to reach the process editing area in SAP Cloud ALM, and which overview tiles jump you straight into the process scope.

Within a solution process's detailed structure, how does a Project Task differ from a Note?

In the Tasks app, why can you delete a user story you created but not a task that came from the SAP Activate template?

After you finish selecting solution processes for a scope, which button locks in the scoping, and how do you make changes afterward?

A consultant tries to open the SAP Readiness Check app in a fresh SAP Cloud ALM tenant and it will not run. What prerequisite is likely missing?

How does SAP Readiness Check support a move from SAP Solution Manager to SAP Cloud ALM, and does the whole thing have to move at once?

The SAP Readiness Check for SAP Cloud ALM result is split into three groupings. What does each one tell you?

Walk through the steps to run SAP Readiness Check and get the data into SAP Cloud ALM.

What is SAP Business Transformation Center, and how is it delivered and licensed relative to SAP Cloud ALM?

Which SAP Business Transformation Center capability ships first with SAP Cloud ALM, and what phase of a transformation is it built to help with?

Beyond producing a blueprint, what does SAP Business Transformation Center aim to be as a platform?

What must a customer already have in place before they can use SAP Business Transformation Center digital blueprints?

What are the two main functional blocks covered by SAP Business Transformation Center?

After uploading a source file to SAP Business Transformation Center, how do you create your first digital blueprint, and can several blueprints share one file?

In a SAP Business Transformation Center digital blueprint, what is the Hint column telling you?

Why do SAP Readiness Check and SAP Business Transformation Center barely matter in a pure greenfield move to SAP S/4HANA?

In SAP Activate, what are accelerators and why do they matter?

How does the explore phase decide what will actually be built, and where do the findings go?

What does the deploy phase set up, and how is the finished solution handed off?

When picking a project approach for an SAP implementation, what are the central deciding factors?

What defines the on-premise scenario, and what turns it into a hybrid scenario?

In an on-premise scenario, how are developments delivered, and how can Cloud ALM project phases mirror that?

What does template protection mean in a template rollout landscape?

When deciding whether two SAP products belong in the same Cloud ALM project, what should drive the decision?

In the example landscape, why is a new Cloud ALM project created for each major template release rather than one project for everything?

Standard tools can't carry Release 1's scope and processes into a new project. What third-party add-on fills that gap, and what can it do?

What triggers the template to go into maintenance, and why create a dedicated maintenance phase for it?

Once a rollout is completed and productive operation begins, does the project end?

After the first template release ships, how does the template evolve, and when should those changes reach a business unit?

What can a Tag administrator do that a Tag viewer cannot?

Which three apps are the essential starting points for creating scopes and authoring processes, and how do you reach them?

Where does the content you select for scopes and processes actually come from?

Why would you select SAP Application Component in the Select Transformation Objects area of a digital blueprint?

In the final step of building a digital blueprint, what two kinds of things do you select and delimit before the summary is shown?

If you hit a problem while working in SAP Business Transformation Center, how do you raise it with SAP, and what self-help is built in?

Because SAP Business Transformation Center follows a cloud release model, how fast does its scope change, and how are you meant to stay current before a project?

Where in SAP Cloud ALM do you attach the SAP Activate roadmap to your project?

When you are migrating an existing SAP solution, which two SAP Cloud ALM tools help you fix the right project scope, and what do they analyze?

What is SAP Readiness Check, and how does it help you plan a digital transformation?

SAP Readiness Check supports several transition scenarios. Which source-system journeys does it cover?

Where do the analysis results actually come from when you start a new SAP Readiness Check analysis, and which system does SAP recommend running against?

What exactly does the SAP Activate methodology describe, and what is it built on?