A Design Sprint is a formal, four-day workshop where the project team documents problems in the organization and vets their solutions. The team breaks out into smaller segments and brainstorms alternatives to present to the rest of the team. Everyone votes on the best option and works together to vet the chosen solution. In the end, a product scope and an approach are created. These help drive the project charter.

The Project Charter is a statement of the scope, objectives, and participants in a software project. It provides a preliminary delineation of roles and responsibilities, outlines the project's key goals, identifies the main stakeholders, and defines the authority of the project team. The project charter is used throughout the project lifecycle.

A Customer Journey Workshop helps map the customer experience based on different personas. It documents the different types of customers and how they interact with your company. It maps their journey from the time they are a lead through their transition to a customer. The Journey map defines and creates the customer-facing user stories and the experiences each of your customers have when they work with your company.

Business Process Mapping (BPM) completes the mapping development by documenting your internal processes. While the Customer Journey map is external facing, the Business Process map is internal facing and helps fill in the blanks on the user stories for your solution.

User Stories are part of an agile approach that shifts the focus from writing about requirements to talking about them. All agile user stories contain a persona, a goal, and a task to achieve the goal. It also includes acceptance criteria which defines a condition, an action that happened as a result of that condition, and the outcome.

User Story Mapping is the process of determining the return on investment for each user story as well as the relationships between users stories. Many times, you can't complete a user story until other stories have also been completed. These users stories are clustered and organized by ROI so TAI can build a release plan.

Release Planning assumes your CRM implementation will be released in phases and it creates a roadmap for each release based upon sets of user stories and their ROI.

CRM Selection is the process of taking the user stories and mapping them to functional specifications. Software is reviewed based upon how closely the software's functions meet the requirements generated by the users stories.