#major implementation

Having run into some struggles lately while working with clients, I wanted to offer some advice for anyone working on a major or complex IT implementation.

Understand the Project Scope. Before your first meeting, make sure you have a clear understanding of what the project is all about. Review any project charters, statements of work (SOWs), project plans, or initial proposals. Know the key objectives, deliverables, and timelines. Stupid Personal Anecdote Time (SPAT): Last year at some point I was implementing a complete re-haul of a major company's email security. On the first call the primary technical contact was the only one from the client side who showed up, and he had no idea what was happening on the project. We ended up cancelling the first call after 5 of the scheduled 60 minutes, and we didn't have our next call with the appropriate resources until 2 weeks later. It turns out his CISO had received the initial scheduling/scoping email and forwarded it to him with no instructions.

Internal Stakeholder Alignment Identify the key stakeholders on your side of the business, I.E. who will be involved. This includes users, department heads, and anyone who will be impacted by the new system or process. Ensure they are aware of the project and their role in it. SPAT: Having been on multiple projects where weeks of time are wasted due to customer-uttered lines like "Oh, we'll have to involve Network Security and they need at least 2 weeks lead time", I strongly recommend the "if you're not sure, ask" approach.