SWDS - Green Team Management Plan 12/10/2010
-Green Team Management Plan-
-Author-
Marissa Hornbrook: Project Manager
-Date-
December 10, 2010
1. Program Identification
This Program Management Plan (PMP) is for the fall implementation of ODU CS410 Project - Green Team. The project deliverable is the Surface Water Detection System (hereafter referred to as SWDS) hardware, software and documentation. SWDS team is responsible for the integration, acceptance testing and maintenance of the product.
1.1 Program Management Overview
Program execution will be performed according to the standards developed by several SWDS project specification documents. These documents are identified as the following:
ü Management Plan (This explanatory document)
ü Resources Plan
ü Risk Management Plan
ü Evaluation Plan
ü Marketing Plan
ü Staffing Plan
ü Funding Plan
ü Appendices
This Program Management Plan describes the management philosophy, program organization, schedule, and major milestones that serve as the guide for execution of the Program. The PMP also provides the customer with the information needed to monitor and evaluate the progress of SWDS. This plan provides the following information:
· Corporate Organization during Phases 0-3
· Program Team Organization with Areas of Responsibility
· Detailed Program Schedule and Milestones
· Work Breakdown Structure
1.2 Management Approach
SWDS’s management goal is to work closely with the customer to fully understand the system requirements and field a system that meets those requirements. The management approach to executing contracts at SWDS is based on the philosophy that successful Programs are delivered by goal-oriented teams. A Program Manager (PM) will lead the team. The PM is responsible for all planning, programmatic, technical, and financial aspects of the Program. The PM is the primary Point of Contact (POC) for the customer. The PM is responsible for all Program-related decisions and commitments with approval, as required, from the Corporate Management Team (Board of Directors). A key element of SWDS’s program management approach is customer involvement. We encourage the customer to retain an active role in monitoring the progress of all aspects of the program. The customer is encouraged to discuss technical details directly with members of the development team, provide planning and schedule recommendations, and assist in resolution of technical and programmatic issues. In order to facilitate customer involvement, SWDS staff will provide access to program information including, but not limited to:
· program plans and schedules
· program status
· formal review material
· action items
· system drawings and documentation
2. Project Outlook
The goal of SWDS is to provide a solution to the problem that currently, roadways prone to flooding lack a city controlled contiguous alert system to warn drivers of dangerous water levels. Such a system could assist drivers in preventing vehicle damage and personal injury in cases where they proceed through inundated portions of the road.
The core of this project will be an alert system which notifies drivers of high water levels in flooded roadways, to warn them against driving through that portion of the road. This can be done with our basic closed system design, consisting of a single ultrasonic sensor, microcontroller, and flashing warning sign. If a more extensive solution is desired, the client can choose to implement our networked solution, which consists of a network of ultrasonic sensors which send data (water levels) not only to flashing signs on-site, but also to a database to be manipulated.
3. Tool Utilization
SWDS team members will primarily use recitation meetings to collaborate and communicate ideas. The SWDS team website (www.cs41x.com) will be used to share and store ideas and documents through the use of the implemented repository and wiki features. Recitation meetings, CS e-mail, and the CS410 website will be used to establish meeting times, deadlines, and other important dates in order for the project manager to utilize time efficiently and delegate to the team.
4. Team Organization and Corporate Structure
The SWDS Corporation formed in August of 2010 and its members made a commitment to quality innovation and production. The following sections outline the SWDS Corporate organizational structure and member responsibilities during the different phases of the project.
4.1 Phase 0 (CS410) & Phase 1 (CS 411)
Among the tasks, phases 0 and 1 of the project include the problem identification and analysis, consultation with a domain expert, preparation of business plans, establishing of the team’s website, prototype design and development. According to those tasks, the team consists of the following specialists:
Fig. 2 - Phase 0 and Phase 1 Organization Chart
Staff Listing/Skills:
· Marissa Hornbrook: Project Manager
§ Rank: Senior, Old Dominion University
§ Skills: Management, web development, C++ programming, software development, technical writing, database management.
§ Responsibilities: The Project Manager is responsible for the coordination, communication, and collaboration of the team, monitoring development, and delegating task assignments/project schedules.
· Eric Boyd: Web Developer/Webmaster
§ Rank: Senior, Old Dominion University
§ Skills: Web Development, ASP.NET Development, Software Engineering
§ Responsibilities: The web developer is responsible for designing, developing, and maintaining the web application software portion of the solution, in addition to the internal SWDS website
· Robert Dayton: Hardware and Communications Specialist
§ Rank: Senior, Old Dominion University
§ Skills: C++/C#/BASIC Programming, embedded prototyping development, basic hardware implementation, and networking.
§ Responsibilities: The Hardware Specialist is responsible for the design, networking, and implementation of all hardware required in the development of SWDS. Essentially responsible for a large part of the embedded system development and prototype creation.
· Jill Mostoller: Research and Development
§ Rank: Senior, Old Dominion University
§ Skills: Programming: C, C++, Java
§ Responsibilities: Research and Development Specialist is responsible for researching to solve team problems and assisting implementation of the SWDS prototype. Also responsible for documenting work in written reports and oral presentations, in addition to accomplishing additional tasks as needed.
· Cassandra Rothrauff: Marketing and Public Relations
§ Rank: Senior, Old Dominion University
§ Skills: HTML, PHP, Javascript, AJAX, Unix, networking
§ Responsibilities: The Marketing Specialist is responsible for promoting and maintaining a positive image for SWDS, and will represent the company while establishing and maintaining contacts with the client. The Marketing Specialist will also design and implement effective marketing campaigns and thorough market research plans.
4.2. Phase 2- Functional Prototype and Development
During phase 2, when the actual product is developed from the previously built prototype, the team is increased with the following additional specialists: Network Engineer and Remote/On-Site Technical Support.
Fig. 2 - Phase 2 Organization Chart
Phase 2 Increased Staff Listing:
· Network Engineer:
§ Responsibilities: The Network Engineer is responsible for troubleshooting, support, monitoring, security, documentation, equipment configuration, performance and ensuring the highest quality in maintaining the SWDS sophisticated networked solution.
· Technical Support:
§ Responsibilities: The Technical Support Specialist is responsible for providing first-level contact and problem resolution for all users with hardware, software and applications problems. Their goal is to resolve as many user-reported problems as expertise permits using available tools and following procedures and policies for the handling of support cases. Support Specialist will use advanced troubleshooting skills to solve both user and network issues.
4.3. Phase 3- Post Production
To begin mass production of the SWDS, additional staff will need to be acquired, in the following capacities: Accounting & Finance Specialist, Sales Representative, and Administrative Assistant.
Fig. 4 - Phase 3 Organization Chart
Phase 3 Increased Staff Listing:
· Accounting & Finance Specialist:
§ Responsibilities: The Accounting and Finance Specialist is responsible for all areas relating to financial reporting. This position will be responsible for developing and maintaining accounting principles, practices and procedures to ensure accurate and timely financial statements. This is to include payroll, basic bookkeeping, A/P, A/R, tax reporting, and employee benefits.
· Sales Representative:
§ Responsibilities: The Sales Representative is responsible for interesting buyers and purchasing agents in the SWDS, addressing clients’ questions and concerns. Sales Representative will demonstrate advise clients on how using the SWDS can benefit the local city government. Sales Representative may spend much of their time traveling to and visiting with prospective buyers and current clients.
· Administrative Assistant:
§ Responsibilities: The Administrative Assistant is responsible for answering telephones and transferring the calls to appropriate team members, general clerical duties, and limited human resource duties.
4.4 Program Duration
The SWDS program is a 3 year project. The first prototype deliverable will be produced by May 2011 in Phase 1 of the project. Subsequent releases of the prototype will be produced in accordance with client requests.
5. Progress Performance Assessment
All SWDS Team members will participate in progress reporting and team management. SWDS staff will track technical and financial progress of the program, and meetings will be held monthly or as mutually agreeable the project manager and customer to discuss:
· Report on progress to date
· Present work to be performed during the next month
· Present status of all deliverables and review planned delivery dates
· Discuss technical or programmatic issues as necessary.
In preparation for the meetings the SWDS Project Manager will collect the current status data on relevant on-going activities, progress against schedule and budget, and planned activity for the next reporting period. Quality reviews of all program documentation and procedures will be held periodically. In particular, the quality program will be involved with program deliveries and milestones and will work off of the master program schedule laid out by the work breakdown structure. Following are the details of the project milestones and the work breakdown structure.
Progress Reports
In order to maintain a thorough understanding of the project’s progress, several reports will be required throughout the duration of the project. These include monthly progress reports, technical reports, budget reports, and reviews.
Monthly Progress Reports
Monthly Progress reports will be due from each member of the team. These reports are to be submitted to the Project Manager and will detail what has been
accomplished since the last report, what is currently in progress, and what is still withstanding. These reports will aid the Project Manager in maintaining an overall view of the project’s progress while still maintaining the daily interactions with the rest of the team.
Technical Reports
Technical reports will be delivered by software engineers to their direct supervisors on a weekly basis. These reports will include information on completed tasks, in progress tasks, and pending tasks as scheduled in the work breakdown structure. These reports will also report on any unforeseen problems with the product design.
Budget Reports
The Financial Specialist will be responsible for delivering a weekly budget report to the Project Manager. This report will describe the project’s progress in terms of dollar amount, as defined by the work breakdown structure, and the amount spent to date on staffing, resources, and equipment. This report is intended to identify budget deficits early so that they can be dealt with before they become a major problem.
Reviews
The entire team will be required to deliver a monthly self-review to their immediate supervisors. The contents of these reports are to be decided by the supervisors but should include self-progress, tasks completed, tasks currently being worked on, and any problems that may have hindered their progress.
Evaluations Standards
The Evaluation Plan will determine completion of all tasks and deliverables. Task status reports and progress reports will be handled as described above.
6. Major/Minor Milestones:
1.0 - Closed System Software
Major Features
· Measures distance between itself and its target surface.
· Filters out erroneous measurements such as cars and rapidly changing water levels due to movement of body of water.
· Triggers flashing lights on/off once a calibrated threshold is reached.
Features by Minor Milestone
1.0.1 - Distance Measurement
· Ultrasonic Sensor is programmed to relay depth measurement to microcontroller.
1.0.2 - Measurement Interval
· Microcontroller processes depth measurements over defined time period.
1.0.3 - Filter Logic
· Microcontroller discards erroneous depth measurements such as cars, people, animals, etc.
· Microcontroller establishes a baseline height over the time period.
1.0.4 - Light Triggering Logic
· Microcontroller controls flashing lights based on calibrated threshold.
1.1 - Networked System/User Control Panel
Major Features
· Communicates measurement, threshold, and sensor ID from remote sensor to centralized server.
· Control Panel Application
o Status of remote sensors can be monitored.
o Lights on/off can be overridden from control panel application.
o Sensor parameters can be overridden from control panel such as the filtering logic and distance threshold.
o Recorded data is stored in database.
o Control Panel UI (User Interface) is a web application that can be extended to a public website.
Features by Minor Milestone
1.1.1 - Microcontroller with Network Interface
· Microcontroller uses NIC (Network Interface Card) to transmit measurement, threshold, and ID over ethernet.
1.1.2 - Centralized Receiving of Remote Sensor Transmission
· Application residing on centralized server receives remote sensor transmission.
· Transmission from multiple remote sensors is organized for use in control panel application.
1.1.3 - Security
· Authentication via SSL.
· UI for user administration.
1.1.4 - Database
· Remote sensor data is recorded into a database.
· UI for querying/displaying historical information in control panel.
1.1.5 - Remote Sensor Status Display
· Control panel application displays the current status of each remote sensor (Measurement, Threshold, and ID).
1.1.6 - Control Panel Override of Remote Sensors
· Microcontroller is programmed to be overridden/reset from control panel