How to use SAP Activate Roadmaps as project template for Focused Build
Focused Build for SAP Solution Manager is a ready-to-run and integrated solution to manage requirements and software development in large, agile projects. On top of that, SAP Activate provides the methodology and implementation content.
The SAP Activate methodology is SAP’s recommended implementation methodology when implementing SAP Products, for example SAP S/4HANA. The provided roadmaps contain lists of deliverables for each phase, a process description in the form of tasks as well as accelerators like templates, examples, guides or web links in an easy consumable way to help customers to perform the implementations efficient and simple. The SAP Activate Roadmaps can be checked online via Roadmap Viewer.
Key Terms in the Activate Roadmap:
Phases are stages of the project. At the end of each phase, a quality gate exists to verify the completion of the deliverables.
A workstream is a collection of related deliverables that show time relationships within a project and among other streams. Streams can span phases and are not necessarily dependent on phase starts and end.
A deliverable is an outcome that is delivered during the course of the project. Several deliverables are included within a work stream.
A task is work to be performed. One or several tasks comprise a deliverable.
An accelerator is a document, template, or a web-link that helps a consultant, a customer, or the PM perform the task and complete the work faster or with less effort.
More filter groups: Different road maps provide additional groups to filter the content (e.g. Services in the transition to SAP S/4HANA road map)
SAP offers three types of Roadmaps:
Cloud specific – methodologies for the implementation of and transition to specific SAP Solutions in the cloud
On-premise specific – methodologies for the implementation of and transition to specific SAP Solution deployed on premise
General – generic methodologies that guide you through the implementation of SAP products in general without having the focus on a specific product
An existing document SAP Activate and Focused Build – Working Together describes how SAP Activate and Focused Build can be aligned from a methodology point of view.
With some new features which have been provided by Focused Build SP8 / SAP Solution Manager 7.2 FPS13 it is finally possible to easily setup projects using SAP Activate project templates and convert them to Focused Build projects reusing the SAP Activate content.
In this blog post I would like to provide some guidance on how to use SAP Activate Roadmaps as a project template for Focused Build and work on related project task in parallel to the build activities using Requirements, Work Packages and Work items. Managing both in the same project(s) provides a holistic view and full transparency on all activities via Solution Readiness Dashboard.
Main/ Build Project versa Single Project approach
See detail presentation available in Support Portal starting at page 12: Focused Build – Project Management presentation
Which Focused Build projects should get the SAP Activate Roadmap content?
In case you choose a Main / Build Project approach you have several options in which projects the Activate content should be part of
- Main and all Build Projects
- only in Main Project
- Main and selected Build Projects
For each project with SAP Activate content you can follow the chapter ‘Prepare Activate Project template for Focused Build’.
For projects without SAP Activate content you can use the standard way to create projects either via ‘Create Project by Template’ or ‘by User Input’ considering the SAP Activate project schedule.
- Check in SPRO if Task Type ‘Engagement Task’ is part of the Focused Build Project Types
- Add Task Type ‘Engagement Task’ to the visibility customizing for UI5 app
Prepare Activate Project template for Focused Build
- Download the roadmap that fits to your solution and implementation approach from Roadmap viewer: https://go.support.sap.com/roadmapviewer/
- After the download of the zip-file open it and extract the xml-file for Solution Manager 7.2
- In Solution Manager Launchpad open ‘My Projects – Project Management’ tile
and import the project template (XML-file) from extraction folder ‘Upload_to_SAP_Solution_Manager’
- Select in the dropdown for “Application” XML-File, then choose the xml-file which you have extracted and click on “Import Selected Data”.
- In the section “Data for Import” make sure to select “Structure, Resources and Resource Assignment”, afterwards click on “Check.
- If the check was successful and no errors occurred, the project import can be started via the “Import”-button.
- When the import was successful the Import Project Popup can be closed. In the Projects-application, switch to the tab “Last Used Projects”. From there the imported project can be opened.
Change Project / Phase Types
- Open the imported project
- Change Project Name and Number according to your needs and change project type from Engagement Project to one of the Focused Build project types: Main, Single or Build Project
- Change the phase type of all Phases except ‘Realize’ to ‘Common Phase for Focused Build Projects’
- Change the phase type of ‘Realize’ Phase to ‘Sprint Planning
- Select Project Header and then ‘Reset all Constraints’ on to clean dates coming from template
- Adjust Project Start Date to your need and make sure the end date has no finish constraint
- Select ‘Schedule’ to update calculated dates for your project
Assign Release to Project and create Waves
- In the Launchpad open the app ‘Project Management – Focused Build Project’
- Select the project you imported before
- Switch to Edit Mode and assign Actual Release on Project Header
- Select Phase ‘Realize’ Mode and select (+) button ‘Create New Wave’
- Enter required data for the new wave and click on ‘Create’
If Release field is empty, the Project/Release assignment is inherited. Further Waves can be added accordingly, depending on your needs.
- If you have chosen a Main / Build Project approach you need to assign all created Build Projects (with or without SAP Activate content) to your Main Project
- Adjust the project structure and schedule to your needs and finally check that the Release assignment and timing of phases and waves are in sync.
- Before you can assign Work Packages to the Build Projects or Single Project, please set the status to ‘Released’. Same for the Sprint to be able to assign Work Items.
Optional Fiori app ‘Confirm Project Tasks‘ can be used by project team members
More Detailed Product Features and Implementation Information in SAP Fiori Apps Reference Library:
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/ and enter App ID: ‘F0284’ in search field.
Ensure you select ‘SAP Business Suite’ as product line to get the right documentation of Product Features and Implementation Information. Select the latest Delivery Q3/2016.
Excellent blog post Reiner, very well written! Thanks for sharing!
Reiner very helpful insight.
A question for you. When you import an Activate project template directly were you still able to get the Focused build Milestones and KPIs?
thanks for your feedback.
The Focused Build Milestones do not come from the Activate Project template but will be created implicitly with the 'Create New Wave' dialog.
Hope this answers your question.
Best Regards Reiner
I noticed the project plan template is only available on the SAP Activate Methodology for Transition to SAP S/4HANA roadmap. Is it fait to say you can use this also for the cloud specific methodology items also or is there another template set to use?
Focused Build started with the focus on Greenfield On Premise implementations. Here also the general methodology roadmap 'SAP Activate Methodology for Business Suite and On-Premise- Agile and Waterfall' was recommended next to the Transition Roadmaps, that can be used for our Conversion use case in Focused Build.
If we are talking about S/4HANA Private Cloud edition as part of RISE with SAP program, 'SAP Activate Methodology for RISE with SAP S/4HANA Cloud, private edition' should be used.
All roadmaps which do not have a template for SAP Solution Manager (XML) are typically for Public Cloud solutions. Here you can directly use the roadmap as task templates in SAP Cloud ALM.
Hope this helps.
Hi Reiner, very good blog.
I understand that with the blog procedure you can create projects based on the agile roadmap.
But, I need to be able to modify this roadmap (change some tasks, translate it, etc) and then you can export it to another Solman.
Is there any way to create based on the modified project, create a new Focused Build custom TEMPLATE?
Thank you very much
Hi Federico, thanks for the feedback.
You can modify the roadmap template to your needs. After you did your modifications, exported and imported it to the target Solution Manager, you can follow the procedure starting at blog section 'Change Project / Phase Types'.
Hope this helps.
We want to download the Project Plan from Road Map and add our custom tasks and activities but the accepted format to Solution manager is only XML , then how can we add custom lines ?
When we download the Project Plan , the accelerator links get broken so how can we get the accelerator links downloaded to SolMan when we upload from "Roadmap"?
Hi, you can adjust the project template, e.g. add custom lines, add Common Tasks etc., after import into Solution Manager. Unfortunately the accelerator links only work correctly in the roadmap viewer.
Thank you . Is there way to mass load all custom tasks as one time activity to Solution Manager as customization in SolMan Project Management is a time taking task and manually have to be done . Moreover , if we want to do the same for different customers, it will be repetitive.
Any option to Add custom tasks to a File ( Excel) and load to SolMan as one time Load then it is more or less like PMO task rather than SolMan Expert task?
There is an Excel upload feature in PPM, but the required Excel format is not intuitive to use. You could achieve your goal in importing the original roadmap to Solman, then adjusting content in PPM so it fits for various customers. Then you can export it again to be used as your own template to be re-used for multiple customers.
Thanks a lot Reiner..
We have used this widely in two projects. My 10 cents is that this is great for SAP eco-System, but projects are wider and the refuse of SAP to open up the Collaboration Diagrams to be edited in non SAP tool, and the enforce to use Signavio makes extremely difficult to convince our users. This si the story of never made perfect products - started from SAP Enterprise Designer, than Solman Document app, improved a little bit Focused Build and now the Cloud ALM (CALM) - I need to advice to SAP Labs guys and marketing department that in the enterprise the selling cycle is 5 years.
On the positive side - this jump from the product to product provides us, the SAP Build Partners, an opportunity for closing gaps. But we need to open-up the SAP Products black box and ask you to make it more extensible. Happy Holidays to everyone!!!