Summary/Introduction -

Identify the problem, propose an IT solution, and discuss WHY it is necessary. Talk about where the problem is located, and how you propose solving it.

Make the scope of the project clear, and be sure and add an additional sentence or two that clearly state that this document is a proposal to implement your specific project/solution.

Review of Other Work - This is where you talk about third party work done in the area by using sources (we recommend at least 4 for the proposal) to justify decisions you are making in the project.

This can be white papers, best practices, tech blogs, etc. Try going to ProQuest database in the WGU library and using the search terms ‘white papers on [your topic]' or ‘research studies on [your topic]' and you will find more than you need. See https://owl.english.purdue.edu/owl/resource/560/02/ for help with correct formatting of in-text citations.

Rationale and System Analysis - Rationale is the WHY... why is this project needed?

Systems Analysis means to describe the current state of affairs that makes this project necessary, to further justify the need for this project. Also, at the end of this section be sure and give a brief description of the project management methodology will you use, and how will it manage your project effectively.

Goals and Objectives - A precise list of specific goals for the project and this must include their corresponding objectives.

A good format is:

Goal #1:

- Objective 1: Step to reach the goal
- Objective 2:

Then you will provide some paragraph information about each goal and its corresponding objectives. You will repeat this for goal #2 and its objectives, and so on.

Goals are the big picture (most project management methodologies include more than one phase/goal). Each goal will have objectives, which are the measurable steps that must be taken to achieve that goal. Deliverables are the predicted outcomes for Tech Writing, and proof of completion examples for Capstone (screen shots, snippets of code, network map, pictures of work done, etc.).

Capstone Guide

Please note that each section below aligns with aspects of the rubric for this course. You should think of each section as a question on an objective exam... it is asking for something very specific. So even if you already discussed something in a previous section, you must give the information required. In other words, not only is it OK to repeat yourself in different sections, it is expected.

Precise Description and Summary - Begin with a precise description of the project (this is a rubric requirement). For example, something like "This report discusses a virtualization project for XYZ company, to solve the problem of... and to support the..." (you get the idea). Then you will give a logical overview of the entire development of the project, from start to finish... for example, this is the problem that was identified, this is what was proposed, this is what was accepted, this is how it was actually implemented, and these were the outcomes.Wrap it up with a statement of what the project accomplished.

Other Work - This is where you expand the third party work done in the area by using additional sources (we recommend at least 7 total for Capstone) to tie into the actual implementation of the project (as in, ‘this informed this aspect of the project' or ‘this showed us a new direction to take' or ‘this paper helped validate our results.' As for Tech Writing, these can be white papers, best practices, tech blogs, etc. Try going to ProQuest database in the WGU library and using the search terms ‘white papers on [your topic]' or ‘research studies on [your topic]' and you will find more than you need. See https://owl.english.purdue.edu/owl/resource/560/02/ for help with correct formatting of in-text citations.

Rationale and System Analysis - First explain the WHY... why was this project needed, and what do the results show now that the project is completed? Then describeboth the state of affairs in the company (or wherever the identified problem existed) before implementation, and then describe the state of affairs after completion of the project, which should also justify the completed project and why the project was necessary.

Project Goals and Objectives: Here you must write a few paragraphs explaining why or why not each of the goals and objectives was met. Don't leave any out!

Project Timeline - The timeline needs to include the table format of your project milestones from Tech Writing, and must include duration, as well as start date and projected end dates. But you must now add an additional column for Actual End Date, and all dates must be in the past because this is a post-implementation report.

Then you must write a few paragraphs explaining why or why not each of your timeframes was met. Be thorough.

Project Development - Here you must explain the development and implementation of the project, with an emphasis onwhat it actually accomplished.

Then write a paragraph or two for each of the following sub-sections:

Problems Encountered - identify any problems encountered and explain how they were solved

Reasons for Changes - explain any changes made to the original proposal

Unanticipated Requirements - explain any unanticipated requirements or components and how you resolved them

Actual and Potential Effects - explain the actual outcomes/effects of the project, and discuss any potential effects on down the road

Conclusions - discuss your conclusions about the success and effectiveness of this project

Attachment:- Assignment.rar