For many people, it seems counter-intuitive to begin a project by looking at the end-state. That is, however, precisely what needs to be done. One of the most important steps in any project management engagement is to clearly, and precisely, define what the project result should be. Whether it is a complex e-commerce website or a simple business card, this process must happen.
How is this done?
First, a clear understanding of expectations must be reached with all stakeholders involved. If you are building a website for a client, after the initial proposal and cursory discovery process, a very serious conversation must happen. During this discovery phase, among other things, a site-map will be generated, a content creation plan will be generated, and a list of functional elements will be drafted. From here, and this is the part that most people overlook, the QA plan must be created. By defining the testing criteria at this early, pre-development stage, build efforts can be directed properly and efficiently focused.
How detailed should this QA plan be?
As a project manager, ask yourself this one simple question: “Am I willing to gamble that my definition of ‘done’ is the same as my client’s definition of ‘done?’ ” Another way to look at this is to review your previous projects. Have you ever asked for client sign-off on a site, only for that client to ask for features that you didn’t build, but were discussed? The level of detail in the QA plan will be directly proportional to the complexity of the project, and your own risk tolerance level. If you don’t mind last minute additions, possible rework, frayed nerves, and, possibly, ill will, then don’t plan ahead.
Stanley Communications is a full-service technology partner. From information systems to web applications, we have the skill and knowledge to help you succeed.