Green computing project i have added the files needed
team_contract.docx
Team Contract
Project Name:
Project Team Members Names and Sign-off:
|
Name |
Sign-off on Team Contract |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Code of Conduct: As a project team, we will:
·
·
·
Participation: We will:
·
·
·
Communication: We will:
·
·
·
Problem Solving: We will:
·
·
·
Meeting Guidelines: We will:
·
·
·
top_10.xlsx
Sheet1
| Top 10 Risk Item Tracking for Project Name | ||||
| Prepared by: | Date: | |||
| Risk Event | This Month | Last Month | Number of Months in Top 10 | Risk Resolution Progress |
Sheet2
Sheet3
wbs.docx
Work Breakdown Structure Template for Project Name
Prepared by: Date:
1.0 Main category 1
1.1 Subcategory
1.2 Subcategory
1.2.1 Sub-subcategory
1.2.2 Sub-subcategory
1.3 Subcategory
1.4 Subcategory
2.0 Main category 2
2.1 Subcategory
2.2 Subcategory
2.2.1 Sub-subcategory
2.2.2 Sub-subcategory
2.3 Subcategory
2.4 Subcategory
3.0 Main category 3
3.1 Subcategory
3.2 Subcategory
3.2.1 Sub-subcategory
3.2.2 Sub-subcategory
3.3 Subcategory
3.4 Subcategory
4.0 Main category 4
4.1 Subcategory
4.2 Subcategory
4.2.1 Sub-subcategory
4.2.2 Sub-subcategory
4.3 Subcategory
4.4 Subcategory
wtd_decision_matrix.xlsx
Sheet1
| Weighted Decision Matrix for Project Name | |||||
| Created by: | Date: | ||||
| Criteria | Weight | Project 1 | Project 2 | Project 3 | Project 4 |
| A | 25% | 90 | 90 | 50 | 20 |
| B | 15% | 70 | 90 | 50 | 20 |
| C | 15% | 50 | 90 | 50 | 20 |
| D | 10% | 25 | 90 | 50 | 70 |
| E | 5% | 20 | 20 | 50 | 90 |
| F | 20% | 50 | 70 | 50 | 50 |
| G | 10% | 20 | 50 | 50 | 90 |
| Weighted Project Scores | 100% | 56 | 78.5 | 50 | 41.5 |
Weighted Score by Project
Project 1 Project 2 Project 3 Project 4 56 78.5 50 41.5
Sheet2
Sheet3
breakeven.xlsx
Profit Analysis
| Units Sold | Revenue | Expense | ||||||
| 0 | $0 | $25,000 | ||||||
| 500 | 6,000 | 29,000 | ||||||
| 1,000 | 12,000 | 33,000 | ||||||
| 1,500 | 18,000 | 37,000 | ||||||
| 2,000 | 24,000 | 41,000 | ||||||
| 2,500 | 30,000 | 45,000 | ||||||
| 3,000 | 36,000 | 49,000 | ||||||
| 3,500 | 42,000 | 53,000 | ||||||
| 4,000 | 48,000 | 57,000 | ||||||
| 4,500 | 54,000 | 61,000 | ||||||
| 5,000 | 60,000 | 65,000 | ||||||
| 5,500 | 66,000 | 69,000 | ||||||
| Sales Price per Unit: | $12 | 6,000 | 72,000 | 73,000 | ||||
| 6,500 | 78,000 | 77,000 | ||||||
| 7,000 | 84,000 | 81,000 | ||||||
| Manufacturing Cost per Unit: | $8 | 7,500 | 90,000 | 85,000 | ||||
| 8,000 | 96,000 | 89,000 | ||||||
| 8,500 | 102,000 | 93,000 | ||||||
| Fixed Monthly Expense: | $25,000 | 9,000 | 108,000 | 97,000 | ||||
| 9,500 | 114,000 | 101,000 | ||||||
| 10,000 | 120,000 | 105,000 | ||||||
| Break-Even Point (Units Sold): | 6,250 | 10,500 | 126,000 | 109,000 | ||||
| Revenue at Break-Even Point: | $75,000 | 11,000 | 132,000 | 113,000 | ||||
| 11,500 | 138,000 | 117,000 | ||||||
| 12,000 | 144,000 | 121,000 | ||||||
| 12,500 | 150,000 | 125,000 | ||||||
| 13,000 | 156,000 | 129,000 | ||||||
| 13,500 | 162,000 | 133,000 | ||||||
| 14,000 | 168,000 | 137,000 | ||||||
| 14,500 | 174,000 | 141,000 | ||||||
| 15,000 | 180,000 | 145,000 | ||||||
| 15,500 | 186,000 | 149,000 | ||||||
| 16,000 | 192,000 | 153,000 | ||||||
| 16,500 | 198,000 | 157,000 | ||||||
| 17,000 | 204,000 | 161,000 | ||||||
| 17,500 | 210,000 | 165,000 | ||||||
| 18,000 | 216,000 | 169,000 | ||||||
| 18,500 | 222,000 | 173,000 | ||||||
| 19,000 | 228,000 | 177,000 | ||||||
| 19,500 | 234,000 | 181,000 | ||||||
| 20,000 | 240,000 | 185,000 |
Profit Analysis
Revenue 0 500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000 9500 10000 10500 11000 11500 12000 12500 13000 13500 14000 14500 15000 15500 16000 16500 17000 17500 18000 18500 19000 19500 20000 0 6000 12000 18000 24000 30000 36000 42000 48000 54000 60000 66000 72000 78000 84000 90000 96000 102000 108000 114000 120000 126000 132000 138000 144000 150000 156000 162000 168000 174000 180000 186000 192000 198000 204000 210000 216000 222000 228000 234000 240000 Expense 0 500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000 9500 10000 10500 11000 11500 12000 12500 13000 13500 14000 14500 15000 15500 16000 16500 17000 17500 18000 18500 19000 19500 20000 25000 29000 33000 37000 41000 45000 49000 53000 57000 61000 65000 69000 73000 77000 81000 85000 89000 93000 97000 101000 105000 109000 113000 117000 121000 125000 129000 133000 137000 141000 145000 149000 153000 157000 161000 165000 169000 173000 177000 181000 185000 Break-Even6250 75000
Units Sold
burndownchart.xlsx
Sheet1
| Days | Tasks Done | Remaining | Ideal Done Per Day | Ideal Velocity | |
| Initial Value | 0 | 0 | 200 | 10 | 200 |
| 1 | 0 | 200 | 10 | 190 | |
| 2 | 5 | 195 | 10 | 180 | |
| 3 | 3 | 192 | 10 | 170 | |
| 4 | 12 | 180 | 10 | 160 | |
| 5 | 17 | 163 | 10 | 150 | |
| 6 | 9 | 154 | 10 | 140 | |
| 7 | 8 | 146 | 10 | 130 | |
| 8 | 13 | 133 | 10 | 120 | |
| 9 | 15 | 118 | 10 | 110 | |
| 10 | 6 | 112 | 10 | 100 | |
| 11 | 18 | 94 | 10 | 90 | |
| 12 | 15 | 79 | 10 | 80 | |
| 13 | 16 | 63 | 10 | 70 | |
| 14 | 11 | 52 | 10 | 60 | |
| 15 | 8 | 44 | 10 | 50 | |
| 16 | 13 | 31 | 10 | 40 | |
| 17 | 9 | 22 | 10 | 30 | |
| 18 | 6 | 16 | 10 | 20 | |
| 19 | 10 | 6 | 10 | 10 | |
| 20 | 6 | 0 | 10 | 0 |
Sprint 1 Burndown Chart
Remaining Initial Value 200 200 195 192 180 163 154 146 133 118 112 94 79 63 52 44 31 22 16 6 0 Ideal Velocity Initial Value 200 190 180 170 160 150 140 130 120 110 100 90 80 70 60 50 40 30 20 10 0Sheet2
Sheet3
business_case.docx
Business Case for Project Name
Date
Prepared by:
|
1.0 Introduction/ Background
|
|
2.0 Business Objective
|
|
3.0 Current Situation and Problem/Opportunity Statement
|
|
4.0 Critical Assumption and Constraints
. |
|
5.0 Analysis of Option and Recommendation
|
|
6.0 Preliminary Project Requirements
|
|
7.0 Budget Estimate and Financial Analysis
|
|
8.0 Schedule Estimate
|
|
9.0 Potential Risks
|
|
10.0 Exhibits Exhibit A: Financial Analysis
|
business_case_financials.xlsx
Sheet1
| Financial Analysis for Project Name | ||||||
| Created by: | Date: | |||||
| Note: Change the inputs, shown in green below (i.e. interest rate, number of years, costs, and benefits). Be sure to double-check the formulas based on the inputs. | ||||||
| Discount rate | 8.00% | |||||
| Assume the project is completed in Year 0 | Year | |||||
| 0 | 1 | 2 | 3 | Total | ||
| Costs | 140,000 | 40,000 | 40,000 | 40,000 | ||
| Discount factor | 1.00 | 0.93 | 0.86 | 0.79 | ||
| Discounted costs | 140,000 | 37,200 | 34,400 | 31,600 | 243,200 | |
| Benefits | 0 | 200,000 | 200,000 | 200,000 | ||
| Discount factor | 1.00 | 0.93 | 0.86 | 0.79 | ||
| Discounted benefits | 0 | 186,000 | 172,000 | 158,000 | 516,000 | |
| Discounted benefits - costs | (140,000) | 148,800 | 137,600 | 126,400 | 272,800 | NPV |
| Cumulative benefits - costs | (140,000) | 8,800 | 146,400 | 272,800 | ||
| ROI | 112% | |||||
| Payback in Year 1 | ||||||
| Assumptions | ||||||
| Enter assumptions here |
Sheet2
Sheet3
change_request.docx
Change Request Form
Project Name:
Date Request Submitted:
Title of Change Request
Change Order Number:
Submitted by: (name and contact information)
Change Category: Scope Schedule Cost Technology Other
Description of change requested:
Events that made this change necessary or desirable:
Justification for the change/why it is needed/desired to continue/complete the project:
Impact of the proposed change on:
Scope:
Schedule:
Cost:
Staffing:
Risk:
Other:
Suggested implementation if the change request is approved:
Required approvals:
|
Name/Title |
Date |
Approve/Reject |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
charter.docx
Project Charter
Project Title:
Project Start Date: Projected Finish Date:
Budget Information:
Project Manager: Name, phone, e-mail
Project Objectives:
Main Project Success Criteria:
Approach:
Roles and Responsibilities
|
Role |
Name |
Organization/ Position |
Contact Information |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Sign-off: (Signatures of all above stakeholders. Can sign by their names in table above.)
Comments: (Handwritten or typed comments from above stakeholders, if applicable)
client_acceptance.docx
Client Acceptance/Project Completion Form
Project Name: ________________________________________________
Project Manager: ________________________________________________
I (We), the undersigned, acknowledge and accept delivery of the work completed for this project on behalf of our organization. My (Our) signature(s) attest to my (our) agreement that this project has been completed. No further work should be done on this project.
|
Name |
Title |
Signature |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. Was this project completed to your satisfaction? Yes No
2. Please provide the main reasons for your satisfaction or dissatisfaction with this project.
3. Please provide suggestions on how our organization could improve its project delivery capability in the future.
Thank you for your inputs.
comm_plan.docx
Communications Management Plan
Prepared by: Date:
1. Introduction
2. Collection and filing structure for gathering and storing project information
3. Distribution structure (what information goes to whom, when, and how)
4. Format, content, and level of detail of key project information
5. Production schedule and resources for producing key project information
6. Technologies, access methods, and frequency of communications
7. Method for updating the communications management plan
8. Escalation procedures
9. Stakeholder communications analysis
|
Stakeholders |
Document Name |
Document Format |
Contact Person |
Due Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Comments:
|
10. Glossary of terms
cost_estimate.xlsx
Sheet1
| XXX Project Cost Estimate | |||||
| Prepared by: | Date: | ||||
| Note: Change the WBS items and other entries to meet your project needs. This data is from Figure 7-1 of Schwalbe's text | |||||
| Information Technology Project Management, Fourth Edition. Also make sure the formulas work properly based on the data you enter. | |||||
| # Units/Hrs. | Cost/Unit/Hr. | Subtotals | WBS Level 1 Totals | % of Total | |
| WBS Items | |||||
| 1. Project Management | $306,300 | 20% | |||
| 1.1 Project manager | 960 | $100 | $96,000 | ||
| 1.2 Project team members | 1920 | $75 | $144,000 | ||
| Contractors (10% of software development and testing) | $66,300 | ||||
| 2. Hardware | $76,000 | 5% | |||
| 2.1 Handheld devices | 100 | $600 | $60,000 | ||
| 2.2 Servers | 4 | $4,000 | $16,000 | ||
| 3. Software | $614,000 | 40% | |||
| 3.1 Licensed software | 100 | $200 | $20,000 | ||
| 3.2 Software development* | $594,000 | ||||
| 4. Testing (10% of total hardware and software costs) | $69,000 | $69,000 | 5% | ||
| 5. Training and Support | $202,400 | 13% | |||
| 5.1 Trainee cost | 100 | $500 | $50,000 | ||
| 5.2 Travel cost | 12 | $700 | $8,400 | ||
| 5.3 Project team members | 1920 | $75 | $144,000 | ||
| 6. Reserves (20% of total estimate) | $253,540 | $253,540 | 17% | ||
| Total project cost estimate | $1,521,240 | ||||
| * See software development estimate | |||||
Sheet2
| * Software development | |||
| Contractor labor estimate | 3000 | $150 | $450,000 |
| Project team member estimate | 1920 | $75 | $144,000 |
| Total labor estimate | $594,000 | ||
| Function point estimate | Quantity | Conversion Factor | Function Points |
| External inputs | 10 | 4 | 40 |
| External interface files | 3 | 7 | 21 |
| External outputs | 3 | 5 | 15 |
| External queries | 3 | 4 | 12 |
| Logical internal tables | 6 | 10 | 60 |
| Total function points | 148 | ||
| Java 2 languange equivalency value | 46 | ||
| Source lines of code (SLOC) estimate | 6,808 | ||
| Productivity *KSLOC^Penalty (person months) | 30.27 | ||
| Total labor hours (160 hours/month) | 4,842.55 | ||
| Cost/labor hour ($120/hour) | $120 | ||
| Total software development estimate | 581,106 |
Sheet3
earned_value.xlsx
EV data
| Earned Value Calculations for Project Name | |||||||||||||||||
| Prepared by: | Date: | ||||||||||||||||
| Note: Change the entries to meet your project needs. This data is from Figure 7-4 of Schwalbe's text Information Technology Project Management, Fourth Edition. | |||||||||||||||||
| Also make sure the formulas work properly based on the data you enter. | |||||||||||||||||
| To Date | Planned | Actual | |||||||||||||||
| Activity | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | PV | % Complete | % Complete | RV | EV |
| Plan and staff project | 4,000 | 4,000 | 8,000 | 100 | 100 | 100% | 8,000 | ||||||||||
| Analyze requirements | 6,000 | 6,000 | 12,000 | 100 | 100 | 100% | 12,000 | ||||||||||
| Develop ERDs | 4,000 | 4,000 | 8,000 | 100 | 100 | 100% | 8,000 | ||||||||||
| Design database tables | 6,000 | 4,000 | 10,000 | 100 | 100 | 100% | 10,000 | ||||||||||
| Design forms, reports, and queries | 8,000 | 4,000 | 8,000 | 75 | 50 | 67% | 5,333 | ||||||||||
| Construct working prototype | 10,000 | - 0 | - 0 | ||||||||||||||
| Test/evaluate prototype | 2,000 | 6,000 | - 0 | - 0 | |||||||||||||
| Incorporate user feedback | 4,000 | 6,000 | 4,000 | - 0 | - 0 | ||||||||||||
| Test system | 4,000 | 4,000 | 2,000 | - 0 | - 0 | ||||||||||||
| Document system | 3,000 | 1,000 | - 0 | - 0 | |||||||||||||
| Train users | 4,000 | - 0 | - 0 | ||||||||||||||
| Monthly Planned Value (PV) | 4,000 | 10,000 | 10,000 | 10,000 | 12,000 | 16,000 | 10,000 | 6,000 | 8,000 | 4,000 | 5,000 | 5,000 | 43,333 | ||||
| Cumulative Planned Value (PV) | 4,000 | 14,000 | 24,000 | 34,000 | 46,000 | 62,000 | 72,000 | 78,000 | 86,000 | 90,000 | 95,000 | 100,000 | |||||
| Monthly Actual Cost (AC) | 4,000 | 11,000 | 11,000 | 12,000 | 15,000 | ||||||||||||
| Cumulative Actual Cost (AC) | 4,000 | 15,000 | 26,000 | 38,000 | 53,000 | ||||||||||||
| Monthly Earned Value (EV) | 4,000 | 10,000 | 10,000 | 10,000 | 9,333 | ||||||||||||
| Cumulative Earned Value (EV) | 4,000 | 14,000 | 24,000 | 34,000 | 43,333 | ||||||||||||
| Project EV as of May 31 | 43,333 | ||||||||||||||||
| Project PV as of May 31 | 46,000 | ||||||||||||||||
| Project AC as of May 31 | $ 53,000 | ||||||||||||||||
| CV=EV-AC | $ (9,667) | ||||||||||||||||
| SV=EV-PV | $ (2,667) | ||||||||||||||||
| CPI=EV/AC | 81.761% | ||||||||||||||||
| SPI=EV/PV | 94.203% | ||||||||||||||||
| Estimate at Completion (EAC) | $ 122,308 | (original plan of $100,000 divided by CPI) | |||||||||||||||
| Estimated time to complete | 12.74 | (original plan of 12 months divided by SPI) | |||||||||||||||
EV chart
Chart1
| 4000 | 4000 | 4000 |
| 14000 | 15000 | 14000 |
| 24000 | 26000 | 24000 |
| 34000 | 38000 | 34000 |
| 46000 | 53000 | 44000 |
| 62000 | ||
| 72000 | ||
| 78000 | ||
| 86000 | ||
| 90000 | ||
| 95000 | ||
| 100000 |
Chart4
| 3 | 4 | 3 |
| 8 | 8 | 8 |
| 19 | 18 | 19 |
| 32 | 29 | 31 |
| 47 | 41 | 41.5 |
| 63 | 56 | 48.645 |
| 91 | 83 | 73.045 |
| 145 | ||
| 206 | ||
| 233 | ||
| 246 | ||
| 254 |
Sheet1
| Activity | Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | Plan | % Complete | EV |
| Plan and staff project | 4,000 | 4,000 | 8,000 | 100 | 8,000 | ||||||||||
| Analyze requirements | 6,000 | 6,000 | 12,000 | 100 | 12,000 | ||||||||||
| Develop ERDs | 4,000 | 4,000 | 8,000 | 100 | 8,000 | ||||||||||
| Design database tables | 6,000 | 4,000 | 10,000 | 100 | 10,000 | ||||||||||
| Design forms, reports, and queries | 8,000 | 4,000 | 12,000 | 50 | 6,000 | ||||||||||
| Construct working prototype | 10,000 | 10,000 | - 0 | - 0 | |||||||||||
| Test/evaluate prototype | 2,000 | 6,000 | 8,000 | - 0 | - 0 | ||||||||||
| Incorporate user feedback | 4,000 | 6,000 | 4,000 | 14,000 | - 0 | - 0 | |||||||||
| Test system | 4,000 | 4,000 | 2,000 | 10,000 | - 0 | - 0 | |||||||||
| Document system | 3,000 | 1,000 | 4,000 | - 0 | - 0 | ||||||||||
| Train users | 4,000 | 4,000 | - 0 | - 0 | |||||||||||
| Monthly Plan | 4,000 | 10,000 | 10,000 | 10,000 | 12,000 | 16,000 | 10,000 | 6,000 | 8,000 | 4,000 | 5,000 | 5,000 | 100,000 | 44,000 | |
| BCWS or Cumulative Plan | 4,000 | 14,000 | 24,000 | 34,000 | 46,000 | 62,000 | 72,000 | 78,000 | 86,000 | 90,000 | 95,000 | 100,000 | |||
| Monthly Actual | 4,000 | 11,000 | 11,000 | 12,000 | 15,000 | ||||||||||
| ACWP or Cumulative Actual | 4,000 | 15,000 | 26,000 | 38,000 | 53,000 | ||||||||||
| Monthly EV | 4,000 | 10,000 | 10,000 | 10,000 | 10,000 | ||||||||||
| BCWP or Cumulative EV | 4,000 | 14,000 | 24,000 | 34,000 | 44,000 | ||||||||||
| Project BCWP as of May 31 | 44,000 | ||||||||||||||
| Project BCWS as of May 31 | 46,000 | ||||||||||||||
| Project ACWP as of May 31 | $ 53,000 | ||||||||||||||
| CV=BCWP-ACWP | $ (9,000) | ||||||||||||||
| SV=BCWP-BCWS | $ (2,000) | ||||||||||||||
| CPI=BCWP/ACWP | 83% | ||||||||||||||
| SVI=BCWP/BCWS | 96% | ||||||||||||||
| Estimated cost at completion | $ 120,455 | (original plan of $100,000 divided by CPI of 83%) | |||||||||||||
| Estimated time to complete | 12.55 | (original plan of 12 months divided by SVI of 96%) | |||||||||||||
| Above for Figure 6-2 | |||||||||||||||
| Chart below for Figure 6-3 |
Sheet1
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | 0 | 0 |
| 0 | ||
| 0 | ||
| 0 | ||
| 0 | ||
| 0 |
Sheet2
Sheet3
-
20,000
40,000
60,000
80,000
100,000
120,000
123456789101112
Month
$
Planned Value (PV)
Budget at Completion (BAC)
Actual Cost (AC)
Earned Value (EV)
Estimate at Completion (EAC)
expectations.docx
Expectations Management Matrix
Prepared by: Date:
|
Measure of Success |
Priority |
Expectations |
Guidelines |
|
Scope
|
|
|
|
|
Time
|
|
|
|
|
Cost
|
|
|
|
|
Quality
|
|
|
|
|
Customer Satisfaction
|
|
|
|
|
Financial Impact |
|
|
|
final_documentation.docx
Final Project Documentation for Project Name
Prepared by: Date:
I. Project description
II. Project proposal and backup data (request for proposal, statement of work, proposal correspondence, and so on)
III. Original and revised contract information and client acceptance documents
IV. Original and revised project plans and schedules (WBS, Gantt charts and network diagrams, cost estimates, communications management plan, etc.)
V. Design documents
VI. Final project report
VII. Deliverables, as appropriate
VIII. Audit reports
IX. Lessons learned reports
X. Copies of all status reports, meeting minutes, change notices, and other written and electronic communications
Gantt_chart.mpp
issue_log.docx
Issue Log
Prepared by: Date:
|
Issue # |
Issue Description |
Impact on Project |
Date Reported |
Reported By |
Assigned To |
Priority (M/H/L) |
Due Date |
Status |
Comments |
|
1 |
|
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
|
3 |
|
|
|
|
|
|
|
|
|
|
etc. |
|
|
|
|
|
|
|
|
|
kick-off_meeting.docx
Just-In-Time Training Project
Kick-off Meeting
Date
Meeting Objective: Get the project off to a great start by introducing key stakeholders, reviewing project goals, and discussing future plans
Agenda:
· Introductions of attendees
· Background of project
· Review of project-related documents (i.e. business case, project charter)
· Discussion of project organizational structure
· Discussion of project scope, time, and cost goals
· Discussion of other important topics
· List of action items from meeting
|
Action Item |
Assigned To |
Due Date |
|
|
|
|
|
|
|
|
|
|
|
|
Date and time of next meeting:
lessons_learned_report.docx
Lessons Learned Report
|
Prepared by: Date: Project Name: Project Sponsor: Project Manager: Project Dates: Final Budget: |
|
1. Did the project meet scope, time, and cost goals?
2. What was the success criteria listed in the project scope statement?
3. Reflect on whether or not you met the project success criteria.
4. In terms of managing the project, what were the main lessons your team learned?
5. Describe one example of what went right on this project.
6. Describe one example of what went wrong on this project.
7. What will you do differently on the next project based on your experience working on this project?
|
list_of_risks.docx
List of Prioritized Risks for Project Name
Prepared by: Date:
|
Ranking |
Potential Risk |
|
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
6 |
|
|
7 |
|
|
8 |
|
|
9 |
|
|
10 |
|
milestone_report.docx
Milestone Report for Project Name
Prepared by: Date:
|
Milestone |
Date |
Status |
Responsible |
Issues/Comments |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
network_diagram.mpp
pareto_chart.xlsx
Sheet1
| Pareto Diagram for Remote Deposit Capture Project | |||
| Problem | Count | % | Cumulative % |
| Allow scanning multiple checks at once | 30 | 30% | 30% |
| Show simple checkbox to select account to make deposit into | 25 | 25% | 55% |
| Make showing check scanned image the default | 18 | 18% | 73% |
| No confirmation message after scanning check | 15 | 15% | 88% |
| Show running total for all checks scanned | 9 | 9% | 97% |
| Add video/animation for instructions | 3 | 3% | 100% |
| Total | 100 | ||
Sheet2
Sheet3
payback.xlsx
Sheet1
| Year | Costs | Benefits | Cum Costs | Cum Benefits |
| 0 | 140,000 | 0 | 140,000 | 0 |
| 1 | 37,200 | 186,000 | 177,200 | 186,000 |
| 2 | 34,400 | 172,000 | 211,600 | 358,000 |
| 3 | 31,600 | 158,000 | 243,200 | 516,000 |
Payback
cumulative costs 0 1 2 3 140000 177200 211600 243200 cumulative benefits 0 1 2 3 0 186000 358000 516000Year
$
Sheet2
Sheet3
prob_impact_matrix.pptx
Probability/Impact Matrix for Project Name
Impact
Probability
low
medium
high
low
medium
high
risk 1
risk 4
risk 6
risk 9
risk 2
risk 5
risk 11
risk 3
risk 7
risk 8
risk 10
risk 12
progress_report.docx
Status/Progress Report
|
Project Name: Team Member Name: Date: Reporting Period: |
|
Work completed this reporting period:
|
|
Work to complete next reporting period:
|
|
What’s going well and why:
|
|
What’s not going well and why:
|
|
Suggestions/Issues:
|
Project changes
|
project_desc_Gantt.mpp
project_desc_text.docx
Project Name Description
Prepared by: Date:
Objective:
Scope:
Assumptions:
Cost:
Schedule:
project_org_chart.pptx
Organizational Chart for Project Name Prepared by: Date:
qualty_assurance_plan.docx
Quality Assurance Plan for Project Name
Prepared by: Date:
1.0 Draft Quality Assurance Plan
1.1 Introduction
1.2 Purpose
1.3 Policy Statement
1.4 Scope
2.0 Management
2.1 Organizational Structure
2.2 Roles and Responsibilities
2.2.1 Technical Monitor/Senior Management
2.2.2 Task Leader
2.2.3 Quality Assurance Team
2.2.3 Technical Staff
3.0 Required Documentation
4.0 Quality Assurance Procedures
4.1 Walkthrough Procedure
4.2 Review Process
4.2.1 Review Procedures
4.3 Audit Process
4.3.1 Audit Procedures
4.4 Evaluation Process
4.5 Process Improvement
5.0 Problem Reporting Procedures
5.1 Noncompliance Reporting Procedures
6.0 Quality Assurance Metrics
Appendix
Quality Assurance Check List Forms
ram.xlsx
Sheet1
| Responsibility Assignment Matrix for Project Name | ||||||||||
| Prepared by: | Date: | |||||||||
| WBS Activities | 1.1.1 | 1.1.2 | 1.1.3 | 1.2.1 | 1.2.2 | 1.2.3 | 2.1.1 | 2.1.2 | 2.1.3 | |
| OBS Units | ||||||||||
| A | ||||||||||
| B | ||||||||||
| C | ||||||||||
| D | ||||||||||
| E | ||||||||||
| F | ||||||||||
| Key: |
Sheet2
Sheet3
reqs_matrix.docx
Requirements Matrix for Project Name
Prepared by: Date:
|
Requirement No. |
Name |
Category |
Source |
Status |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
resource_histogram.xlsx
Sheet1
| Resource Histogram for Project Name | ||||||
| Prepared by: | Date: | |||||
| Month 1 | Month 2 | Month 3 | Month 4 | Month 5 | Month 6 | |
| A | 1 | 1 | 1 | 1 | 1 | 1 |
| B | 2 | 2 | 2 | 1 | 1 | 1 |
| C | 1 | 1 | 4 | 4 | 4 | 1 |
| D | 0 | 0 | 0 | 1 | 1 | 1 |
Number of People
Sheet2
Sheet3
rfp_outline.docx
Request for Proposal (RFP) Outline
for Project Name
Prepared by: Date:
I. Purpose of RFP
II. Organization’s Background
III. Basic Requirements
IV. Hardware and Software Environment
V. Description of RFP Process
VI. Statement of Work and Schedule Information
VII. Possible Appendices
A. Current System Overview
B. System Requirements
C. Volume and Size Data
D. Required Contents of Vendor’s Response to RFP
E. Model Contract
risk_register.xlsx
Sheet1
| Risk Register for Project Name | |||||||||||
| Prepared by: | Date: | ||||||||||
| No. | Rank | Risk | Description | Category | Root Cause | Triggers | Potential Responses | Risk Owner | Probability | Impact | Status |
Sheet2
Sheet3
scope_statement.docx
Scope Statement (Version xx)
|
Project Title: Date: Prepared by: |
|
Project Justification:
. |
|
Product Characteristics and Requirements: 1. 2. 3. 4.
|
|
Summary of Project Deliverables Project management-related deliverables: business case, charter, team contract, scope statement, WBS, schedule, cost baseline, status reports, final project presentation, final project report, lessons-learned report, and any other documents required to manage the project. Product-related deliverables: research reports, design documents, software code, hardware, etc. 1. 2. 3. 4.
|
|
Project Success Criteria:
|
stakeholder_register.docx
Stakeholder Register for Project Name
Prepared by: Date:
|
Name |
Position |
Internal/External |
Project Role |
Contact Information |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
stakeholder_strategy.docx
Stakeholder Management Strategy for Project Name
Prepared by: Date:
|
Name |
Level of Interest |
Level of Influence |
Potential Management Strategies |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
statement_of_work.docx
Statement of Work for Project Name
Prepared by: Date:
I. Scope of Work:
Describe the work to be done to detail. Specify the hardware and software involved and the exact nature of the work.
II. Location of Work:
Describe where the work must be performed. Specify the location of hardware and software and where the people must perform the work
III. Period of Performance:
Specify when the work is expected to start and end, working hours, number of hours that can be billed per week, where the work must be performed, and related schedule information.
IV. Deliverables Schedule:
List specific deliverables, describe them in detail, and specify when they are due.
V. Applicable Standards:
Specify any company or industry-specific standards that are relevant to performing the work.
VI. Acceptance Criteria:
Describe how the buyer organization will determine if the work is acceptable.
VII. Special Requirements:
Specify any special requirements such as hardware or software certifications, minimum degree or experience level of personnel, travel requirements, and so on.
sw_project_mgt_plan.docx
Software Project Management Plan (SPMP) Outline
for Project Name
Prepared by: Date:
Introduction
Project Overview
Project Deliverables
Evolution of the SPMP
Reference Materials
Definitions and Acronyms
Project Organization
Process Model
Organizational Structure
Organizational Boundaries and Interfaces
Project Responsibilities
Managerial Process
Management Objectives and Priorities
Assumptions, Dependencies, and Constraints
Risk Management
Monitoring and Controlling Mechanisms
Staffing Plan
Technical Process
Methods, Tools, and Techniques
Software Documentation
Project Support Functions
Work Packages, Schedule, and Budget
Work Packages
Dependencies
Resource Requirements
Budget and Resource Allocation
Schedule