[Navigation Bar]  
 
 

    

[OpenSUSE powered]
[BUSH powered]
[vi powered]
[XML] [RSS]

 An outline for submitting a Linux project proposal for a contract.

Outline for Writing a Linux Proposal

Here is a general layout for a project proposal. Your proposal may not need all this information. Use this when the client doesn't provide a solution but asks you to supply a solution instead. For a project of 6 months to a year, it can take 2 months to research the project and creating a hundred page project specification, and then another 2 weeks to prepare a 10 to 12 page the formal proposal.

Layout

  • Use basic fonts at easy to read sizes (e.g. Arial 11)
  • Use single-spaced text with wide outer margins for comments
  • Have somebody else proof read for spelling and grammar
  • Include a Table of Contents
  • All pages should numbered

Cover Page

  • The Project Title
  • Whom the Project is Prepared For
  • The Date Prepared
  • The Team Leader
  • The Team Members
  • Contact Information

Executive Summary

  • Background on the Problem
  • What the Project Does (in layman's terms)
  • How does it Solve the Problem

Constraints and Requirements

  • The hardware/server required
  • The operating system to be used
  • The programming languages to be used
  • The web requirements (for a web project)
  • The minimum throughput requirements
  • The hardware that will be interfacing with
  • The software that will be interfacing with
  • Migration/Porting Issues
  • The deadline/target date

Phase 1: Review of the Problem

  • Summary of existing problems
  • Research into Tools to help correct the problem

Phase 2: Research into the Solution

  • Techniques to Solve the Problems
  • What You Chose to Use and Why You are Using Them

Phase 3: Project Development Outline

  • List of Components of Project
  • Describe Briefly What the Components Do
  • Describe Briefly What the Components Are Responsible For

Phase 4: Project Maintenance Outline

  • Rollout Requirement Details
  • Migration Requirement Details
  • On-going Maintenance Plans

Pragmatics and Contract Terms

  • Background History and Clients
  • Payment Method (Time/Materials, Fixed Cost, etc.)
  • List of Payment Milestones
  • Time, Quality or Cost Optimization
  • Intellectual Property Terms
  • Deliverables
  • Risks
  • Contact People and Responsibilities
  • Your Contact Times and Call Return Times
  • Guarantees and Limitations
  • Non-Compete and Non-Disclosure Terms
  • Charges for Extra Work
 

Read More:  What do I Charge? --> 

 
     

« Truth Humility Communication Nobility Freedom Purity Excellence Right Support Courage Compassion Quality Honesty Trust Cooperation Challenge Education »
PegaSoft Canada - A Linux Association Since 1994