Christopher GarstinProduct Manager| Netsweeper Inc.Kitchener, Ontario, Canada
When launching a project (with a client) where the requirements are unknown and the requirement gathering/definition effort will occur as part of the billable project, is a Statement of Work the right document to use?
What should you keep in mind if creating a Statement of Work, and you do not know what is meant to be delivered? Saving Changes...
In such circumstances where you are working in the unknown and the client is unsure what the final product will look like, you must agree with the client a 'roadmap' as to how you are going to approach the situation in order to distil down exactly what is being sought. This will also have a bearing on the type of methodology that you will use on the project, that being maybe many small incremental will be required in a short period of time in order to flesh out some of the requirements of the project, thus SCRUM methodology. The statement Of Works is a high level document that does not spell out in detail how you are going to get to a specific point but merely what work has been agreed between client and project manager. Saving Changes...
It may also depends on what type of contract vehicle you are planning to use (fixed versus reimbursable) for your project. You may include multiple optional tasks in the SOW to have flexibility, language to modify the SOW based on the specific set of milestones, etc. Saving Changes...
Christopher GarstinProduct Manager| Netsweeper Inc.Kitchener, Ontario, Canada
Thanks everyone for all the comments. We've decided to go with the two-phase approach. We are working through the Elicitation Phase now, governed by one SOW, and will then move into the Development Phase, governed by another SOW.
While the process is something new to this company, with some apprehension (and confusion) from my colleagues, it's serving the purpose of making sure the client is engaged and accountable to deliver meaningful requirements.
Thanks again for all the feedback! Saving Changes...
Manuel PerezProject Management Coordinator| Las Vegas Valley Water DistrictNorth Las Vegas, Nv, United States
I have to say that there must be a high-level scope statement or the project would not exist! Requirements are usually developed as part of the project. For example, I worked on a project for which replacement of a ships navigating system was needed. The initial scope was to develop a navigation system that could be deployed throughout the entire fleet. Also, the navigation system needed to allow seamless integration with a Command and Control application.
The requirements were developed after the project was given the go ahead for preliminary design and evaluation. During the requirements development then you start listing all of the functionality (i.e. Must Allow user to complete a fix, must alert of danger of collision, etc…) And the breakdown of requirements continues until all stakeholders agree that all possible functions have been addressed.
Then you develop storyboards to model how the functionality should be implemented. Finally, once the requirements and specifications are complete, they are included as part of the scope of work to start the software development and deployment. Saving Changes...
