Salesforce Pivotal Tracker Workflow Diagram There isn’t much complexity to this but this is something that a lot of teams seem to have trouble adopting a standardized process with. I think from what I have seen this can come down to the Roles on the various teams, as a one person developer team may not need to promote their code to 3 sandboxes, etc. This particular process would be a minimal Dev Sandbox, and UAT / Staging sandbox for acceptance Testing. It also supports a QA Step, which is a big piece of functionality that can help inject Quality processes into existing Salesforce and Pivotal Tracker teams’ workflows. The reviews process can an awesome QA addition to workflows that you can read more about here. If you are interested in diagramming overall, salesforce is starting to put out documentation ABOUT documentation on their architects site. Diagramming is an awesome skill to have and nips any weird stalemates with requirements in the bud. While a non technical user can definitely have issues reading Code, diagrams bridge the gap and allow for a visual way to show ideas and I am a huge fan.
A Proposed Workflow for Pivotal Tracker and Salesforce Development Processes
