Post Content:
In large-scale CRM implementations, managing solution layers and platform integrity is critical for stability and scalability. At Volvo, we adopted a structured approach to balance platform governance with development agility.
Here’s what worked for us:
✅ Platform vs Dev Solutions
- Platform Solution: Core managed components deployed by the platform team—locked for consistency.
- Dev Solution: Customizations layered on top of the platform solution without breaking its integrity.
✅ Updates vs Upgrades
- Updates: Incremental changes (e.g., adding fields, modifying views) applied safely over the platform layer.
- Upgrades: Full solution replacement—only possible when no immutable platform layer exists.
✅ Using Patches
- Deploy small fixes without re-importing entire solutions.
- Workflow: Create patch → Import → Consolidate via “Clone Solution.”
✅ Governance Strategies
- Collaboration: Align platform and dev teams early.
- Standardization: Separate platform and custom components for clarity.
- Incremental Updates: Prefer updates and patches over full upgrades.
✅ Publisher Strategy
- Multiple Publishers: Better governance, accountability, and audit trails.
- Single Publisher: Simplified upgrades but less oversight.
Key Takeaways:
- Respect platform layers to avoid deployment conflicts.
- Use patches and updates for agility without compromising stability.
- Define clear rules for dependencies, upgrades, and communication across teams.
No comments:
Post a Comment