Consulting Consultants IT Consulting
Search 180systems.com       
News Letter Signup
Home
Portals
ERP
CPM
BPI
CRM
About Us
Our People
References
Clients
Services
Software Selection
Business Process Review
Business Case
Project Management
IT Audit
Corporate Diagnostic
HR Management
IT Infrastructure
Strategic Planning
Technology White Papers
Technology Seminars
News & Articles
180 Blog
ERP Systems1
BI2
PSA3
CRM4
SCM5
BPI6
Business Case
Sarbanes-Oxley
IT Strategy
IT Project Management
Office Productivity
Internet
IT Marketing
IT Security
HR
IT Humour
Buyers Guide
Software Selection
Business Case
Total Cost of Ownership
Software Implementation
Accounting Software
Distribution Software
Manufacturing Software
BI2
PSA3
CRM4
Implementation
Software Reviews
ERP Comparison1
ERP Reviews1
ERP Customer Survey1
BI Comparison2
BI Reviews2
PSA Comparison3
CRM Comparison4
Case Studies
Accounting Systems
Manufacturing Software
PSA3
CRM4
White Papers
ERP1
CPM7
Contact Us
Office
Careers
Site Map

Software Selection, Business Process Improvement and Project Management

Wednesday, July 01, 2009

Managing Scope for Project Success

June 24, 2009 from Project Times – “Ever start a project without a stable foundation for scope? How did it go? To ensure project success, it is essential that scope be unambiguous and carefully managed. This can be accomplished with the Scope Management Process, which provides a formal set of procedures for planning, executing, monitoring and controlling scope…

Basic functions in the Scope Management Process include reviewing the project charter and other documents such as the contract, statement of work and request for proposal…”

180 View – Anyone familiar with project management methodology will already know most of what’s in the article. The main reason for including it is the discussion of where scope is defined. The article suggests the contract and statement of work as a source. It is extremely unlikely that scope will be defined well enough in either of these documents. The article also suggests the request for proposal. I agree with that but it needs to be part of the contract, which it is usually not. If using the RFP as scope, the requirements in the RFP need to be defined specifically enough to avoid misunderstanding later. The requirements should also be prioritized to ensure focus on the most important requirements.

Labels:

0 Comments:

Post a Comment

<< Home

 

 
1enterprise resource planning | 2business intelligence | 3professional services automation
4customer relationship management | 5supply chain management | 6business process re-engineering
  © 2004 One Hundred & Eighty Degrees Systems Limited. All Rights Reserved
Web Site optimized by Toronto Search Engine Optimization | resources