Sure Step with Microsoft Office SharePoint Server
Yesterday I delivered a presentation about benefits of Sure Step methodology, as a part of an internal partner academy program. The audience was fantastically interactive, and if anyone of you…
Yesterday I delivered a presentation about benefits of Sure Step methodology, as a part of an internal partner academy program. The audience was fantastically interactive, and if anyone of you…
Implementing a new Microsoft Dynamics solution doesn’t merely introduce a new piece of software into your environment. Yes, the software is an important part, you need to deploy it successfully, configure it as necessary, probably even customize it and change the business logic under the hood.
One component, however, is easily overlooked, and you wouldn’t believe how often it’s not addressed until late. Or too late. It’s the infrastructure.
Infrastructure is tough. It’s not just servers and desktops with some wires, switches and access points in between. Its a lot more. What kind of hardware do you need for your servers or desktops? What kind of performance do you really need? What kind of network layout is optimal for your transaction volume? Should you run the client on desktop machines, or would a remote desktop access be a preferred method? Do you virtualize your servers? What kind of failover capacities do you need? Can you retain any of your old hardware? How many users will use the system? Tomorrow? In five years? What about interfaces and integration to other systems or applications?
A couple of wrong answers, and down you go.
(A short, almost pointless rant about PMBOK vs. Sure Step nonsense)
Once, while preparing an important RFP response, a partner told me they don’t use Sure Step because they use PMI methodology. This made my toenails curl up—when people tell me they are using PMI methodology, they in fact tell me they are using no methodology at all. It’s simple:
Another time a partner told me they preferred PMBOK to Sure Step. Now, while this was a better argument, it was still very much wrong. As if they told me they don’t wear shoes, because they wear footwear.
The degree of fit is an important indicator of your project’s alignment with the standard functionality.
After you determine the degree of fit, and understand what it means for the project, do you just passively accept the findings, or do you do something to make them more favorable?
I’d like to have a BMW X6. A fantastic car. Only, I’d like it to be convertible, because I love the feel of wind in my hair while driving into summer sunset. I could use a glass roof as well, it makes the interior feel much more spacious. And of course, it can’t have that automatic transmission—I don’t care if it’s not a hybrid car, it simply must have the continuously variable transmission, no matter the cost.
I’ll never have a car like this.