Reference no: EM131335303

Assignment

Outcomes addressed in this Assignment:

Outcomes:

• Prepare the Project Charter outlining identified needs and your proposed solution

• Examine possible hardware and software solutions for identified problems

• Specify the system improvements and additional capabilities needed to meet the identified needs

Client Specifications: Analyze users' technical issues.

Technology Analysis: Evaluate IT trends, practices, and products.

Assignment Instructions:

The Project Charter is the most important documentation for the course. This document will provide the foundation for the entire project. This will be used to evaluate the success of your Final Project and presentation. Your professor will use this document to assess whether the project objectives have been completed in the Final Project. You will identify the project objectives, assumptions, scope, milestones, deliverables, impact statement, roles and how success will be measured. It is substantial documentation and will require a time investment. Do not rush through the file. There are ample resources available online for completing a Project Charter. Please be sure to conduct the necessary research to complete quality documentation.

Project Requirements:

Complete the Project Charter and address the following:

1. Project Objectives: Focus on how business needs are being solved. How do the objectives support the business strategies?

Note: For Web projects in particular, this does not address interface designs or any design details at this point.

The Project Charter does not include any visual design aspects in terms of color palettes, fonts, or images being used.

2. Assumptions: These will address circumstances and outcomes which can be taken for granted. You will not have all concrete information to begin the project, but you can make some assumptions.

Examples may include vendor reliability and availability of resources.

3. Project Scope: Address the deliverables of the project. Options may include system upgrades, help files, documentation, full source code, training and support. Also establish some boundaries. For example, if you are developing a network, how many offices will it entail? If computer systems are being upgraded, is this limited to certain departments, such as sales, or does it involve the entire organization?

4. Project Milestones: Examples of high level milestones range from completing the Project Charter and receiving approval, completion of design phase, and beginning of execution phase. Low level milestones could include completion of web mockups, beginning physical topology schematics, and beginning prototype development. Include a combination of high and low level milestones.

5. Impact Statement: How will this project impact the business objectives? Will the updated network result in secured VPN access? Or will the new shopping cart result less in cart abandonment and in higher conversion rates? Will the backup server result in a higher level of privacy and security for customer data?

6. Roles and Responsibility: Who are your team members and what are their responsibilities? While it is likely you may be the only one developing this project, identify and designate the additional roles necessary to achieve your objectives. This section does need to be completed by everyone.

7. Success Measurements: What are the success metrics and measures? Has the new database replaced or integrated duplicate systems? Have the Google analytics proven an increase in Web traffic? Has the software package resulted in high customer satisfaction ratings? Has the guaranteed network uptime been increased successfully?

While expansive, this document will serve as the foundation for all subsequent Assignments. It will also be the document your instructor references to ensure all aspects have been completed by the end of the term. Takeyour time to conduct research to complete the file and please be sure to start this early in the week! Throughout the term, to help you evaluate if enough content is in place, consider how a client or team would review the documentation. Would they be left with questions or would they understand how to proceed on the project without having to ask for clarification? If they can proceed, then enough content is in place. There will always be questions about minor details, but all main content should be firmly established in the documentation.

Written Assignment Requirements

Answers or website materials contain sufficient information to adequately answer the questions and contain no spelling, grammar, or APA errors. Points deducted from grade for each writing, spelling, or grammar error are at your instructor's discretion.