top of page

Contained Agile Methodology Process (CAMP)™

Hikers High Five

Contact us to learn more about Contained Agile Methodology Process (CAMP)™

Or just drop us a line here

Someone will be in contact with you shortly.

The CAMP framework started when I was asked to explain my process for successfully delivering Salesforce CRM projects.  CAMP was born from my training on creative and design thinking processes, 20+ years of full-stack software development and technical architecture experience, love of the Salesforce eco-system, and my camping adventures, which go back as far as I can remember.

​

So, what is the Contained Agile Methodology Process (CAMP)™?

CAMP is a series of actions taken based on delivery methods that allow the project teams to control scope while moving quickly to deliver innovative, design-forward software solutions that delight your customers while driving value for your company or client. CAMP is used to decide on what to do, when to do it, who to bring along, and what to pack. It is used to determine how to setup your camp and camp rules, establish your touch-tree, and have a great and successful journey (project).

​

CAMP is a trailblazing agile framework that is

tailored specifically for the accelerated delivery

of Salesforce projects.​​

​ â€‹â€‹â€‹â€‹â€‹â€‹â€‹â€‹â€‹â€‹â€‹

CAMP Framework:

CAMP with Words.png
Get Contained Agile (CAMP) Trained

Overview of Delivering Projects

Overview of CAMP.png

Where does CAMP fit into the Agile Framework?

Agile Scrum.png
CAMP.png
Safe.png

Step 1: Embarking on your Journey (Project)

On a typical Salesforce CRM journey, this would be one or more of the following activities in this step:

  • Pre-Sales/Ideation

  • Learning & Clarifying Strategy Roadmap

  • Project Business Case 

  • Project Charter

    • Scope of the work

    • Requirements

    • Proposed timeline

    • Budget

    • Resources

    • Definition of done

    • Project success factors

  • RFP Process/SOW Process

  • Buy needed Software Licenses

  • Contracts signed with Delivery Partner

  • Delivery Team is Identified

  • All Teams are Ready for Discovery Phase

iStock-844497282.jpg

Step 2: Discovery – Who, What, Where and When – this will be where the teams make critical decisions on the 4 W’s of the project.

During a Salesforce CRM journey, the teams would work through the following activities:

  • Who: identify the various business users either client or customer

Possible tools:

Personas

Empathy Maps

Role and Sharing Diagrams

System Authorization Flow diagram

Other Universal Methods of Design as needed

  • What: Exists today, in terms of systems, tools,                                                                               processes (current state)

Possible tools:

System Landscape (current)

Data Model (current)

Swimlanes – Process Mapping

Other Software Methods as needed​

  • Where: the client wants to get to (desired state)

Possible tools:

System Landscape (future)

Data Model (future)

Environment and Release Management Diagram

UI/UX Documents

- Pitch Writing

- Wireframes

- File Structure

- Mockups

- Global Components

- Style Guide

- Prototype

  • When: confirm timeline of project

Possible tools:

​Project Schedule
Outline Project Plan

Step 3: Plan, Prep, and Pack – this is the first of two often-missed critical steps that will set the project up for success. Plan for what will be covered, prep for the journey ahead, and make critical decisions on what will be included in this project.

In a Salesforce CRM journey, this is generally one of my favorite steps. If done well, this step will tighten up what will be delivered, determine when everyone will be prepped and ready to begin the journey, and helps the teams make critical decisions on what will be in scope, (and what will not be in scope). This is the final converging on the where that is going to be delivered in this project.

 

The activities for this step are as follows: 

  • Plan: the various sprints and which user stories are included in the project. Plus, the following:

    • Refine Project Schedule – finalize length of project

    • Refine Project Plan (Travel Itinerary)

    • Risks and Issues Log – identify potential hazards

    • Change Request Management - have a contingency plan for unexpected changes/surprises

    • Finalize Work Breakdown Structure (WBS) for the various software/parts/components that will be needed – Complete Checklist

  • Prep: ensure all teams are trained and ready to go

    • Establish training that is needed before build

    • Ensure training is completed or have a plan for completion

    • Review and practice (if needed) before you start the next step

    • Review and anticipate the Mental State of delivery and client teams

  • Pack: ensure the teams let go of those items that are not part of the journey

    • Not everything can fit into the backpack – only take what is needed for this journey!

    • Critical that the delivery team and client team are all in alignment on this step - Change Management can help with getting the teams aligned if needed.

iStock-1294865347.jpg

Step 4:  Set-up Camp – this is the second of two often-missed critical steps that will set the project up for success.

