SAP Activate Methodology For Business Suite and On-Premise-Agile and Waterfall
SAP Activate Methodology For Business Suite and On-Premise-Agile and Waterfall
SAP Activate Methodology For Business Suite and On-Premise-Agile and Waterfall
Please note:
Welcome to the SAP Activate Methodology for Business Suite and On-Premise Roadmap .
This roadmap is intended to guide the implementation team through the On-Premise
implementation utilizing Agile Methodologies (Agile implementation utilizes a SCRUM-
based approach to build solutions. This in turn allows for an iterative implementation process
with more flexibility for change). It is comprised of Phases, Deliverables, and Tasks in
accordance with the SAP Activate methodology. In addition, accelerators are linked to the
relevant deliverables and tasks making them easy to consume when they are needed. The
Deliverables and Tasks are listed in sequential order based on the activity start. However,
parallelization is necessary to expedite the implementation.
Note : If you are running the implementation using the Waterfall approach, please use
the Tagging Option to view only deliverables, tasks and accelerators necessary for a
Waterfall implementation. Waterfall implementation utilizes the core concepts of a Waterfall
development methodology. Implementation is completed with all the phases only being
performed once and are more involved than the smaller sprints of an Agile implementation.
1. Discover
The purpose of the Discover phase is to discover the solution capabilities, understand the
business value and benefits of the solution to customer’s business, determine the adoption
strategy and roadmap in alignment with understanding the solution capabilities and product
roadmap.
To conclude the Discover phase of SAP Activate, customers and sales teams agree on :
Implementation scope
Project timelines
Targeted solution model.
Link to Content
2. Prepare
The purpose of this phase is to provide the initial planning and preparation for the project. In
this phase, the project is started, plans are finalized, project team is assigned, and work is
under way to start the project optimally.
Key Prepare Activities:
Link to Content
3. Explore
The purpose of this phase is to perform a fit/gap analysis to validate the solution functionality
included in the project scope and to confirm that the business requirements can be satisfied.
Identified gaps and configuration values are added to the backlog for use in the next phase.
Explore Activities:
In the Explore phase, industry and solution experts from SAP lead a series of structured
show-and-tell and solution design workshops. The goal of these workshops is to review the
best practice functionality of the SAP solution, identify delta requirements or gaps and
document the conceptual design of the to-be delivered SAP enterprise solution. The team
documents all functional and technical requirements, project issues, and gaps in SAP Solution
Manager.
Link to Content
4. Realize
The purpose of this phase is to use a series of iterations to incrementally build and test an
intergrated business and system environment that is based on the business scenarios and
process requirements identified in the previous phase. During this phase, data is loaded,
adoption activites occur, and operations are planned.
Realize Activities:
Establish the solution landscape
Implement the solution in the development environment using incremental build in
time-boxed iterations
Conduct overall end-to-end testing of the solution within the QA environment
Setup production environment
Prepare for data migration and data archiving
Conduct performance testing
Conduct project team and key user training
Finalize end user training materials and documentation
Track and report on value delivery
During Realize phase, the project team uses a series of iterations to incrementally configure,
test, confirm, and document the entire end-to-end solution and to create legacy data
conversion programs. The project team actively works with business representatives to ensure
good fit of the built solution to the requirements from the backlog. Project Team releases
results of multiple iterations to the business users to accelerate time to value and provide
early access to finalized functionality. Each release is thoroughly tested in end-to-end
integration test and user acceptance test.
The project team documents the configuration decisions and solution in the SAP Solution
Manager tool. They also document all development –including interfaces, integration points,
data conversion programs, reports, and any required enhancements – in SAP Solution
Manager. Once these activities are complete for particular release and the team has obtained
business approval, they make the release available in the production environment.
Link to Content
5. Deploy
The purpose of this phase is to setup the production system, confirm customer organization
readiness, and to switch business operations to the new system.
Deploy Activities:
Link to Content
6. Run
The purpose of this phase is to further optimize and automate the operability of the solution.
Operability is the ability to maintain IT systems in a functioning and operating condition,
guaranteeing systems availability and required performance levels to support the execution of
the enterprise’s business operations.
Link to Content