Focused Build, the Third
The idea behind Focused Build is a "turnkey", preconfigured solution based on SAP Solution Manager 7.2 that implements the Scaled Agile Framework (SAFe) as a project methodology.
The configuration is based on SAP's experience, offers a best-practice approach, and fully maps the requirement-to-deploy (R2D) process. Thus, for example, S/4 Hana implementation projects can be carried out in an agile mode with best-practice content from SAP Activate.
In project management, the integration has been further improved. For example, the project overview page has been enhanced with improved filter options and variants. Phases and Q-Gates have been added to the Gantt chart so that they can be mapped in the diagram.
In addition, project risks have been integrated into the diagram. This means that project risks can be maintained and viewed directly in the Gantt. However, the greatest work simplification in project management is the direct navigation to the associated work packages (called work packages) and work items (called work items).
In Process Management, the handling of documents has been greatly improved. Since Service Pack 3, conflicts in a document are displayed directly in DropDoc. For example, a conflict always arises when a document has been edited in different branches.
Now this conflict situation is displayed directly in the DropDoc area and the possibility to resolve these conflicts is offered. In addition, DropDoc has been integrated into the Work Package and Work Item display.
For example, the required documents are automatically created based on defined KPIs as soon as a new work item is created. In conjunction with the MyDocuments app, this makes work much easier.
An upload function is now offered in Requirement Management. This means you can upload requirements from another system or sample content from the Model Company.
This means that you do not have to start your project from scratch, but can draw on SAP's project experience as a basis for your own project.
The long overdue email notification is now also available. For example, developers are notified by email when a work item is assigned to them. The tester is notified directly when a work item reaches the "To Be Tested" status.
In addition to e-mail notification, the handling of defect corrections has also been simplified. You can create defect corrections during the sprint directly from the work item without a test plan and test package.
This automatically sets the Work Package to the "In Repair" status. This means that you can also manage defect corrections without Test Suite Integration. Low-priority defect corrections are automatically transferred to the next wave when the release cycle is set to the "Hypercare" status.
Integration with test management has also been improved with SP 3. In the Work Package display, there is a new Test Management tab that shows you the test packages and test plans for this Work Package directly.
The display itself is linked, so you can jump directly to the test plan, for example. A search field has been implemented in the "My Test Execution" app to make it easier to find a specific test case. Also, since this release, automated test cases can be executed directly from the app.
The ScrumBoard API has been extended to include Defect Corrections. This means that you can now create a Kanban board for a change cycle and thus, for example, process the defect corrections easily and efficiently in the hypercare phase of the project.
SP 3 consists of many enhancements that make work easier for project management, developers and testers. And all of this is already preconfigured and free of charge for all customers from 2020.