The activities for this step are as follows:

  • Complete needed documentation

    • Project Communications Plan

    • RACI Matrix - who is Responsible, Accountable, Consulted, and Informed for each task

    • Testing Plan

    • DEV Ops Plan

    • Update/Finalize Project Plan (Travel Itinerary) if needed

    • Finalize and Approve User Stories

    • Finalize number of Sprints needed

  • Set-up your touch-tree and perimeter of the project

    • Clearly specify what is in scope and out of scope – establish final good enough design

    • Change Request Management – clarify that if item is not planned (“Butterfly Garden”) then it will be documented for the next project

    • We stay within the CAMP boundaries keeping the touch-tree in sight to ensure no one goes too far away

  • Set up the Camp Rules

    • We are ALL responsible for Quality

    • We work together as a team – we are all responsible for making the project successful

    • Other rules identified by the delivery and client teams

  • Expect any Weather – be prepared for changes

    • Change Request Management – establish how issues are identified and brought forward

  • Setup ORGs and Development Operation

Step 5: Build & Test – this will be a contained agile build process with continued emphasize around containing scope.

The activities for this step are as follows:

  • Prioritized solution design and features are built, tested, and reviewed with the client for final sign-off. 

  • Use the Contained Agile    method to deliver the build during the sprints:

    • Approved backlog items that are pointed are moved into the upcoming sprints as needed.

    • Duration of each sprint is XX weeks (XX business days).

    • Ensure that the teams are containing scope that was identified in the earlier steps. 

    • Minimize the number of new requirements allowed – only those items that fit within the touch-tree established scope area.

    • Team will create test scripts during each sprint for testing

  • User Acceptance Testing (UAT) will be executed with the following:

    • ​Project Team will support Customer with their User Acceptance Testing. 

    • Customer will document the testing feedback and provide it to Project Team prior to a Testing Feedback Review meeting.

    • Approved UAT Feedback changes will be incorporated into the application.

    • Customer will perform retesting to provide final validation/confirmation that all agreed-upon changes have been completed successfully.

  • Complete Pre-Deployment activities:

    • ​Project team will conduct Train the Trainer sessions

    • Business team will create End user training material

    • Project team will prep Orgs for Go Live

    • Project team will prep data for Go Live as needed

    • IT team will prep integrations for production as needed

    • Finalize Go Live timing and move to production

  • Complete Deployment activities:

    • ​Go Live! Move items to production

    • Project team will migrate data for Go Live as needed

    • IT team will deploy integrations to production as needed

    • Project and Business teams will conduct production validation

  • Complete Post-Deployment activities:

    • ​Training team will conduct training sessions as users are enabled on the new system

    • Review post go live feedback and make critical fixes as needed

  • Keep & Follow Camp Rules – review often

  • Practice Situational Awareness – don’t fall into the trap of poor decision making – always be aware of what’s going on and where you are in the process

  • Don't Panic! – continue to have a plan in place to handle changes

  • Stick to Travel Itinerary – again, if item is not planned (“Butterfly Garden”) then it will be documented for the next journey!

TM

Step 6: Pack-up, Clean-up and Measure Outcomes – this ties up the current scope and allows for measurable outcomes to verify the success of the project.

Complete 1 or more of these activities for this step:

  • Create and deliver the Train the Trainer Content

  • Business Team Trainers will conduct End User Training

  • Delivery Team will conduct knowledge transfer sessions

  • Conduct a Final Review and submit a project sign-off request to Project Sponsor for approval

  • Project team will provide any needed Post Go-Live support

  • Finalize Project Deliverables and complete Administrative Closure

  • Establish and Build Measurable Outcomes – Reporting and Dashboarding

  • Create the Lessons Learned Register

Step 7: Share your Journey – this is an important step to share success to ensure adoption of the solution. 

Complete one or more of these activities for this step: 

  • Finalize Project Deliverables

  • Celebrate Success – share the journey with the project teams, throughout the organization and customers

  • Reinforce Adoption – continuation of Change Management process

  • Write Up a Win Story 

  • Archive Project Documents & Release Resources

Step 8: Plan your Next Journey – There should be projects already identified during the build phase which will need to be assessed and set-up for the next project.

Complete one or more of these activities for this step:

  • Assess the project success by creating a Project Closure Report

  • Conduct a Post-Implementation Review (PIR)

  • Plan Next Journey – review the items identified during build that were possible next projects

  • Review Strategy with Company/Client around next project(s) and potential additional Salesforce solutions

bottom of page