Today I welcome my good friend, Garry Polmateer as a guest blogger at CRMFYI. Garry is not only a Salesforce community rockstar, but he’s planned and executed some great Salesforce implementations, especially in the nonprofit arena. It’s always great to learn from the successes of others and I know you’ll pick up something from his ideas here.
|
Stop. Drop. Roll. You remember the drill from elementary school, if you happen to find yourself on fire, Stop. Drop. Roll. Now don’t get me wrong, Salesforce.com is an amazing, fast, and nimble platform to make things happen for your business, but with great power comes great responsibility. As the system administrator, sometimes your answer is “yes”, sometimes it is “no”, and sometimes (and often) it should be “Let’s think about what you’re really asking first”
I propose the following maxim: Stop. Think. Do. It’s easy to say “Sure, I can do that”, and then wire new functionality into your system, but did you stop and think about all of the ramifications, dependencies, maintenance, training, and things that can go wrong with your proposed solution? Let’s put our Business Analyst (BA) hats on and dissect, the simple act of making coffee. Before you proceed any further, take a minute and write down how to make a cup of coffee with your favorite coffee machine. It probably goes something like this: Fill the carafe with water, dump it in the machine, put in a new filter, add 3 scoops, push the red button, wait, pour, flavor to taste. These are great instructions if you’re telling someone how to do something and they are familiar with making coffee. What you are not doing is building a process so that someone who does not even know what coffee is can understand it. You are making gross assumptions about the abilities of the user and all systems involved. Any breakage in these systems will cause a total failure because the weaknesses have not been identified, nor have contingency plans. Here’s a few questions I’d ask regarding the coffee making process: What kind of water are we starting with? (Tap Water, Filtered Water, Distilled Water) And these are just unknowns about the materials and process when things are working properly! What about when things are not working properly, then what happens? What happens if you turn on the faucet and no water comes out? Making a cup of coffee is pretty forgiving, generally the process works. Sometimes it tastes good, and sometimes it tastes bad, but you still usually wind up with something resembling coffee. However, in Salesforce, or any IT project, when something “Tastes Bad”, it generally does not work at all. Instead of being in a gray zone, we’re stuck with zeroes and ones. If any step of the process is short of perfect, it will break the entire process. So let’s try to make sense of the coffee making process from a simple Business Analyst tool called a Use Case. In short, a Use Case is a software modeling tool that creates a path of an interaction between system components with a useful outcome. Click Here to read the full wikipedia article. http://en.wikipedia.org/wiki/Use_case A short overview of some simple use case terms: Title: What is this use case called With this in mind, I’ll share one lightweight example of the coffee making process at a user level: UC0 - Make the Perfect Cup of Coffee
Extensions One note – bold text indicates a reference to another use case. So, filling the carafe with water could be its own use case with multiple sub steps, each sub step having its own set of extensions. What is the advantage of documenting requirements in this format? During my consulting practice, using this format of noting requirements has a few major advantages:
A few final tips for use case writing and resources
Thanks everyone for reading, would love to hear if you have ever written documentation with Use Cases and what your results were, and if you have any tips or resources to add to the above. -Garry Garry Polmateer, CAE |



If you
Earlier this year, I wrote about 
The future of business applications is upon us. It’s a world where your data comes alive, those who log into your applications are people, not just users, your team’s past work is leveraged into future solutions and even proactively fed to those who need it, and you truly collaborate with not just your direct coworkers, but people from across the company in a way never before possible. This world is
This week I had a chance to write a guest blog post for the Salesforce AppExchange. I chose to write about utilizing networks to become a hero to your Salesforce users.










