TKO Software | Policy | Procedure | SOP Software | Business Template| Quality | Manuals
Document your systems and procedures
  • Features
  • Pricing
  • FREE TRIAL
  • Templates
  • Documents
  • Contact Us
  • Log in
Select Page ...

Discussing and Identifying Customer Requirements (agreeing Scope)

Discussing and Identifying Customer Requirements (agreeing Scope)

Sales Process
Download Now!

Purpose

Agree on key deliverables in the customers requirements and document them

Background

Creating and agreeing the REQUIREMENTS for a project are only part of the story (what the project is going to do – an important part!)

It’s equally important to agree what the BOUNDARIES are of any undertaking and these must show what the project is NOT going to do.

These elements are bound together and are called the Project Scope Statement which details the project objectives, end-products (deliverables), and requirements.

The Scope must be agreed with all concerned, and used to create the project plan ‘baseline’. Once agreed, the scope sets the expectations of all stake holders so they are clear about what they are going to get when the project is finished.

The last thing we want is a disagreement at project hand over about what we have or haven’t done – and what was expected.

Many projects fail – not because Requirements were not met – but because of difference of opinion about what the project was to deliver.

Most projects are triggered by some form of requirements document. These are central to success and lead to the project developing some form of functional specification against which the project outcome is designed. But not enough effort is spent getting a joint agreement on these documents, and that is where a scope planning and scope development play a key part.

“Scope creep” is seen as an industry-wide evil, instead as being viewed as the natural corollary to change control.

There is a little-known technique that beats all others hands-down for laser-focussed scope planning and development.

It’s this. At the very beginning of project planning, agree what the end-product along with the major products are to be.

Procedure

  • Project Objectives – what the project is to do. These should be quantified and measurements agreed. Typically the measurements will include one or more of, cost, time scale, quality, or business benefits.  You will have heard of the SMART acronym for each objective: Specific, Measurable, Accurate, Realistic and tangible, Time bound (time frame plus date).
  • Deliverables (End-Products). Each should have a Product Description written. This contains descriptions of the purpose, composition, derivation, and the quality criteria for it to be acceptable to the customer.
  • Requirements. This is a specific skill, almost certainly done by specialist team, the customer, users, etc. But it is the responsibility of the project manager to make sure they are captured and agreed. Requirements quantify and prioritise the wants, needs and expectations. They may also describe some aspects of functionality of the project deliverables.
  • Project Boundaries. Care must be taken here. This should focus on what is to be excluded from the scope in terms of requirements, objectives, and deliverables. It’s a good idea to create a draft boundary document and circulate it for comments. Or perhaps generate the document from within a meeting with key stake holders.
  • Product Acceptance Criteria. This should document the WHAT and the HOW that will be carried out as part of agreeing successful project closure. It must be the Customer/Users perspective. The actual criteria used can be taken from a wide choice of aspects, and may include elements such as ease of use, reliability, operating costs, performance data, etc.  This should also include HOW the objectives, deliverables and other outcomes of the project are to be approved.
  • Constraints. All projects have constraints – often put there by humans – sometimes by the rules of physics!  A constraint is anything which impedes the project team’s work. The obvious choices may include, time, cost, quality, key milestone dates or logistics, standards, procedures, directives, compliance, legal and law, health and safety, technology, etc.  Whatever. Get them down and agreed – then plan accordingly.
  • Assumptions. In a nutshell, anything you believe to be true. Do not use this section to capture a load of disguised risks (although stated assumptions may lead to generated risks). Documenting them at the start of a project helps test these assumptions and get them agreed.  Should these assumptions prove to be false at a later date, these captured statements can be used as a basis to plan and manage the way forward.
  • Project Organisation. Well, as it is initially – it is likely that changes may be necessary to the roles and responsibilities assigned to individuals.
  • Initial Risks. Any known risks at this time. It is helpful to include an initial risk analysis so that readers can get a ‘feel’ for each risk.
  • Milestones. These may be externally dictated and/or internally created as a result of planning by the project manager. Be sure to have them represent significant points of achievement (or key decision points such as an end-stage assessment).
  • Funding Limitations. This is different to cost constraints. It refers to the availability of money to finance the project, and this may have an impact on cash flow. It may state key dates when funds are available, these may be dictated by certain completion criteria, and it also state the amount of funds released at a given point.
  • End Product Description. This should include the quality criteria for the product to be acceptable for the customer/user. 
  • Specification Document. This is usually derived directly from the Requirements document. It is usually highly detailed and created by the specialist team along with input from the customer and users.

