null

TITLE OF YOUR PAPER 4

Title of Capstone Here
Author’s Full Name, including middle initial, Here

Running head: 50-CHARACTER VERSION OF TITLE IN CAPS 1
TITLE OF YOUR PAPER 2

Table of Contents
Summary 3
Review of Other Work 3
Changes to the Project Environment 3
Methodology 3
Project Goals and Objectives 3
Project Timeline 4
Unanticipated Requirements 4
Conclusions 4
Project Deliverables 4
References 6
Appendix A: 7
Appendix B: 8
Appendix C: 9
Appendix D: 10

Note: On the pages that follow, keep the bolded main heading but delete the prompt material once you’ve reviewed and made the necessary additions and adjustments. Also, update the running head and title page. Remove this note as well

Summary
In this section, include a logical overview the project’s client, setting, problem, proposed solution, and how the solution was carried out. The details should include a description of the flow of the project, including all the major aspects that were accomplished.

From the Proposal: Proposal Overview including the following:
1. Problem Summary
2. IT Solution
3. Implementation Plan

What to Adjust: Remove the subheadings (e.g. Problem Summary). Convert the material to past tense where necessary and provide additional details as to how the project was implemented in the last part of this section.

Note: Be sure that your entire capstone report is written in past tense so it reflects a completed project.

Review of Other Work
In this section, provide an expanded review of the Review of Other Work section. You may accomplish this two ways: 1. Using the sources from the proposal but adding three new ones. 2. Starting from scratch with three new sources. The new sources must deal with how the project was implemented.

From the Proposal: You may insert your entire Review of Other Work from the proposal but be sure it reads in the past tense. If you wish, you may leave out that material and start from scratch to meet the section’s requirements. Either approach is acceptable so consider how relevant your proposal material is to the final report when deciding to keep or start from scratch.

What to Adjust: Provide a review of three additional works on your topic (not referenced in Task 2) that relate to development of this project. Look for sources that provide guidance, answer questions, or include technical material that was helpful.
 
Note: These other works may include interviews, white papers, research studies, best practices, configuration/implementation guides, migration paths, case studies, or other types of work that are publicly accessible.

Project Rationale is not used in the final capstone report. Do not copy from the proposal.

Changes to the Project Environment
In this section, describe and detail changes to the project environment made by the implementation of the project after its completion. Analyze the systems and describe the status of the project environment after the project implementation.

From the Proposal: Move your Current Project Environment material from the proposal. Label this as the “original” environment before the project was completed.

What to Adjust: Add new material (another paragraph works) that describes how the original environment changed once the project was completed. What’s new and what did it improve?

Methodology
In this section, describe and detail how your completed project was governed by a specific methodology. Explain how a standard methodology was applied for the implementation of the project.

From the Proposal: Move your proposal’s Methodology section to this report.

What to Adjust: You’ll want to make the old material read in past tense. You’ll also want to add specific project details or examples to the phases of your methodology to emphasize what you actually accomplished.

Project Goals and Objectives
In this section, provide a detailed explanation on how the project goals and objectives were met. If goals and/or objectives were not accomplished, that’s fine as long as you provide a reason as to why.

From the Proposal: Copy your Goals, Objectives, and Deliverables section. You may also copy the Goals table as it helps the evaluator more clearly understand the hierarchy.

What to Adjust: Make sure this reads in past tense. You may remove the deliverables. You must include a clear, obvious statement with each goal and objective about how it was successfully completed. If you decide to leave the deliverable, connecting them with your objective’s success statement is an effective approach.

Project Timeline
In this section, create a timeline that deals with planned and actual durations and the final project’s start and end dates. Include a paragraph after the timeline that compares the durations and provides information about where times did or did not work out as planned.

From the Proposal: Copy the timeline table.

What to Adjust: Create new headings that include: Planned Duration, Actual Duration, Actual Start Date, and Actual End Date. Keep the Deliverables column. Remove or rename the proposal’s date columns.
Note: Because the project is now completed, all the dates must be in the recent past. The evaluator will not compare them to the proposal dates.

Unanticipated Requirements
In this section, describe the requirements that emerged during implementation. These are not timing related (those go in the timeline) but relate to hardware, software, or personnel-type issues that arose during the project’s implementation. Additionally, be sure to explain how they were resolved or why they were not solved. This is a new section.

Conclusions

In this section, explain the actual project accomplishments and immediate and potential future effects of the completed project. Include at least one measurable metric that was used to prove the project’s success.

From the Proposal: Copy the Outcome section.

What to Adjust: Change your Outcome to past tense. Include information about immediate and potential effects from the completed project. Provide specific examples where relevant. Update the measurable metric information from the proposal. If there is none, add new material that specifies what was measured and what measurement indicated success.

Project Deliverables
In this section, describe at least three project artifacts (examples) that appear in the appendices. The artifacts should provide a logical display to substantiate the described successes and benefits of the completed project. Refer to each appendix item (included after the References section as Appendix A, Appendix B, etc.) and describe how it demonstrates evidence of the project’s completion. Artifacts may include such things as: code samples, screen shots, photos, flowcharts, process diagrams, tables, graphs, network diagrams (before and after), training materials or related documents (e.g., policies), etc. This is a new Section.

References
List all the outside sources that the narrative refers to in-text. For in-text and reference list citations, please refer to the web link in the Course of Study or visit the WGU Writing Center.
Note: Ensure that you have an in-text citation for each full citation and vice versa. Those citation pairs must match up according to APA formatting. For example:

In-text found in the body of the document:

The article also states design elements shouldn’t be confusing and that mobile apps should be designed with disruption in mind as the user will frequently change tasks while using the mobile device. (Osborne, 2018)

Full citation appearing in this section:

Osborne, B. (2018). 6 Mobile App Development Best Practices Worth a Glance. Retrieved from https://www.topcoder.com/blog/6-mobile-app-development-best-practices

Appendix A
Title of Appendix
Put any supporting material in these appendices. Add additional or delete superfluous appendices as needed.

Appendix B
Title of Appendix
Put any supporting material in these appendices. Add additional or delete superfluous appendices as needed.

Appendix C
Title of Appendix
Put any supporting material in these appendices. Add additional or delete superfluous appendices as needed.