Do a Project Charter for Internet of Things (IoT) device vulnerability analysis project
Describe the business need, social need, customer request, technological advancement, opportunity or problem that the project was undertaken to address - i.e., the project justification. Why would someone want to invest in your project? 2. DELIVERABLES What are the proiect artifacts? A project artifact is a piece of hardware, software, documents, presentations, etc. Each deliverable should be sufficiently detailed so that the Project Team will understand what needs to be accomplished. Describe the deliverable using action words (verbs) such as "deliver, provide, create, research, etc. Deliverables should be measurable, so the Project Sponsor and Team can determine whether the deliverable has been successfully completed at the project's conclusion. What needs to be approved for the project to be objectively considered complete? 1. 2. 3. Document the scope of work to be delivered. Provide a high level list of 'what' needs to be accomplished in order to meet the goals of the project. To assist you in defining scope, use documentation such as RFP', sales proposals, business requirements, functional specifications, etc. to set and limit the scope. In Scope is what the project will include to meet the requirements of the Project goals. Out of Scope excludes responsibilities, activities, deliverables or other areas that are not part of the Project. The project will include: The project will not include: Identify the significant project milestones, including invoicing dates to the client. As a minimum, each deliverable needs to be identified, along with an estimated date relative to the start of the project. Additionally, some interim milestones of project's prototype should be identified, such as software flow diagrams, state diagrams, schematics complete, CCA layouts complete, material received, prototypes assembled, testing complete, etc. 5. ASSUMPTIONS, CONSTRAINTS \& DEPENDENCIES Identify the assumptions that were made to form the basis of defining scope. Also identify any assumptions that will be made for the purposes of planning the project. The objective here is to set the boundaries and address how the triple project management constraint (scope, time and cost) are potentially impacted/managed. List any constraints (potential factors that will impact the delivery or make it difficult to manage the project) on the project or dependencies on resources or funding to the project. Consider time, cost, dates and regulatory issues as constraints or dependencies to the project. Reference any related documents that were used to define scope and assumptions - e.g., RFQ, RFP, Sales Proposal, etc. Identify the primary risk (negatives) that are perceived that may cause the project to not meet the technical performance requirements (scope of work), the schedule, or the cost (both material and labor) Primary Technical Risk: Primary Schedule Risk: Primary Cost Risk: State the proposed/estimated budget for the project and the source of funding (you, your company, a project sponsor, etc.) Estimate the total material (\$)and total labor (man-hours) required. No detailed breakdown is necessary. Software Costs (est): Hardware Costs (est): Labor Hours - Project Team (est): Labor Hours - non-Project Team (est): 8. PROJECT ORGANIZATIONAL STRUCTURE Identify the key stakeholders and team members by name and role
