-
Project Management: Da Vinci’s Requirements
May 25, 2013
-
3 Smart Leadership Secrets To Increase Employee Engagement
May 24, 2013
-
Project Management on the Far Side of Complexity
May 24, 2013
-
How-to Guide: Change in Project Management
May 23, 2013
-
How Much Project Management Is needed in a Federated Organization?
May 23, 2013
-
Become a Proactive Project Manager
May 22, 2013
-
Project Management - Communicating Successfully
May 22, 2013
-
Talk Like a Project Manager
May 21, 2013
-
How to Project Manage a Pyramid
May 21, 2013
-
The Art of Project Management: Scale
May 20, 2013
Defining the Scope in IT Projects - Part I
March 24, 2008 | Author: PM Hut | Filed under: Project Scope Management, Scope Management
Defining the Scope in IT Projects - Part I (#1 in the series Defining the Scope in IT Projects)
By Neville Turbit - Project Perfect
Scope vs Time & Cost
When people talk about scope, they immediately think time and cost. Time and cost are outputs of scope. Determining scope is a different exercise. In the context of this white paper, when we talk about defining the scope, we are talking about developing a common understanding as to what is included in, or excluded from, a project. We are not talking about deciding how long it will take, or how much it will cost. That comes after the scope is defined.
If we were looking for a car, we would first define the scope. For example we want a 4-cylinder front wheel drive with seating for 2 adults and 2 children, and less than 2 years old. Maybe you also want it to be a red convertible.
Having defined the scope, you can calculate cost and time. How much you will have to spend and how long you will take to buy it. If you get the scope wrong, the time and cost will be wrong.
Why is Scope important?
Anyone who has ever done a project will have tales of how scope changes caused grief. Scope is bound to change, and this is to be expected. As the detail becomes clearer, more complications creep in. These are not foreseeable at the start and hopefully we build in a contingency for what we cannot see.
The scope changes that usually cause problems are those where the perception of what was in and out of scope was different between various parties. The Project Manager assumed there would only be four or five reports, and the business assumed ten to twenty. Nobody felt it was worth talking about because they assumed the other person thought the same way they did.
Project Perfect is a project management software and project infrastructure consulting organisation based in Sydney Australia. Their focus is to provide creative yet pragmatic solutions to Project Management issues as well as to set up the infrastructure an organisation requires to successfully manage projects.
Project Perfect sell “Project Administrator” software, which is a tool to assist organisations better manage project risks, issues, budgets, scope, documentation planning and scheduling. They also created a technique for gathering requirements called “Method H”, and sell software to support the technique. For more information on Project tools or Project Management visit www.projectperfect.com.au
Related Articles
- Defining the Scope in IT Projects - Part II
- Defining the Scope in IT Projects - Part VII - Other Considerations
- Defining the Scope in IT Projects - Part IV - Define the Functionality
- Defining the Scope in IT Projects - Part VIII - Other Work
- Defining the Scope in IT Projects - Part III - Define Deliverables
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized
1 person has left a comment
[...] Defining the Scope in IT Projects - Part II [...]