When doing a Salesforce discovery project, the deliverables are usually a series of documents. Here are the usual suspects, sometimes with different names:
- System Landscape
- Data Model
- Security Model
- Sandbox Management
- Data Migration Strategy
- User Flows
- User Stories
- Test Strategy
- Training Plan
- Project Plan
In one particular project I’m finishing up, these documents were originally written in Google Docs. When they were submitted to the client, they were exported as MS Docs and named v1.0.
Then they were copied to “v1.0 – review” in Google Docs to allow the client to comment. Changes were made in v1.1, another Google Socs. Then we submitted v1.1 as MS Docs and named v2.0. “v2.0 – review” was created and the process above was repeated until v3.0 was submitted.
The takeaway
There’s no need to make document management overly complicated. In this case, it felt like we could have used a source code repository and merged our changes back into the main branch 🙂
If you start with Google Docs (and I highly recommend this if you have multiple authors working remotely), it’s OK to produce static documents as v1.0, v1.1 etc. for the client. But the source documents can remain live documents.
I’m curious, how do you manage documents?