CX Works

CX Works brings the most relevant leading practices to you.
It is a single portal of curated, field-tested and SAP-verified expertise for SAP Customer Experience solutions

Project Plan | Template Download

4 min read

As the outcome of the workshop during the Explore phase, the team should have enough information to estimate and plan the project. To plan the project, we need to consider the following; the prioritized list and high-level estimates of the features, resource capacity, resource availabilities, as well as customer dependencies. The project plan will be presented to the customer to set the start and end dates of each release, the go-live window, and other dependent milestones

Table of Contents

Project Planning

Project planning refers to the planning activities required to schedule the proposed release(s) of a project. The project plan will likely include activities dates such as:

  • Release start/end
  • Phase start/end within each release
  • Sprint start/end within the Realize phase
  • Acceptance testing start/end
  • Go-live
  • Performance testing
  • Security testing
  • Content creation 
  • Data migration  

Additionally, the project plan will show dependencies and associated activities and milestones. 

The project/release plan initially created should be refined to include fixed release and phase timescales together with associated go-live dates. Assumptions, made in the original plan, may have changed. Therefore, the plan may need to be modified during the Explore phase workshops to account for agreed changes to capacity and timescales. In some cases, more than one plan may need be presented to provide the customer with a number of options.

The agreed project plan is then provided as an Explore phase deliverable. 

Release Planning

During the Explore phase workshops, the requirements need to be documented, estimated, prioritized and planned using a release wall to create a release roadmap.

The requirements, for each release, should be appropriately categorized as either must-have or should-have requirements and then prioritized. 

Structure of the Artifact

The project plan tab shows the project schedule. The schedule is developed after the resource planning is completed. The project plan includes:

  • Weekly Calendar: The weekly calendar is the top row of the plan. Once the first date of the project is entered, the rest of the dates will be updated automatically.
  • Release(s): The project phases are grouped into release(s). If there are any key milestones, such as go-live and holidays during the release, register them on the plan.
  • Phases: All phases will be included in the plan. Indicate the duration of each phase as calendar blocks.  
  • Sprints: Under the Realize phase section, display the number of sprints and the duration of each sprint.
  • Post go-live Support (optional): If the project team is involved in post go-live support, indicate the duration as part of the Run phase.






Conclusion

The project plan guides the team towards achieving the milestones, and ultimately the launch of the commerce site. The project manager should seek the input from the representatives from each stream.  The plan should receive buy-in from the team before it gets finalized.  The project plan is then communicated to the team members and made available during the course of the project. 

Overlay