IT Bites - Project Scoping

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:

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
Initial 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:

Content to follow

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:

Content to follow

Communication Plan - this module identifies interested parties and the mechanisms by which the interact, and the events that may instigate the interaction:

Content to follow

Project Plan - module not only aims to create an initial project plan e.g. Gantt, but also the standards used in planning:

Content to follow

IT Bites Ltd
26 - 28 Church St
Saffron Walden
Essex CB10 1JQ
Email admin@it-bites.com for more information

	Home > Services > Scoping
<b>Search</b> <b>Profile</b> Steve Nikki <b>Services</b> PeopleSoft Project Management Project Scoping Functional Training <b>Products</b> Global Payroll <b>Projects</b> UK Mutual Dutch Bank Scottish Bank Global Risk Co. Others <b>Stuff</b> Privacy Policy Contact Us Useful Links Client List Fun	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: 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 Initial 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: Content to follow 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: Content to follow Communication Plan - this module identifies interested parties and the mechanisms by which the interact, and the events that may instigate the interaction: Content to follow Project Plan - module not only aims to create an initial project plan e.g. Gantt, but also the standards used in planning: Content to follow

				Click the section heading to collapse or expand
		IT Bites Ltd 26 - 28 Church St Saffron Walden Essex CB10 1JQ Email admin@it-bites.com for more information	© Copyright IT Bites Ltd. v2.0 2011