1. DeFoor Greenhouse Network Project
Group 2 Members:
Jaris Tilstra
Meir Shapiro

2. Outline Project Overview Employee Labor Costs Project Deliverables
Project Charter
Stakeholder Registry
Risk Register
Probability/Impact Matrix
Project Scope Statement
Employee Labor Costs
Project Cost Estimate
Responsibility Matrix
Comm. Management Plan
Lessons Learned
Project Assessment
Questions
* There is a notes section on some slides *

3. Project Overview Greenhouse is located at Tucumcari, New Mexico
Includes environmentally friendly energy sources
Need to provide a computer for each office
10 monitors to measure temperature, humidity, and sunlight
Needs to be operational in 12 weeks
The budget is $100,000
The DeFoors were recently awarded a state grant that will enable them to set up a state-of-the-art greenhouse in Tucumcari, New Mexico.
This greenhouse will include wind-generated electricity, geothermic heat exchangers, and light from solar tracking devices.
The company has located a 27,000 square foot building to use as their first greenhouse.
The building will contain one office for the bookkeeper, one for the sales manager, one for the greenhouse manager and a reception area.
There will also be an internet connection to meet future company needs.
There are 5 employees working on the project. 1 project manager, 2 full-time employees and 2 part-time employees.

4. Project Deliverables Project Charter Work Breakdown Structure (WBS)
Gantt Chart
Cost Estimate
Resource Assignments
Communications Plan
Risk Register and Matrix

5. Project Charter Project Sponsor: Mr. and Mrs. DeFoor
Project Start Date: 09/16/13
Projected Finish Date: 12/09/13
Project Manager: Jaris Tilstra
Budget Information: $100k for labor and network components procurement.
Project Team: Jaris Tilstra, Meir Shapiro, Tanishia Brown, Steve Williams, Elizabeth Smith
Project Objectives
To have a functional network set up within 12 weeks and under the $100k budget.
The network will allow the company to monitor temperature, humidity, and sunlight in the greenhouse. 3 functional workstations for employees need to be connected to the network.
Coordinate with the website project team to determine what web servers and internet connections will be available.
Coordinate with the network construction team to determine if physical changes are necessary to implement the network.

6. Stakeholder Registry Name Role Position
Contact Information
Mr. & Mrs. DeFoor
Sponsor
Owners
Jaris Tilstra
Project Manager
Manager
Meir Shapiro
Team Member
Network Engineer
Tanishia Brown
Steve Williams
Elizabeth Smith
Kevin Pham
Consultant
IT Director
Jason Stanley
PR Head
Leslie Taylor
HR Director
Hailey Bucket 
 Consultant
Admin Assist.

7. Risk Register Rank Risk Description Category 1 Outdated wiring
The wiring and/or WAN is not suitable for the building
Technology 2
Customers go elsewhere
Customers could potentially go elsewhere for their produce
Project 3
Installation takes too long
Installation can take longer than expected
Human Resources 4
Lack of experience
The team members may have a limited amount of experience with this type of project 5
Shortage of network engineers
With multiple projects going on there may be a shortage in network engineers 6
Monitor placement issues
The setup of the greenhouse may not support the proper placement of monitors
Hardware

8. Probability/Impact Matrix
High
Risk 1
Risk 3
Risk 6
Risk 4
Risk 5
Probability
Medium
Low
Risk 2
Low
Medium
High
Impact

9. Project Scope Statement
Project Summary and Justification
Summary of Project Deliverables
Project Success Criteria
Project Summary and Justification: Project charter was approved by the sponsors – Mr. & Mrs. DeFoor. Based on the recent grant received from the state we have been allocated $100,000 to design a network and procure the necessary hardware & software for the recently purchased building in Tucumcari, New Mexico.
Summary of Project Deliverables:
Management related: project charter, project scope statement, WBS, WBS dictionary, schedule, cost estimate, status reports, risk register & matrix, final project presentation, final project report, lessons-learned report
Technology related: network design document, 3 workstations, 10 monitors, web servers, printers, support schedule for the onsite team
Success Criteria: Design and support an attainable network plan that will stay within the $100,000 budget and will finish no later than 12/09/13 . Procure, setup and validate that all hardware and software for the workstations and greenhouse monitoring is functional. The Network should satisfy the needs and requirements of the project sponsor and stakeholders.

10. Gantt Chart

11. Employee Labor Costs 1.1 Initiation All Members $738 1.2 Planning
$5,715
1.3
Execution
$44,492
1.4
Control
$2,144
1.5
Closeout
$1,191
Total:
$54,280

