Using workshops to define project scope

I have found while working with business groups with limited IT knowledge that it is not sufficient to get signoff of the development project scope by the stakeholders individually. This leads to unexpected

Requires Free Membership to View

misinterpretations and scope creep.

A more effective approach is to gather the stakeholders together and workshop the scope. This gives you the opportunity to respond to any differences of opinion in a forum environment which maximizes the possibility of a common understanding of the scope. In a workshop peer pressure can be used to advantage once consensus has been reached to bring any radical ideas back into line. Remember to record and distribute minutes from the workshop as a future reminder of the scope agreed.


This was first published in August 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.