jump to navigation

Proposal A September 7, 2005

Posted by Coolguy in Project Management.
Tags:
trackback

1 Executive Summary

1.1 Program Approach and Scope

  • Initial Envisioning Phase followed by three iterative phases
  • Envisioning Phase will mitigate risk and will allow for greater accuracy in time and budget forecasting
  • If requirements are clearly defined and are unlikely to change as the project progresses, client may wish to sign off on the design for the entire solution before build commences; in this case, one would proceed without iterative development and implement the solution using a single development phase.
  • Using a single Solution Planning and Development phase should reduce the project timescales
  • The Envisioning Phase will involve a team of consulting company’s consultants and contributions from parents company employees.
  • The deliverables of the Envisioning Phase are a clear design and plan for the completion of the solution.
  • Resources to be used for iterative phases
  • Timescales for deployment.

1.2 Schedule

  • Initial Envisioning Phase which will last for (1-6) weeks.
  • Estimated dates for completion

1.3 Pricing

  • Envisioning Phase ~ Fixed price
  • Time and Materials basis the estimate for the completion of the project
  • After Envisioning Phase we will be better able to estimate the
    complete price and time lines.

2 Company information

2.1 Background

  • Registered address and detailes
  • Inception date and articles of incorporation

2.2 Financial Stability

3 Organisation

3.1 Company profile

  • Expertise: Training and certifications program
  • Assets: Architectures and frameworks
  • Experience: Customer engagements

3.2 Company locations

3.3 Management Structure

3.4 Knowledge Maintenance

4 References

5 Proposal Overview

5.1 Background

5.2 Scope

5.3 Objectives

  • Increased efficiency of current processes.
  • Improved customer service.
  • Reduced training time for operator through the use of a common system.
  • Increased ability to drive ‘add-on’ sales.
  • A lower Total Cost Of Ownership (TCO) over the ageing technologies and
    complex systems.
  • Future proofing.
  • System resilience.

6 Solution

  • Infrastructure
  • Technical Architecture

6.1 Architecture Goals

  • Satisfy the functional requirements
  • Satisfy the non-functional requirements
  • Smooth integration with pre-existing applications and infrastructure, if any
  • Reuse of pre-existing systems and processes, if any
  • Leverage best practices in solution and operating architecture
  • Ease of migration from existing processes if any, to the new solution.
  • Ease of maintenance
  • To provide a good foundation for future
  • To maximise the use of existing technology

6.2 Architecture Overview

  • Modules and brief description

6.3 Enabling Architecture

  • Technology to be used for auditing, logging, authentication, security

6.4 Infrastructure Architecture

6.4.1 High Level Architecture

  • Directory services. Active directories
  • Business logic: Microsoft BizTalk Server
  • Workflow: Microsoft SharePoint Portal
  • Database:
  • Operations Management: MOM

6.4.2 Server Architecture

6.4.3 Infrastructure Components

6.4.4 Capacity

6.4.5 Authentication

6.4.6 Systems Management

  • Operations Management

6.4.7 Resiliency

6.4.8 Disaster Recovery

6.4.9 Driving down TCO

  • TCO consists of all Direct Costs (budgeted) and Indirect Costs (unbudgeted costs) over the lifespan of the IT System.
  • Direct Costs
    o Hardware/Software
    o IT Operations
    o Administration
  • Indirect Costs
    o User Operations
    o Downtime

6.4.10 Direct Costs

  • Hardware/Software
  • IT Operations
  • Administration

6.4.11 InDirect Costs

  • User Operations
  • Downtime
  • Future Proofing

7 Project Delivery Approach

7.1 Envisioning

7.1.1 Objectives

  • To produce a project plan
  • High level design

7.1.2 Deliverables

  • High Level Requirements Document
  • Project Initiation Document comprising:
    o Scope Document – Definition of the scope and deliverables for the
    implementation phases of the project.
    o Risk Mitigation Plan – Identification of the risks to the
    implementation phases of the project, and suggested mitigation
    strategies.
    o Project Plan – A Project plan for the implementation phases of
    the project to deliver the scope stated in the Scope Document.
    o Project Quality Plan – A description of the quality measures
    to be taken to ensure the successful delivery of the project
    scope.

7.2 Development Phases

7.2.1 Development Iteration(s)

7.2.1.1 Objectives

7.2.1.2 Deliverables

7.2.4 Stabilisation Phase

8 Deployment

8.1 Development and Staging

8.2 Live

9 Estimated Costs

9.1 Costs

9.2 Licenses

10 Schedules & Timeframes

11 Solution Delivery Methodology

12 Project Governance

12.1 Project Organisation

12.2 Role Descriptions

12.3 Scope management

12.4 Change Management Process

12.5 Testing

12.6 Quality assurance

12.7 Progress tracking & reporting

12.8 Risk Management and Exception Reporting

12.9 Skills transfer

Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: