Week 1: Project Preparation and Management

Unit 4: Working with Milestones and Q-Gates

Working with Milestones and Q-Gates
Example of project structure in Build projects

Project structure sample with two waves, and two sprints per wave
Project

Discover
Explore Realize Deploy Run
& Prepare

Wave 1 Wave 2

Sprint 1 Sprint 1
Develop & Develop &
Test Test
Single Single Functional
Sprint 2 Functional Sprint 2 Functional Integration
Develop & Test Develop & Test &
Test Test Regression
Sprint 3 Sprint 3 Test
Develop & Develop &
User User
Test Test
Acceptance Acceptance
Test Test
Show & Tell / Sprint Review

Acceptance Acceptance

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Working with Milestones and Q-Gates
Waves and document KPIs

Requirements Func. spec. Single Func Test

reviewed availability Test completed

Wave N
Preparation Sprint A Sprint B Sprint C Sprint D Wave closing

Scope definition Sprint review Sprint review Sprint review Sprint review Q-Gate Wave-Exit/
Test result validation
In a wave you…: (UAT/int. & reg./key-user feedback)
Performance tests/
▪ Comprise a well-defined functional scope of work Operations feasibility test
packages to define what needs to be done
▪ Start with scope definition and a preparation time Legend
= Q-Gate
– Provide at least the functional specification required
= Milestone
to start the first sprint of the wave = Customer-facing
▪ Execute functional integration testing = Bus. Process Expert
= Development
▪ End with the Q-Gate “Wave exit-criteria fulfilment” for
passing the Q-Gate Work package
assigned to a wave
receiving milestones from
wave as default due dates
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Working with Milestones and Q-Gates
Sprints and document KPIs

Func. spec. CA Integration test Show & Tell Backlog prep

availability sprint B sprint B sprint D

Business Process Expert

Sprint C
Development
Backlog Tech. design Build Unit test Sprint Sprint C closing /
availability sprint C available completed completed review Sprint C retrospective /
Show & Tell
readiness decision/
In a sprint you…: Sprint start D /
▪ Comprise a well-defined scope of work items
to define how to do it
▪ Start with sprint backlog definition and Legend
prioritizing the work items = Q-Gate
= Milestone
▪ Provide technical design papers and software = Customer-facing
developments for review in show and tell = Bus. Process Expert
sessions = Development
▪ Execute unit test Work package
▪ End with sprint review before passing the assigned to a wave
receiving milestones from
Q-Gate “sprint closing”
wave as default due dates
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Working with Milestones and Q-Gates
Sign off tasks or deliverables to pass the Q-Gates

When all task and checklist

deliverables are delivered,
maintain ‘Status’ and ‘Severity’ of
the Q-Gates
▪ Change Status to ‘completed’ to
signify that the tasks are done
▪ Change Severity to ‘ok’ to signify a
green status on the project structure
▪ The status change is reported to the
Solution Readiness Dashboard →
Schedule Tile

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Working with Milestones and Q-Gates
Demo

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Working with Milestones and Q-Gates
Maintain and release Q-Gates (in ITPPM)

To make the date for the next Q-Gate visible

on the Solution Readiness Dashboard 2

▪ Enter date for Finish Constraint

1 3

2
▪ Change the status to ‘Released’

3
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Working with Milestones and Q-Gates
Maintenance of wave / sprint start / end dates

1. Switch to Edit mode for project

2. Select relevant project element, e.g. Wave
3. Dates can be edited, e.g. while checking ‘Release Go-Live’ dates and Gantt chart

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Working with Milestones and Q-Gates
Maintenance of milestones

1. Switch to Edit mode

for project
2. Select relevant
milestone
3. Specify end date of
milestone
4. Check Gantt chart
5. Repeat steps 2-4 for
all relevant milestones
(e.g. next wave /
sprint)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.