IT Bites > Services >
Project Scoping
IT Bites Ltd can help you to accurately define your project.
Our typical approach sees us partner with our clients to produce an accurate
definition of where the project wants to be at conclusion, and the roadmap that
will get the project team there.
Based on PMI & Prince 2 methodologies, a Project Initiation Document (PID) is
created with the following modules:
(please click on a module to expand details of the content)
 | Project Overview - based on Project Briefs and/or Feasibility studies,
this module aims to define:
 | Purpose and background to the project |
| High Level Objectives |
| Approach to be taken |
| Scope of the project |
| Outline deliverables |
| Project Exclusions |
| Constraints |
| Interfaces to other systems/organisations/projects etc |
| Assumptions |
| Inituial Business case - reasons, benefits, costs, measures of success
etc |
| High level project controls |
| Tolerances |
|
| Product Definitions - this module aims to fully define each deliverable
identified in the project:
| Purpose - what is the deliverable that is being created |
| Composition - the elements that will be produced e.g. a report; a
software application etc |
| Derivation - the sources that are used to create the product |
| Format - styles etc |
| Owner - the strategic decision-maker associated with the product |
| Product Leader - the project team member who has taken responsibility
for the products delivery |
| Control - planning dates for earliest and latest starts and finishes |
| Dependency - any other deliverables on which this one is dependent |
| Parent To - any other deliverables which depend on this one |
| Quality Criteria - a checklist of how we know when the product has been
fully created and its delivery be accepted and signed off |
| Quality Checks - how governance is applied to ensure quality is adequate |
| Management - approval, sign-off and change control |
|
| Organisation Structure - this module aims to define a project structure
which stands best chance of success. It is IT Bites belief that the best
project teams reflect the need for the Business, its Users and Suppliers to
have their interests recognised and to provide forums where these can be
discussed:
| Projects place in any wider programme |
| Governance as defined by a strategic management group - a Project Board
or Steering Group |
| Operational team in the form of a project team responsible for
day-to-day delivery |
| Consideration of Project assurance functions and organisation |
| User support groups who may assist the project team in providing
experience; design input etc |
| Specific project roles along with descriptions of responsibilities etc |
|
| Quality Plan - this module will define how quality will be checked through
the project, which may include plugging into any standards adopted by the
business:
| Responsibilities are defined |
| Standards are set |
| Establishing Project Management controls |
| Defining product controls |
| Documenting review types - quality; peer; test plan. |
| Applying quality to change and configuration management |
|
| Communication Plan - this module identifies interested parties and the
mechanisms by which the interact, and the events that may instigate the
interaction:
| Communities - the groups involved in the project |
| Relationships between the communities |
| Information List - when and how information is to be provided |
| Communication templates e.g. standard project forms to be used such as
project issues; change requests etc |
|
| Project Plan - module not only aims to create an initial project plan e.g.
Gantt, but also the standards used in planning:
| Principles and techniques - estimating, monitoring etc |
| Tools |
| Levels of plan e.g. stages, project, product |
| High level overviews - supported by Work Breakdown Structures; Product
Flow Diagrams etc as necessary |
|
