Project Team Proposal

1
Project Team Proposal

• Overview
• of the PTP Deliverable

2
Components of the PTP

• Cover Letter
• Client Profile
• Problems/Opportunities Identified
• Scope
• Project Feasibility

3
What is success?

• On time
• On budget
• On target

4
Scope Creep

• How do you avoid scope creep (MIS 160)?
• Know where you fit in as a consultant
• Write a good scope statement
• How do you manage scope creep (MIS 161)?
• Project management
• Knowledge management
• Change management

5
Know where you fit in

• Stage 1 Application Mapping you inform the
  owner whats possible
• Stage 2 Defining business needs owner decides
  what the firm needs
• Stage 3 IS planning end user and you sit down
  and decide on a portfolio of applications
• Stage 4 Seek value added business led (owners
  and end-users prioritize)
• Stage 5 Link it the proposal to the business
  strategy

6
Scope Statement

• Zoom in
• What type of system is it?
• Describe the context of the system
• List the outputs of the system
• Describe the functions of the system
• The functions that it will have
• The functions that it will not have
• Zoom out
• Identify all the stakeholders and their interests
• Toyota Processing System (TPS) Five Whys

7
What type of system is it?

• Operational (Transactions)
• Tactical (Control)
• Strategic (Planning)

8
Sample Operational Systems

• Order entry
• Processing
• Tracking shipping documents
• Vehicle scheduling/loading
• Sales and purchase ledgers

• Cost accounting
• Stock control Shop-floor scheduling
• Bill of materials
• Purchase orders
• Receiving
• Employee records
• Payroll

9
Sample Tactical Systems

• Sales analysis budgetary control
• Management accounting
• Inventory management
• Quality analysis

• Expense reporting
• Market research/statistics
• WIP control
• Requirements planning
• Supplier analysis

10
Sample Strategic Systems

• Sales forecasting
• Operating plans capacity planning
• Profit/earnings forecasts
• Business mix analysis
• Manpower planning
• Financial modelling

11
Describe the context of the system

• If the system is an operational systems, it will
  be processing transactions
• The idea therefore is to list the source of all
  inputs, including volumes and rates
• And to list all the targets that will be
  accepting the outputs of the system
• This collection forms the so-called Context
  Diagram

12
List the outputs of the system

• If the system is an operational system, get
  actual volumes (number of transactions) and rates
  (number of transactions of per hour)
• Prioritize the transactions by volume or rates

13
Functions

• To carry out a transaction you will need to do
  several functions
• There may be several ways to carry out the
  transaction
• The idea therefore is to actually list all the
  transactions need, including volume and rate data
• Moreover, list all the functions you will not be
  developing

14
Zoom back and take a good look

• Identify all the stakeholders and their interests
• End users
• Customers
• Suppliers
• The owners
• Agencies
• Etc.

• TPS Five Whys
• How goes down the ladder
• Why goes up
• Explore each level before going further, up or
  down (What)
• Five Whys and Five Hows will help you find
  all the stakeholders and their interests

15
Scope Statement

• The type of system
• The context of the system
• The outputs of the system
• The functions of the system
• The functions that it will have
• The functions that it will not have
• All the stakeholders and their interests