Many a times the project scope document (or Project Blueprint) bites dust after the initial discovery session. The scope document should be the initial plan, carefully evolving as your project moves forward. The success of salesforce.com implementation lies in creating a 'living and breathing' scope document, actively maintained by both the implementation partners as well as the internal project team. The following is a must-have in a working blueprint document or Scope Document:

Shorter is better: Keep sections small without unnecessary creative explana.

Detailed Databased Model & Workflow: These must be always up-to-date prior to any changes being effected in salesforce sandbox. (lack of this document makes it very difficult to carry the project forward in case of new project ownership)

Set (Micro) Milestones upfront: We recommend having weekly milestones speculated and documented. The teams should be held accountable for any misses.

Maintain Active 'In-charge' Status: tAssociating milestones and deliverables to 'general owners' leads to ambiguity and blame games. Maintain a clear ownership of each task from both partner and internal teams perspective.

Keep the Working Blueprint Handy: We encourage using google drives for collaboration and sharing so that this document is starting point of all weekly or bi-weekly checkpoint meetings.