All referenced attachments included. I have also included previous versions (Nortons Bank & Projectplan w2) to build off of.
(1.)
Conducting research and creating a supporting research report serves two important purposes with respect to your project:
- It explains your technological choices in terms of business benefits and risks. This explanation is critical for executive approval.
- It either reinforces or improves your planbut only if you apply the results of your research to a new draft of your plan. In the industry, project managers develop their plans iteratively by changing them as they conduct more research and identify better or cheaper alternatives. This iterative approach is especially relevant to IT projects because new technologies are being developed and retired at a very quick pace.
For this assignment, you will compile research and create a supporting research report. Then, based on your research, you will identify and explain the rationale for three improvements to the project plan you submitted last week.
Compile additional research on your projects industry, recommended technology vendors, and the categories presented in the supporting research report. You may want to include the and in your list of organizations to research.
Complete the template.
Create a second draft of your project plan. Highlight in yellow at least three changes you made to the network, database, and/or cloud solutions within the second draft based on the in-depth research you conducted this week and explain why you made the changes.
Submit your Supporting Research Report and second draft.
(2. )
Project implementation is arguably the most exciting stage of the project management process. It is during project implementation that project plans begin to come to life and assumptions are able to be tested and measured in real-life scenarios.
One of the outcomes of project implementation is a set of deliverables that typically includes a system diagram; a network diagram; a database design document, including an entity-relationship diagram, a data dictionary, and table definitions; a clearly articulated cybersecurity plan; and source code.
To complete this assignment, you will create:
- A system diagram that shows, in graphic form, the components of your project.
- Your system diagram should follow the system description you submitted in your Week 2 project plan (but may differ based on the research you have conducted since Week 2).
- You may create your system diagram in Microsoft PowerPoint or a graphics program of your choice.
- A network diagram that shows, in graphic form, the flow of data within your project.
- Your network diagram should follow the network description you defined in the Week 2 project plan (but may differ based on the research you have conducted since Week 2).
- You may create your network diagram in Microsoft PowerPoint or a graphics program of your choice.
- A database design document, including an entity-relationship diagram, a data dictionary, and table definitions, representing all of the data that must be stored and maintained within the context of your project and how that data is organized.
- A clearly articulated cybersecurity plan that explains how you plan to secure project data and processes.
- Source code (may be partial) for at least one software application.
- Your source code may be implemented in HTML/JavaScript, Java, C++, or another programming language.
- Download and unzip the files for an example of a partial software application implementation.
- A quality assurance and software test plan.
- Download the for an example of what information is typically included and how it is typically organized in a software test plan.
Note: All deliverables must be portfolio ready, which means as complete and error-free as possible.
(3.)
Project rollout begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project rollout process comprises specific steps that must be scheduled carefully to enable the project to hit production deadlines and meet business expectations.
For this assignment, you will create an implementation project plan, which outlines the steps involved in implementing your project. This document is sometimes called a work-back schedule because you begin with the date that your project needs to go live, and then work back from there to determine what needs to be done when.
You will also conduct a post-mortem on the work you have submitted to date. Post-mortem (from the Latin for after death, but referring to it in the context of business) is the analysis of a projects process and results conducted by key project stakeholders after the project has been moved into production, which means its functionally complete. The goal of a post-mortem is to identify what went right and what went wrong post-implementation so that project managers can apply these lessons learned to future projects.
For this three-part assignment, you will:
- Construct a work-back schedule that presents the steps involved in implementing your project.
- Construct a post-mortem using the template on the work you have submitted to date in this course.
- Create updated project documents based on the results of your post-mortem.
Review the .
Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software to create your project implementation plan.