Related documents

  • Closing Sales
  • Product Recall
  • How to use bottlenecks in your business to help you write effective standard operating procedures (SOP)
  • SOP Software to help you manage your standard operating procedures (SOP)
TKO Business Modeller
Pat Williams, is the creator of TKO Business Modeller & TKO Policy Guides software. Pat firmly believes in the benefit of documenting your business systems. In doing so, a business owner can build the system once, then duplicate themselves over and over again simply by inducting new people into the system.

* Please read our disclaimer before downloading any of our documents

← Marketing Manual
Documentation Control Procedure →
  • Document your systems with TKO
  • Related documents

    • Closing Sales
    • Product Recall
    • How to use bottlenecks in your business to help you write effective standard operating procedures (SOP)
    • SOP Software to help you manage your standard operating procedures (SOP)
    TKO Business Modeller
    Pat Williams, is the creator of TKO Business Modeller & TKO Policy Guides software. Pat firmly believes in the benefit of documenting your business systems. In doing so, a business owner can build the system once, then duplicate themselves over and over again simply by inducting new people into the system.
  • Manuals .

    • ►Manuals (14)
      • Business Manuals (14)
  • Document Categories .

    • ►Administration
      • ►Administration Plans and Goals
      • ►Administrative Forms and Templates
      • ►Office Policies and Procedures
      • ►Purchasing
      • ►Records and Data
    • ►Best practices and ideas
    • ►Customer Relationships
      • ►Customer Forms and Templates
      • ►Customer Management
      • ►Customer Relationships Plans and Goals
    • ►Document Conversion
    • ►Environmental
      • ►Environmental Forms and Templates
      • ►Standards and Overview
    • ►Finance
      • ►Accounts Payable
      • ►Accounts Receivable
      • ►Asset Management and Planning
      • ►Financial Forms and Templates
      • ►Financial Management Policies
      • ►Financial Plans and Goals
      • ►Financial Reporting
      • ►Payroll
    • ►Human Resources
      • ►Discipline and Termination
      • ►Dispute Resolution
      • ►Employee Induction Manual
      • ►Employee Safety Manual
      • ►General Human Resources Policies
      • ►Human Resources Forms and Templates
      • ►Human Resources Plans and Goals
      • ►Leave and Separation Policies
      • ►Staff Recruitment
      • ►Staff Training & Performance
    • ►Job Descriptions
      • ►Job Descriptions – General
    • ►Management and Executive
      • ►Business Plan-model
      • ►Company Policies
      • ►Management Review and Continual Improvement
      • ►Risk Management
    • ►Manuals
      • ►Business Manuals
    • ►Manufacturing and Assembly Operations
      • ►Caring For Customer Property
      • ►Correcting and Preventing Defects
      • ►Manufacturing Forms and Templates
      • ►Manufacturing Operations Plans and Goals
      • ►New Products
      • ►Producing Goods Or Services
      • ►Supply Chains
      • ►Warehousing
    • ►Marketing
      • ►Business Development
      • ►Marketing Plans and Goals
      • ►Marketing Resources
      • ►Mockups and Templates
    • ►Property Management
    • ►Quality Iso 9001-2008
      • ►Management Responsibility
      • ►Measurement- Analysis and Improvement
      • ►Product Realization
      • ►Quality Management System
      • ►Quality Manual Overview and Purpose
      • ►Quality System Forms and Templates
      • ►Resource Management
    • ►Real Estate Sales
      • ►Auctions
      • ►Customer Service Program
      • ►Inspections
      • ►Listings
      • ►Market Appraisal
      • ►Property Sales
      • ►Prospecting
      • ►Sales Team Operations
      • ►Settlement
    • ▼Sales
      • ►Performance Reports
      • ►Sales Forms and Templates
      • ►Sales Plans and Goals
      • ▼Sales Process
        • Closing Sales
        • Discussing and Identifying Customer Requirements (agreeing Scope)
        • Product Recall
    • ►SOP Software
    • ►Templates and Forms
      • ►Templates
    • ►TKO Knowledge Base
      • ►Tutorials
    • ►Workplace Health and Safety
      • ►Health and Safety Forms and Templates
      • ►Health and Safety Plans and Goals
      • ►Implementation
      • ►Introduction
      • ►Management Review
      • ►Measurement and Evaluation
      • ►Planning
    Copyright © 2019 Cornstalk Software Pty Ltd . All Rights Reserved

    Signup For Trial

    Processing...