The Nexient Delivery Process
Our approach to creating client value
Over years of experience helping clients create and capture value, we’ve continuously honed our approach (more formally known as the Nexient Delivery Process).
Clients have found the model particularly effective in supporting a transition from traditional IT delivery models (focused on operational efficiency and risk mitigation) to a Silicon Valley-style product development model (focused on innovation, digital experience, and driving revenue).
The process comprises four phases in a continuum. For new product innovation, we will go through all four phases; matured products may start anywhere in the process. Every phase incorporates a retrospective, in which we identify the strengths and opportunities we can use to improve future phases and projects.
Using a variety of qualitative and quantitative discovery methods, we define the high-level scope of the product so that the teams are aligned on a common objective. We may conduct one or more of our Applied Innovation summits.
Typical outputs include user personas, product requirements and success criteria, and a roadmap (epics).
Design and scope
Define the MVP
In the design/scoping phase, we conduct rapid prototyping with stakeholders and end users. The goal of this phase is to ensure that the design and features in the minimum viable product (MVP) meet the goals we agreed upon in the Define phase.
Expect to see prioritized user stories, validated mockups and a technical architecture blueprint.
Build the MVP
Small cross-functional teams collaborate in this phase to create, test and refine different features of the product. Working in short bursts or sprints of one to three weeks enables us to incorporate feedback from previous sprints into the next.
You can expect to see regular demonstrations of high quality code with comprehensive unit test coverage, continuous integration and deployment (DevOps) to production or user acceptance environments, and ongoing resource planning based on story burndown (project progress).
Support and learn
Monitor feedback and plan
Because many projects will be expanded from the initial minimum viable product, this is often not the final phase but the beginning of the next cycle to increase usability and business value.
We provide ongoing product support, monitor and analyze user feedback, and refine the product roadmap. Typical tools include a data and user analytics dashboard, product incident backlog and feature enhancement backlog.
Track, share and improve the process
Although we have a number of engagement models, we feel we deliver the best client value when we are accountable for the delivery of a project.
We believe in transparency throughout the engagement, using both traditional governance models (everything from daily standups to quarterly strategic reviews) as well as innovative tools to share progress and productivity.