The team at 37 Signals posted about a change in their development practices:
We recently decided to stop diving in too deep on tasks right away. Instead, we’re going for four hour chunks upfront. We start work on a task and then, after the first four hours, come up for air.
That is an absolutely terrific idea and one that you should consider implementing – I know I will.
So how does this apply to CRM?
As I tell my customers and other Microsoft Partners with whom I work, there are almost always two or three different ways to do everything within CRM. All of which are perfectly viable solutions. The trick is knowing which particular solution best fits the problem you are trying to solve.
The really tricky part is that sometimes what you know is the best solution, turns out to actually be the second-best solution. A fact that you didn't realize until you started work on it.
Or, if you start off with the phrase, "Well, it shouldn't be that hard," only to find out that while it didn't appear to be that hard, there were hidden factors that you simply could not have known until you actually started the development process.
It is the latter fact that gets most of us in trouble. Sometimes CRM just doesn't work the way you think it should, or the way you would like it to, and it can take quite a bit longer to develop a solution that expected.
So, the next time you jump into CRM solution development, set an alarm for four hours and when it goes off, take a break then reevaluate your progress when you return. Are we on the right track? If so, keep going, if not, find the next best course of action and restart the process.
Loading ...
