*** Please utilize the Kanban project methodology : please look at Scenario B attachment*** Assignment 1: (please use the project proposal attachment) For this assignment, you will create a 3- to 4-

*** Please utilize the Kanban project methodology : please look at Scenario B attachment***

Assignment 1: (please use the project proposal attachment)

For this assignment, you will create a 3- to 4-page project proposal for the business scenario you selected earlier this week and that was approved by your instructor. The project proposal must include the following items:

• A project definition and scope that defines the project and articulates the business context for the project
• The problems that the proposed system is expected to solve (or opportunities the proposed project is expected to produce)
• The project objectives
• The project methodology or "game plan"
• A high-level schedule for completing the project scope

Fill out the template based on the business scenario you selected (and that was approved by your instructor) earlier this week. If you prefer, you may recreate the template using another software application of your choice, such as Microsoft Project or Microsoft Excel.

Assignment 2:  (please use the project plan draft attachment)

For this assignment, you will draft a project plan for the project proposal you outlined in Week 1 (and updated earlier this week based on instructor feedback).

Create a 3- to 4-page project plan draft, based on the document provided, for the business scenario you chose last week. You may fill out the document using Microsoft Word, or other another software (such as Microsoft Excel or Microsoft Project), to create your project plan draft. Your draft must include the following items:

• Network technology recommendation(s)
• Database management system recommendation(s)
• Appropriate software application recommendation(s)
• Cloud service recommendation(s)

Assignment 3: (Please use supporting research template attachment) 

Conducting research and creating a supporting research report serves two important purposes with respect to your project:

1. It explains your technological choices in terms of business benefits and risks. This explanation is crucial for executive approval.
2. It either reinforces or improves your plan--but 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 and change 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 developed and forced to retire at a very quick pace.

For this assignment, you will conduct 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.

Conduct additional research on your project's industry, recommended technology vendors, and the categories presented in the Supporting Research Report. You may want to include the Gartner Group and Forrester Research in your list of organizations to research.

Complete the Supporting Research Report template.

Create a second draft of your project plan. Highlight in yellow the three changes you made to the second draft based on the in-depth research you conducted this week, and explain why you made the changes.

Submit both your Supporting Research Report and second draft.

Assignment 4:

To complete this assignment, you will need to create the following components:

• 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, Microsoft Visio, Lucidchart, 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, Microsoft Visio, Lucidchart, 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 HTML/JavaScript/CSS sample code (attached)files for an example of a partial software application implementation.
• A quality assurance and software test plan
• Download the Software Test Plan (attached) 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.

Assignment 5: Project roll-out begins after a project has been implemented, tested, and judged stable and functional enough to be moved into production. The project roll-out process comprises of 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 that 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,"), when referred to it in a business context is the analysis of a project's process and results conducted by key project stakeholders after the project has been moved into production, which means it's 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 assignment, you will need to do three things:

1. Complete a work-back schedule that presents the steps involved in implementing your project.
2. Conduct a post-mortem on the work you have submitted to date in this course.
3. Update your project documents based on the results of your post-mortem.

Review the Project Implementation Plan Example(attached).

Create a project implementation plan for your project based on the example document. You may use Microsoft Word or other software (such as Microsoft Project) to create your project implementation plan.

Download and complete the Post-Mortem template(attached) based on your experiences completing the course project over the last five weeks.

Revise the project documents you have submitted so far in the course based on your completed post-mortem.

Submit your project implementation plan, post-mortem, and updated project documents.