12. Project Cost Estimate Subtotals WBS Level 1 Totals % of Total
Subtotals
WBS Level 1 Totals
% of Total
WBS Items
1. Initiation
$738 1%
1.1 Project manager
$378
1.1 Project team members
$360
2. Planning
$5,715 6%
1.2 Project manager
$3,965
1.2 Project team members
$1,750
3. Execution
$73,546
74%
1.3 Project manager
$13,027
1.3 Project team members
$31,465
1.3.3 Workstations Cost
$4,500
1.3.3 Monitors Cost
$8,053
1.3.3 Web Servers Cost
$3,000
1.3.3 Printers Cost
$1,500
1.3.3 Software Cost
$12,000
4. Control
$2,144 2%
1.4 Project manager
$944
1.4 Project team members
$1,200
5. Closeout
$1,191
1.5 Project manager
$566
1.5 Project team members
$625
6. Reserves (20% of total estimate)
$16,667
17%
Total project cost estimate
$100,000

13. Responsibility Matrix
WBS Activities
1.1.1
1.1.2
1.1.3
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.3.1
1.3.2
1.3.3
1.3.4
1.4.1
1.4.2
1.4.3
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
OBS Units
Meir Shapiro P RP
Tanishia Brown
Elizabeth Smith
Steve Williams p
Jaris Tilstra
Key:
R = Responsible organizational unit
P = Performing organizational unit
1 DeFoor Greenhouse - Network 1.1 Initiation Identifying Project Stakeholders Project Charter Kick-off Meeting 1.2 Planning Requirement Gathering Preliminary Scope Statement Develop WBS Identify Risks Develop Schedule 1.3 Executing Verify & validate User Requirements Design Building Network Procure Hardware / Software Contact vendors for quotes Order Software & Hardware Support On-Site Team Greenhouse Operational 1.4 Controlling Project Status Meetings Progress Reports Control Changes 1.5 Closing Client Acceptance Lessons Learned Meeting Lessons Learned Report Archive Project Documentation Project completed

14. Communications Management Plan
Stakeholders
Document Name
Document Format
Contact Person
Due Date
DeFoor Network Project Team
Weekly Schedule
Box
Jaris Tilstra
Mondays
Bi-Weekly updates to the communications plan
1st and 3rd Mondays of the month
Internal management
Monthly status reports
and meeting
First of the month
Internal technical staff
Steve Williams
Customer business staff
Hard copy
Tanishia Brown
Customer technical staff
Tanisha Brown
Network Installer
Network Implementation Plan
Meir Shapiro
November 10, 2013
Comments: Put titles and date of all documents in headings and have all recipients acknowledge receipt. Change headings and subject lines as necessary.
Introduction – The purpose of this communications plan is to describe the means with which information will be shared regarding the DeFoor Network project. This plan details the different aspects of communication regarding the project and should be used as a guide for communicating with the right people at the right time in the right format.
Target Audiences –
DeFoor Network Project Team – Includes the members actively involved in the project.
Internal Management – DeFoor Managers
Internal Technical Staff - Staff in charge of internal IT.
Customer Business Staff – Staff in charge of business matters.
Customer Technical Staff – Staff in charge of customer technical issues.
Network Installer –Person in charge of installing the new network.
Collection and filing structure – The file collaboration website that will be used for this project is the “Box” ( Jaris Tilstra will be sending out Box invites for this project. Simply follow the instructions in the invite. This will be the site that holds all relevant files and reports related to this project.
Distribution structure – Follow the Stakeholder Communications Analysis table below which depicts which information goes to whom and when. See the media choice table document that is under the communication folder on the Box for choosing the correct media for the correct situation.
Format, content, and level of detail of key project information – We will be using the communications templates found under the communications folder on the Box. This template will tell you what format, content, and level of detail to use. If a section is not relevant for the report leave it in the proper place with a notation why there is no relevant information.
Production schedule and resources for producing key project information – The schedule and resources will be found on the Box that is updated every Monday.
Technologies, access methods, and frequency of communications – We will be using the following communication tools for this project:
Box - For file sharing
– For collaboration, reports and plans.
Hard Copy – For specific reports and plans.
Meetings – For weekly meetings, monthly meetings, collaboration &
Microsoft Lync (instant messaging & video chat) – Daily discussions & collaboration.
Phone – As necessary (See the media choice table document).
The frequency of communications is variable depending on needs. There are also set dates in the stakeholder communications analysis below.
Method for updating the communications management plan – The communications management plan will be reviewed and/or modified on a bi-weekly basis. If you have any input to the plan, please add to the punch list on the Box and it will be reviewed and either accepted or declined.
Escalation procedures – We will run all external issues from Mr. and Mrs. DeFoor through our customer service team. Depending on the severity of the issue, the customer service team will then send out an to the appropriate people so the issue can be resolved.

15. Lessons Learned
Make sure everyone involved in the project understands and agrees with the objectives an requirements of the project.
Set deadlines for review and signoff of weekly deliverables
Make sure to subscribe to the forum as soon as possible
Be active in the forum early on every week so you are not rushed at the end.
Get to know your team members better

16. Project Assessment Hardest Parts Easiest Parts
Understanding the project requirements
Learning MS Project
Assigning resources in MS Project
Losing a team member during the project
Communicating with group team members
Team members each put their fair share of workload to the project
Were able to have our deliverables submitted on time

17. Questions?