|
|
Project Management
ocak 1/6/2008 | 8 (1) | 1006 | 178 | 1 | English
LESSONS LEARNED CHECKLIST TEMPLATE
Project Name: Prepared by: Document Revision/Release Status Revision Date Description of Changes Author / Editor 0.0.1 MM/DD/YYYY Initial draft
Modify the text of this document to fit your project.
1. Project Lessons-Learned Checklist No. Lesson Learned Yes No N/A Impact ... more>>
ocak 1/28/2008 | 0 (0) | 532 | 178 | 0 | English
Software Requirement Specifications Document
DOCUMENT CHANGE HISTORY
Version Number Date Contributor Description Vx.x
** Note to Document Author - Red and blue text in this document is directed at the template user to list process, build standards and help build the document. The text should be removed before submitting an ... more>>
ocak 1/28/2008 | 0 (0) | 1272 | 177 | 0 | English
Milestones and Deliverables - Current [List the milestone and deliverable events/activities/tasks for the current month or report period, due dates and status. Explain reasons for variance and planned corrective actions] Milestones and Deliverables - Upcoming [List the milestone and deliverable events/activities/tasks for the upcoming month or ... more>>
ocak 1/6/2008 | 0 (0) | 729 | 175 | 0 | English
Sheet3
Sheet2
Sheet1
Stage 1: Technical specifications
Stage 2: The development
Search engine software and interface
Online forms (eg membership application forms)
Stage 3: Delivery and deployment
Web server and hosting costs
Scoping the project (ie finalising scope, functions, deliverables and costs)
Graphic design (eg look and feel, ... more>>
ocak 1/10/2008 | 0 (0) | 1113 | 168 | 0 | English
Risk & Change
(7) Admin costs not in overhead
(6) On-Going Support
(5) Network HW-SW
(4) Software
(3) Hardware
(2) Effort
(1) Estimate summary
Project Assumptions
Pre-estimate checklist
Estimating template guidelines
Replace this page with your project risk chart
The following is provided as a basic template that may be used in the ... more>>
ocak 1/28/2008 | 6 (2) | 1480 | 161 | 1 | English
[Insert Project Name]
Test Strategy
Executive Sponsor - [Insert Name]
Business Owner - [Insert Name]
Project Manager - [Insert Name]
Original Plan Date: [Insert Date, Spelled Out]
Revision Date: [Insert Date, Spelled Out]
Revision History
Revision Number Date Comment 1.0 August 14, 2007 Original DoIT PMO Document ... more>>
ocak 1/10/2008 | 0 (0) | 564 | 158 | 0 | English
Your organization logo here
Your organization name here Table of Contents
INTRODUCTION 3
Overview 3
Purpose 3
Organization 3
STAGE I - PROJECT INITIATION 3
Critical Success Factors 4
Activities 5
1. Assign A Project Champion/Leader 5
1. Identify A Sponsor 5
1. Define the Business Need/Opportunity 6
1. Identify ... more>>
ocak 1/10/2008 | 6 (1) | 1392 | 158 | 0 | English
Instructions
for
PROJECT SCOPE STATEMENT
This document is a supplement to the Project Scope Statement.
Note that all documents that are linked to the Scope Statement become part of the Project Scope and require the same degree of management control. Such documents should be maintained in a separate Scope directory along with the Scope Stat ... more>>
ocak 1/6/2008 | 8.5 (2) | 648 | 158 | 0 | English
Change Management Plan
Insert State Route, Project Name
Insert Project MP limits
Project Manager: Insert name here
Date
Change may be encountered during the life of the _______________________ project. The project scope, schedule, budget, and resources will all be areas of potential change. The sources of these changes will be internal ch ... more>>
ocak 1/28/2008 | 0 (0) | 518 | 157 | 0 | English
Project name
Business Requirements Specification
(Detailed BRS)
Document control sheet
Contact for enquiries and proposed changes
If you have any questions regarding this document or if you have a suggestion for improvements, please contact:
Project Manager Insert Project Managers Name Here
Phone Insert Phone Number Here
Version his ... more>>
ocak 1/28/2008 | 0 (0) | 451 | 157 | 0 | English
State of Minnesota
Issue Management Process Flow (Example)
02/23/2006 Page 1 of 1
Issue Management process flow V2.0 5/25/2005 ... more>>
ocak 1/28/2008 | 5 (1) | 762 | 156 | 0 | English
CS3911
Software Requirements Specification (SRS) Template
Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project.
The document in this file is an annotated outline for specifying software requiremen ... more>>
ocak 1/10/2008 | 5 (2) | 966 | 155 | 1 | English
PROJECT SCOPE STATEMENT
Note: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project.
Create links to referenced documents (e.g., Link_To_. ) by using Insert ( Hyperlink on your toolbar.
Note that all documents that are linked to the Scope Statement become part of the Project Scope and req ... more>>
user002 2/5/2008 | 0 (0) | 471 | 154 | 0 | English
Date of Report Jun 30, 2005 Name Start Date 10/1/04 3/28/06 Item No Actual Start Date Tentative Start Date Impact on Completion (Actual vs. Target) Deliverables Lead 12/1/04 4/30/05 1.1 11/15/04 3/31/05 1.2 Prepare for Strategic Planning Off-site 2/1/05 4/15/05 1.3 3/22/05 1) Kick off meeting of technical group 1.4 After Phase 3 1.5 After Phase 3 1 ... more>>
ocak 1/28/2008 | 1 (1) | 1306 | 153 | 0 | English
R T M
Version Control
Requirement Identifier
Test Cases
1.1.1
1.1.2
1.1.3
XX_UC_001
XX_UC_002
XX_UC_003
x
Project Name - Institution Name
Requirements Traceability Matrix
DOCUMENT CHANGE HISTORY
Version Number
Date
Contributor
Description
RELATED DOCUMENTS
Document Name
Location
Software Requirements Specification Document
Use ... more>>
| | | |
| results / page 15/25/50 |
Page: 4 of 54
|
4...
|
|