Project Plans A Project Plan shows what a project must accomplish and how the team will go about doing so. It is a tool for thinking through the project's needs, documenting decisions, and communicating commitments and expectations. It can be one large document or multiple individual ones that together form "the plan."   Typical elements include: Project Summary: Objectives and Scope Project Organization: The Team Management: How the project will be planned and tracked Work plan: WBS, schedule, milestones, budget Resource plan: Staffing, facilities, equipment,experts Processes: Communication, issue management, decisions...

Get Premium access to our complete resource library for just $149/year or $14.95/month. 15-day free trial. No commitments? No problem! Try our new Project Planning and Tracking Bundle 11 of our most popular templates in a one-time purchase downloadable kit. No muss, no fuss, no subscription required. Find out more »

• Software Project Plan -
  Detailed guide for creating a software development plan. Includes making tradeoffs on scope, resources, schedule and other issues with a quality-focus.
• Development Project Plan -
  Cross-functional project plan outline that summarizes project goals and major project activities. Gets into some detail to remind you about all the little "gotchas" that we can forget about when we're busy on a project.
• Small Project Plan File -
  Example of a simple project plan document for a small project. You don't need a 30-page plan, but you still need to agree on goals, control the scope, do the right reviews, get cross-functional buy-in, and get the update done fast while getting on with other efforts.

• Project Definition - Statement of Work
  One approach to documenting high-level project objectives and key parameters in a concise document. Helps make sure the team and all stakeholders understand agree upon the reasons for doing the project, what the project will produce, and various important constraints and assumptions. Such a document should be done before detailed requirements specs are written.
• Project Scope Definition: Vision Document
  A 1-2 page document (from the Quality Rapid Product Development (QRPD) methodology), created by a team in the early days of a project. The project vision builds the case for doing a project, negotiates the overall scope and requirements at the highest customer-focused level, and obtains team alignment and captures agreement on the project definition.
• Project Charter
  Once your project idea has been evaluated and approved for further investigation, you need to communicate the major parameters and high-level information. This template for a succinct project charter helps you summarize that critical information.

• WBS and MS Project Schedule for Electromechanical Systems Project -
  A Work Breakdown Structure for a multi-subsystem development project. More detail than that home improvement project, less detail than building the Hoover Dam. Covers all phases and cross-functional departments.
• Software Release Lifecycle WBS in MS Project
  Breakdown Structure in Microsoft Project that covers 10 phases of a Software Release Lifecycle aimed at large multi-project software releases. SRLC. It shows when each deliverable gets accomplished in each phase and includes typical task dependencies and primary resource assignments for each deliverable.
• MS Project WBS/Gantt Template - IT Software Development Project -
  Very detailed, annotated cross-functional work breakdown structure for development of IT applications. Created by a PMO at a large company.
• Software Bug Fix WBS
  Work breakdown structure for a project to fix 'bugs' or defects in an existing product or system. Efficient but critical - helps avoid duplicated effort and conflicting changes, and takes into account little things like side effects and documentation.
• Department- and Project-Level WBS Example
  Very high level work breakdown structure, in Microsoft Project format, for tracking department-level project. One stop shopping approach to tracking various group time lines and department level phase gates (and their assumed deliverables and milestones).
• WBS and Microsoft Project Gantt - 802.11 Master Development Schedule
  Here's a wireless, networking 802.11b schedule for concurrent development of an access point and PC card with shared, common resources. This WBS is an example of a large, complex, cross-functional project.
• WBS and Microsoft Project Gantt - USB Development Schedule
  This example of an early version of the WBS precedes the first schedule baseline. It was a derivative project from the 802.11 Master Development Schedule. Good example of early planning levels.

• Product and Project Risk Assessment and Mitigation Tables -
  This file contains an overview explanation of risk management, and several examples of Risk Assessment Tables to be used during the early project selection process and during detailed investigation and planning work. The goal is to ensure that technical and non-technical risks are factored into decisions about launching a project and into full project planning to make sure the risks will be handled.
• Project Budgets and Cost Tracking
  Formats for documenting the costs to be incurred during a project. Draft budgets are created as the team investigates alternatives and makes project scope decisions. The final budgets document and communicate the team's estimates for costs to be incurred to develop the requested features/ requirements etc.
• Communications Plan -
  A brief plan created by the project team, documenting how they will communicate important information - includes meetings, status reports, etc. The plan covers internal team communications and external stakeholder communications.

©Copyright 2000-2012 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy