Title of Capstone Here

Title of Capstone Here

Author's Full Name Here, Including Middle Initial

Western Governors University

Table of Contents TOC o "1-3" h z u Proposal Overview PAGEREF _Toc441469365 h 3Problem Summary PAGEREF _Toc441469366 h 3IT Solution PAGEREF _Toc441469367 h 3Implementation Plan PAGEREF _Toc441469368 h 3Review of Other Work PAGEREF _Toc441469369 h 3Relation of Artifacts to Project Development PAGEREF _Toc441469370 h 4Project Rationale PAGEREF _Toc441469371 h 4Current Project Environment PAGEREF _Toc441469372 h 4Methodology PAGEREF _Toc441469373 h 4Project Goals, Objectives, and Deliverables PAGEREF _Toc441469374 h 5Goals, Objectives, and Deliverables Table PAGEREF _Toc441469375 h 5Goals, Objectives, and Deliverables Descriptions PAGEREF _Toc441469376 h 6Project Timeline with Milestones PAGEREF _Toc441469377 h 6Outcome PAGEREF _Toc441469378 h 7References PAGEREF _Toc441469379 h 8Appendix A: PAGEREF _Toc441469380 h 9Appendix B: PAGEREF _Toc441469381 h 10Appendix C: PAGEREF _Toc441469382 h 11Appendix D: PAGEREF _Toc441469383 h 12

Proposal Overview

The Proposal Overview section (suggested length of 24 pages) introduces the problem and overviews the solution. It contains the "road map" for the organization of the remainder of the paper. Describe the problem the project addresses and then provide an overview of the project and the organization of the paper. Summarize the capstones highlights. Include the following in your summary:

Problem SummarySummaries of the problem should include the context in which this problem exists. Summarize what will and will not be included in the project. Provide sufficient background information so that the reader can appreciate the need for a solution and the approach that will be taken in the project.

IT SolutionDescribe the proposed IT solution to the problem. Clearly identify the relationship between the problem and the proposed solution.

Implementation Plan

This section should contain the details of an implementation plan. Provide details on the different phases (if applicable). Explain how the project will be carried out and why it will be carried out in that manner. Discuss the plan for implementing the project.

Review of Other WorkIn this section (suggested length of 34 pages), review other works done by a third party that are relevant and directly relate to the project. Review at least four other works completed on the chosen topic. Summarize interviews, white papers, research studies, or other types of work by industry professionals. For example, if planning a server upgrade project, summarize articles that describe successful upgrade server solutions in other companies, comparisons of various server hardware and software products that are possible solutions, and any case studies that relate or are similar to the planned server upgrade.

Include the following in your review:

Relation of Artifacts to Project DevelopmentProvide a logical description of how each work reviewed relates to the proposed development of the project. Explain how each of the chosen works contextualize the problem or provide direction to the project.

Project RationaleSummaries should include the rationale for choosing this project, including what makes this problem interesting or significant. The Project Rationale section (suggested length of 12 pages) provides a rationale for the project. It should address the reasons for implementing the project, as described in the Proposal Overview. The rationale may include and expand on both business and technical reasons to support the implementation. Justify the selection of the project.

Current Project EnvironmentThis section (suggested length of 23 pages) describes and details the current project environment. It should also address specifically how the current state will set the direction for the definition and implementation of the proposed solution. Other details that support the description should also be included here as needed to support and succinctly define the project environment. Analyze the systems and describe the status of the project environment before the project began.

MethodologyThis section (suggested length of 12 pages) describes and details the specific methodology. The methodology is the process that the project will follow when it is implemented. Include specific details to adequately describe the steps that will take place to fully execute the project. Explain how a standard methodology (such as PDCA, ADDIE, SDLC, Prototyping or Agile) will be applied for the implementation of the project.

Project Goals, Objectives, and DeliverablesIn Project Goals, Objectives, and Deliverables (suggested length of 35 pages), provide a detailed explanation of the goals and objectives for the project, and explain what the project will provide. There should be a specific and clear identification of each goal and objective, as well as a clear and logical description with adequate detail of each of the goals and objectives. Address and explain the criteria that will be used to measure the objectives in order to demonstrate how each goal and objective will be measured. The project will include some sort of formal report. It will likely also include a technical IT product and/or a users manual or other documentation. Deliverables should provide a detailed logical explanation of what the project will provide to substantiate the work and completion of such. Include the following in the description:

Goals, Objectives, and Deliverables TableEvery project has one or more goals. Each goal is supported by at least one project objective. Each objective is enabled by at least one project deliverable. Fill out this or a similarly organized table:

Goal Supporting objectives Deliverables enabling the project objectives

1 Summarize project goal 1 1.a. Describe project objective 1.a. 1.a.i. Explain project deliverable 1.a.i

1.a.ii. Explain project deliverable 1.a.ii

1.b. Describe project objective 1.b. 1.b.i. Explain project deliverable 1.b.i

1.b.ii. Explain project deliverable 1.b.ii

2 Summarize project goal 2 2.a. Describe project objective 2.a. 2.a.i. Explain project deliverable 2.a.i

2.a.ii. Explain project deliverable 2.a.ii

2.b. Describe project objective 2.b. 2.b.i. Explain project deliverable 2.b.i

2.b.ii. Explain project deliverable 2.b.ii

Goals, Objectives, and Deliverables DescriptionsDescribe each of the project goals. Describe each objective. Explain how the objectives support the goals, and explain how the objectives will be achieved. Explain what types of deliverables the project will provide, and describe the key project deliverables expected by the end of the project. Provide a description of the project goals, objectives, and deliverables that aligns with the Goals, Objectives, and Deliverables Table.

Project Timeline with MilestonesIn this section (suggested length of 12 pages), provide a projected timeline with milestones for the project. These may be estimates that will most likely be adjusted, as many times the project will require adjustments during the development and implementation phases. Provide a projected timeline with milestones for the project, including the duration and start and end dates of each milestone. Include the following table:

Milestone or deliverable Duration

(hours or days) Projected start date Anticipated end date

OutcomeIn this section, describe the anticipated project outcomes and explain how the success of the project will be measured once completed. Explain the expected project outcomes and describe the evaluation framework to be used once the project is completed to assess the projects success and effectiveness.

ReferencesList all the outside sources that the narrative refers to in text. For information regarding in-text and reference list citations, please refer to the web link or visit the WGU Writing Center.

Smyth, A. M., Parker, A. L., & Pease, D. L. (2002). A study of enjoyment of peas. Journal of Abnormal Eating, 8(3), 120-125. Retrieved from

http://www.articlehomepage.com/full/url/

Bernstein, M. (2002). 10 tips on writing the living Web. A List Apart: For People Who Make Websites, 149. Retrieved from http://www.alistapart.com/articles/writeliving

Bell, T., & Phillips, T. (2008, May 6). A solar flare. Science @ NASA Podcast. Podcast retrieved from http://science.nasa.gov/podcast.htm

OLPC Peru/Arahuay. (n.d.). Retrieved April 29, 2011 from the OLPC Wiki: http://wiki.laptop. org/go/OLPC_Peru/ArahuayPlath, S. (2000). The unabridged journals. K. V. Kukil (Ed.). New York, NY: Anchor.

Appendix A

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

Appendix BTitle of Appendix

Put any supporting material in these appendices. Add additional or delete superfluous appendices as needed.

Appendix C

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

Appendix D

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

Title of Capstone Here

Author's Full Name Here, Including Middle Initial

Western Governors University

Table of Contents TOC o "1-3" h z u Summary PAGEREF _Toc441471473 h 3Review of Other Work PAGEREF _Toc441471474 h 3Changes to the Project Environment PAGEREF _Toc441471475 h 3Methodology PAGEREF _Toc441471476 h 3Project Goals and Objectives PAGEREF _Toc441471477 h 3Project Timeline PAGEREF _Toc441471478 h 4Unanticipated Requirements PAGEREF _Toc441471479 h 4Conclusions PAGEREF _Toc441471480 h 4Project Deliverables PAGEREF _Toc441471481 h 4References PAGEREF _Toc441471482 h 6Appendix A: PAGEREF _Toc441471483 h 7Appendix B: PAGEREF _Toc441471484 h 8Appendix C: PAGEREF _Toc441471485 h 9Appendix D: PAGEREF _Toc441471486 h 10

SummaryThe Summary section includes a logical overview of the project with sufficient detail to sufficiently describe the actual development of the entire project. Provide a precise description of the project. The description should also provide adequate detail to describe all the components of the project. The details should include a description of the flow of the project, including all the major aspects that were accomplished.

