Home > Managed Services > Project Framework
The Framework Project
Structuring and managing projects that go beyond the scope of the run, without breaking the continuity of your platform.
Strategic Acceleration
The Framework Project is the "build" model of the Texeï Service Centre. It takes over when an evolution becomes too structuring to be absorbed in the current flow: new functional component, redesign of a process, extension to an entity or a country, migration .
A dedicated project organization is then put in place, with appropriate management and, if necessary, the occasional mobilization of experts.
The "Structured Project" applies to initiatives of manageable size, representing less than 60 days of workload. Beyond that, when the scope, duration, or resources required become more significant, the need falls under the category of an Implementation Project, managed within a dedicated project framework.
The two complementary models of the Service Center are TMA (security and evolution) and The envelope (controlled agility).
When to switch to Project-Based Mode
Not all changes are handled in the same way. Some are absorbed into the regular maintenance process without altering the existing organization. Others, due to their scale or cross-functional impact, require upfront planning, scheduling, and their own specific governance structure. Four situations call for the activation of the project model: these are less related to the urgency of the request than to its nature and its implications for the platform.
Ambitious scope
Beyond a certain workload volume, a change can no longer be absorbed into the current workflow without impacting other requests. It requires a specific project structure, with its own schedule, budget, and milestones; managed by the same stakeholders, ensuring continuity with your existing system.
Structuring construction project
Whether it's a new functional component, an extension to an entity, subsidiary, or country, a business process redesign, a third-party system integration, or a migration , these projects have cross-cutting impacts that require upfront design, formalized testing, and change management. They are not maintenance-related.
Continuity preserved
You don't want to have to choose between run and build. The advantage of an integrated Service Center is that you don't have to choose. The project is managed by a dedicated team while the Application Maintenance Team (TMA) continues to secure the existing system, with coordination between the two and a planned maintenance takeover from the design stage.
Controlled trajectory
Avoid the tunnel effect. A poorly defined project is only discovered too late. This approach provides a clear framework, validation milestones, a dedicated committee structure, and intermediate deliverables. You maintain visibility on progress, budget, and risks at every stage.
The methodology for the Framework Project
A five-phase approach, based on the same principles as the rest of the Service Centre: co-construction with the business lines, "standard first" arbitration and organised knowledge transfer.
1
Framing and qualification
Define the need before quantifying it. Experts analyze the request, challenge the stated need, assess its impact on existing systems, and estimate the workload. This phase produces the project scoping document: scope, objectives, constraints, assumptions, macro-planning, and budget. It determines the project's transition and serves as a reference throughout the project.
Design and arbitration of solutions
Design by systematically prioritizing the vendor's standard, then ecosystem solutions, before considering custom development. Every decision is clearly explained and documented: what is retained, what is discarded, and why. This guarantees a platform that will remain maintainable after project delivery.
Iterative implementation
Build incrementally, with regular demonstrations to business users, rather than a single final delivery. Configuration, custom development, and technical interfaces are created, tested, and documented continuously. Discrepancies are identified early, when they are still relatively inexpensive to fix.
Recipe and production
Formalize the process with users, prepare the switchover, and ensure a secure production deployment: deployment plan, environment management, data migration if necessary, and user support during onboarding. No production deployment is disconnected from the vendor's release schedule or the maintenance and support (TMA) schedule.
Transfer and resumption of maintenance
Closing a project means ensuring its long-term viability. Documentation is handed over, knowledge is transferred to the operations team and client representatives, and the new scope is integrated into the maintenance framework. The project doesn't create an isolated system; it expands the secured perimeter.
Insights
FAQ
Contact us if you would like more information.
When does a Salesforce evolution become a structured project?
Beyond approximately 30 days of estimated workload, or when the project has cross-cutting impacts requiring upstream design, formalized testing and change management.
Is it possible to carry out a project while retaining one's TMA (Therapeutic Maintenance Agreement)?
Yes, and that's the recommended setup. The project structure works in parallel with the run team, with coordination between the two and a planned maintenance takeover from the initial scoping stage.
How to avoid the tunnel effect on a Salesforce project?
Through iterative implementation with regular demonstrations to the business, intermediate deliverables and explicit validation milestones, rather than a single delivery at the end of the process.
What happens to the delivered area after the project?
It is documented, transferred to the run team and client contacts, and then integrated into the maintenance system. The project expands the secure perimeter instead of creating an isolated island.
They trust.