Introduction
2023 marks a big transition in how we Sell and Deliver phase 1 of projects at Pricefx.
We move away from 'hybrid-Agile' to 'hybrid - Waterfall’ with Agile ceremonies during delivery.
You can still refer to the /wiki/spaces/CUST/pages/1343848803.
In this article you will find highlights of changes made to the processes.
In our updated Project Methodology we aim to be prescriptive in both Pricefx and Partner led projects, resulting in short time-to-value Phase 1 projects.
The goal is to go-live within 6 months with sufficient value.
We have end-to-end /wiki/spaces/CEOMGMT/pages/4520411212 with use cases documented, resulting in pre-defined user stories.
Phase 1 is to consist of minimum 80% pre-defined user stories, taken from the Industry Catalogues.
We are to steer the client away from customised solution in Phase 1.
Standard vs. Prescriptive
Standard (agile):
Prescriptive:
Where is the Handover?
As PM, SA/BA start working with the client in Phase1 Delivery Workshop, there is no need for the handover. Unless! there is a team member(s) change.
There will also be no more Foundation Sprint, Preparation and Setup Sprint.
What has traditionally been covered in those sprints is moving to other earlier stages, shown above.
Pre-Sales/Sales
Output | Delivered by |
|---|---|
Project Objective Statement | Account Executive |
Use cases/PDR description | |
Start of Value Roadmap | |
“As is“ process and a Pricefx proposed “To-Be“ process | |
Questionnaire about the data | |
Briefing sheet |
Prescriptive Solution Vision Workshop
Introduction of the Prescriptive approach.
Mapping long term vision of the client to the Pricefx capabilities.
Feature demos.
Customers bases their software choice on this workshop.
Main output is the Value Roadmap.
Output | Delivered by | |
|---|---|---|
80/20 map | Finalisation of Value Roadmap | Solution strategist |
List of Use Cases | ||
Prioritised Use Cases (‘must have’ or ‘nice to have’) | ||
Implementation timeline and sequence of Build | ||
High-level dataflow diagram and list of Data Feeds | ||
Fit-Gap analysis | ||
Price Waterfall (level 1 – Plasma level) | Solution strategist | |
Introduction on data readiness | DRM Advisor | |
Customer/Pricefx/Partner Teams and Governance Model | Partner Team | |
Commercial implementation negotiations on order form | Account Executive | |
Training and Change program discussion | Delivery - Education | |
Phase 1 Delivery Workshop
Detailed scoping workshop for phase 1 to be delivered within 6 months.
PM, SA/BA from Pricefx/Partner must take part in the workshop.
During the workshop:
Line up Use Cases from Industry Catalogue
Review User Stories for each Use Case
Identify Necessary Data Sources for each User Story
Inform client that data readiness is a pre-requisite for project to start
Data readiness timeline defined.
PM is the main housekeeper for this process remanding customer to deliver the data
Team to be set up on the customer side
No requirements or design discussion at the project start.
Everything is ready after Delivery Workshop.
Phase 1 is the Foundation that supports all following phases.
They can be implemented in different orders, as long as the foundation is part of phase 1
With such limited scope, client can focus on data and integration.
Client can be trained to consider the waterfall and outliers.
Phase 1 already brings Value.
Output | Delivered by |
|---|---|
Set of use cases and detailed CE ready user stories to be put into SOW | BA |
Price Waterfall definition (level 2) | |
Data specification complete | PM/SA |
Solution Design and Estimations Review with Product team | |
In-scope and Out-of-scope Phase 1 List of Requirements | Solution Sales |
Initial draft of implementation SOW and negotiations on SoW | |
Change program start (if in scope) | Education |
SoW
One big change here is that PM, SA/BA start working with the client Before SoW is signed.
Sales still responsible for SOW signature but there are less handovers.
PM involved in User Stories + Data Workshop + SOW preparation.
In the SoW:
Use cases from Industry catalogue lined up = standard project
Estimations
Timeline presented in weeks instead of declaration of fixed dates.
List of team member from partner and Pricefx.
Pricefx support is non-negotiable.
Minimal support = weekly call.
The less experienced the partner, the more Pricefx will participate.Mandatory requirements made clear to the client: team members, participation, timely delivery of data and testing
List of possible sanctions, such as project put on pause
All chosen modules need to be in SoW, else they cannot be in the order form.
Aim to find a balance between fast go-live and having a large initial license fee.
Output | Delivered by |
|---|---|
Signed SoW | Solution Sales |
Kick-off date |
Project Initiation
Standard 3 weeks
Client is informed clearly of what is expected of them each week.
Week 1
Meet with client about data and get the first data drop -> if customer not ready, stop and escalate to project sponsors.
Client team presentation.
Check if the team is complete and all roles are represented. A complete list of roles can be found in the Project Gates checklist.Joint preparation of the Kick-off workshop.
If data and team are ready, Partner/Pricefx PM requests to set up Dev and QA environments.
Week 2
Kick-off workshop is to focus on Use Cases from the Industry Catalogue + User Stories refinement
User stories refinement means no changes, only details, measures, data input/outputs specifications.
Expectations management!
Client gets familiar with Partner/Pricefx project methodology.
Clear expectations about testing and team members' response time.
Key users' training.
Inform client that failure to comply shall result in escalation to sponsors.
Initial data load
Week 3
User stories refinement (configuration-ready specification) at least for the Feature Sprint 1
Key users' training.
Feature sprints
1 sprint = 3 weeks. Maximum 4 sprints in the project.
Following good Agile practices. Typical ceremonies in place.
Strong focus on keeping initial scope lean and without changes.
Delays in customer testing should be strong indication to escalations on Steering Committee level.
UAT Preparation sprint
Standard duration 2-3 weeks (depends on the number of feature sprints).
Finalize the user stories‘ acceptance
Upgrade to the latest Pricefx release
Load a full (production like) set of data
Performance sprint
Standard duration 1-2 weeks.
Parallel to the UAT Preparation sprint
Performance testing
Performance enhancements
SIT & UAT sprint
Standard duration 3-6 weeks.
First half is dedivcated to Systems Integration Testing
Still the main goal is end to end testing of the solution
Testing is led by the customer
This phase is the last moment for client to present the plan for introducing Pricefx system to business users.
Preparation of Business go-live together with client.
As the result of this sprint there should be GO/NO GO decision for Business go-live taken on the Steering Committee level.
Cutover Preparation sprint
Standard duration 1-2 weeks.
Strong coordination between customer IT and Pricefx/Partner team
Final check for PROD environment by SA.
Data load to PROD.
Integration switched on by IE.
Smoke testing and Business go-live.
Stabilization sprint
Standard 2 weeks.
The main goal is to finalise the project and hand it over to customer.
Project team allocation is limited and focusing only support and bug fixing.
Project Acceptance Protocol to be agreed upon with the customer.
Pricefx to be paid for idle time in this stage.