Review of Other WorkIn this section, provide an expanded review of the Review of Other Work section in task 2, including three additional third-party artifacts on the topic that supported the development of the project, and explain how the artifacts supported the implementation.

Changes to the Project EnvironmentThis section describes and details 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 implementation of the project.

MethodologyThis section describes and details the specific methodology. The methodology is the process that the project filled by being implemented. Explain how a standard methodology was applied for the implementation of the project.

Project Goals and ObjectivesIn this section, provide a detailed explanation on how some goals and objectives were met and why some goals and objectives for the project were not accomplished. Identify the objectives that were met and explain how they were met, and then explain the reasons why some objectives were not accomplished.

Project Timeline

In this section, compare the projected and actual timelines of the milestones or deliverables of the project and explain why the differences occurred. Explain the reasons for each deviation of the actual time frame from the estimated time frame.

Note: All timeline dates MUST be in the past as this document is an after-action report that should reflect a project that is completed.

Unanticipated RequirementsIn this section, describe the requirements or components that were not anticipated at project initiation but emerged during implementation. Describe the problems encountered and the unanticipated requirements, and then explain how they were resolved or why they were not solved.

ConclusionsIn this section, provide an explanation of the actual results and potential effects of the completed project. Describe the actual project accomplishments and discuss the immediately observable effects and potential future impacts of the completed project on the project environment. Explain why the project is or is not considered successful using the evaluation framework from the Outcome section in the project proposal.

Project DeliverablesIn the Project Deliverables section, explain and detail the project key deliverables. The actual project development will be documented by the key deliverables. The project includes some sort of formal report. The deliverables should provide a detailed logical explanation of what the project provided to substantiate the work and completion of such. Describe the artifacts being used to show evidence of the projects completion and use the appendices to include the actual artifacts. Actual project artifacts may include code samples or screen shots; flowcharts, UML, or other process diagrams; charts, tables, and graphs; network diagrams (before and after); training materials; and/or the technical IT product itself.

ReferencesList 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 or visit the WGU Writing Center.

Smyth, A. M., Parker, A. L., & Pease, D. L. (2002). A study of enjoyment of peas. Journal of Abnormal Eating, 8(3), 120-125. Retrieved from

http://www.articlehomepage.com/full/url/

Bernstein, M. (2002). 10 tips on writing the living Web. A List Apart: For People Who Make Websites, 149. Retrieved from http://www.alistapart.com/articles/writeliving

Bell, T., & Phillips, T. (2008, May 6). A solar flare. Science @ NASA Podcast. Podcast retrieved from http://science.nasa.gov/podcast.htm

OLPC Peru/Arahuay. (n.d.). Retrieved April 29, 2011 from the OLPC Wiki: http://wiki.laptop. org/go/OLPC_Peru/ArahuayPlath, S. (2000). The unabridged journals. K. V. Kukil (Ed.). New York, NY: Anchor.

Appendix A

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

Appendix BTitle of Appendix

Put any supporting material in these appendices. Add additional or delete superfluous appendices as needed.

Appendix C

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

Appendix D

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

IT Capstone Topic Approval Form

The purpose of this document is to help you clearly explain your capstone topic, project scope, and timeline, and to assure that they align with your degree emphasis. Without clearly addressing each of these areas, you will not have a complete and realistic overview of your project and your Course Instructor cannot accurately assess whether your project will be doable for the purposes of these courses.

Of course, if this is a project that you have already completed at work or elsewhere, this should be easy to fill in! Most students use a project that they have already completed in the past year or two. In that case, you will write the proposals (Tasks 1 and 2) as if the project has not been done yet, and Task 3 as the complete post-implementation report.

Complete this form and send it (via UGCapstoneIT@WGU.edu) to your Course Instructor for approval. Once approved, you will receive a signed document in PDF format that you can upload as part of Task 1.

DEGREE EMPHASIS:

ANALYSIS:

Project Topic -

Problem Statement or Project Purpose -

DESIGN and DEVELOPMENT:

Project Scope

Project Goal(s) and Supporting Objectives

Project Outcomes and Deliverables

Projected Project End Date

IMPLEMENTATION and EVALUATION:

Describe how you will approach the execution of your project

COURSE INSTRUCTOR SIGNATURE:

COURSE INSTRUCTOR APPROVAL DATE: