[spb_text_block animation="none" animation_delay="0" simplified_controls="yes" custom_css_percentage="no" padding_vertical="0" padding_horizontal="0" margin_vertical="0" custom_css="margin-top: 0px;margin-bottom: 0px;" border_size="0" border_styling_global="default" width="1/1" el_position="first last"]

Methodology Overview

ValuePath​ is Sapient i7’s proven process for quickly and effectively delivering Salesforce projects. Our approach follows the principles of Agile Delivery. Unlike traditional waterfall methods that keep stakeholders waiting until late in the project to see and touch a solution, agile projects deliver in small, frequent increments. This empowers end users to get their hands on the system and provide valuable feedback early and often, ultimately steering the solution to best fit their needs.

Embracing Change

A core principle of agile development is welcoming requirement changes and refinement along the way, rather than trying to fix everything at the start. ValuePath recognises that circumstances change over the course of a project - new technologies arise, legislation and regulation are introduced. By revisiting a product backlog of requirements when planning each development sprint, while also considering end user feedback, the team can quickly adjust their approach to meet customer wants and needs. To enable this, ValuePath defines a key project role of Product Owner to be the client’s voice of all stakeholders to the development team.


While agile methodologies like ValuePath are designed to handle change, these projects actually require more discipline and adherence to time-boxed schedules and ceremonies than traditional waterfall implementations. While the solution itself is flexible and able to evolve to best meet needs of the end users, the project follows a strict cadence of ceremonies to support this. Agile leverages the power of time-boxing to keep projects on schedule and ensure teams are motivated and focused with their efforts. Agile projects require end users to test and accept the solution increments after each sprint. Agile also requires the team to meet after each sprint and reflect on what is working, and where to improve how the team operates.

Agile benefits over Waterfall methodologies:

●  Lower Risk – client participation throughout the project, client gets to see the solution early and often

●  Flexibility – client can adjust course as needs evolve or become more clear

●  Productivity – high-priority items are built first and less time is spent on documentation, more on working software

●  Higher Quality – testing built into each Sprint, clients interact with the software immediately

●  Reduced Time to Market – can go live after any Sprint delivering a shippable produce

●  More Fun – sustainable pace for client and team with more interaction

●  Delighted customers – change is expected. Accommodating new ideas if other ideas of lower priority are pushed to a future release

●  Improved return on investment – since the most important ideas are prioritised and built first, and each release is potentially shippable, clients can maximise their ROI and stop when it gets diminished

●  Reduced costs – the highly collaborative nature of the approach, and focus on working software over documentation, creates efficience

●  Fast results – see results every 2-3 weeks

●  Confidence to succeed in a complex world – big, complex problems are broken into smaller pieces