Dan KahoProject Manager| Niceware International LLCBrookfield, Wi, United States
Hello All! I am the Project Manager for a software company. My sales team recently brought me a request that I'm having a hard time wrapping my head around and I'm wondering if any of you have heard of this and, if so, maybe you can help me. Here it goes...
According to my sales manager, the sales team would like a document or spreadsheet that they can supply to the customer that outlines the whole project process... start to finish... even before requirements and resources have been gathered. They basically want proof that we can do the job that we say we can do by outlining the approach that we are going to take to get the job done. In short, they want a generally descriptive document customized for the type of project they are looking to sell.
I argue that I can't provide you a general document when we offer so many different project opportunities (large and small). Do you see the frustration? Have any of you had this kind of request? Am I going crazy not being able to understand it?
Saving Changes...
I think what this customer really is asking for is to see that your company has a mature project delivery methodology and internal processes. Knowing it might give this customer some reassurance that your company is for real and not in business of selling some vaporware. No guarantees of course, but still something. I have been on both sides of this process number of times. You best bet is to either present it yourself with Sales or provide to Sales documented methodology and sample of various deliverables that you develop for the similar project/client. You will need to mask any references to the actual client though.
Good luck! Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Dan, I agree with Alexander. You need to provide the customer with the generic process you go through on identifying project opportunities, classifying their complexity, identifying stakeholders, validating expectations, gathering requirements, specifying and designing them, testing and validating their readiness for deployment and finally the deployment process. I suggest you look at JPACE and Project Headway here on gantthead as they provide a well documented framework for all the above. Saving Changes...
