Steering an SAP AI Project: Charter, Budget, Roles, Go/No-Go and Value

What you will learn

• Write the nine-line project charter, including a baseline, a pass rule and a kill condition signed by the sponsor
• Forecast run cost in AI Units as tasks per month × actions per task × rate, split by Standard (0.02) and Advanced (0.05) actions, and set the alerts that make the forecast a budget
• Assign the eight roles and the Go/No-Go decision rights with a RACI the committee can sign
• Run five gates with four possible outcomes, each with the evidence it requires and a written No-Go trigger
• Keep a dated status ledger and a steering-level risk table, and report value against a baseline in three readings

Module overview

Who this is for. You have built the business case (M378) and know the delivery lifecycle (M379); now you are the person the sponsor holds responsible for the project. This module is about steering: the charter, the budget, who decides, when to stop and how to show the value. It does not repeat the lifecycle, the AI centre of excellence (M376) or the adoption work (M381); it tells you what the steering committee must decide at each point and what evidence it needs.

Prerequisites

• M378 (Building the SAP AI Business Case) and M379 (the SAP AI delivery lifecycle)
• Experience of running or sponsoring an SAP project with a steering committee

Outcomes

• Produce a charter that a sponsor can sign and later use to stop the project.
• Build a consumption forecast whose drivers and unknowns are labelled, with two alerts and their owners.
• Name the owner of each role and of the Go/No-Go call.
• Decide at a gate from evidence, using Go, Go with conditions, No-Go or Stop.
• Report value against a measured baseline without hardening a range into a point.