Capstone Draft 2

IT700ProjectReportDraftsGuidelinesandRubric.pdf

Home >Computer Science homework help >Capstone Draft 2

IT 700 Capstone Component 2: IT Project Report Guidelines and Rubric Overview: For your IT project report, the second of three capstone components, you will imagine that the key stakeholders for whom you wrote your proposal gave you the go-ahead to implement your information technology solution to the problem you identified. You have designed and developed your project solution, and now you must report to the stakeholders. In other words, for this capstone component, you will design and develop your project solution and then report on it. If you are able to implement your solution, include a summary of your implementation and testing in your report. If you are not able to implement your solution, you may develop a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project. In this case, in your report you should include a plan for implementation and testing. Your report must provide clear evidence that your project was implemented and tested (or is implementable and testable). This can be achieved by documenting a demonstration of the project in use or documenting an explanation of the model, simulation, or prototype. Consider using video or screenshots to demonstrate and explain your project. If the implemented project is to be supplied to the instructor, you could provide a user manual that explains how to install, configure, and run the software. You are encouraged to submit artifacts of the project including diagrams, software applications, database designs, process documents, etc. Make sure to include clear instructions for accessing and using these artifacts. The design and development of your project solution should demonstrate professional- level knowledge and skills. Your project report should include at least one recommendation for future enhancements. Explain what you might add to the project if you had more resources? What risk(s) would you need to consider before the enhancement was implemented at some future point in time? What would have to happen first before the future enhancement was even considered seriously? You will submit drafts of this component in Modules Four, Five, and Seven. You will have the opportunity to review your instructor’s feedback and submit the final draft of all sections of the IT Project Report in Milestone Nine. The following sections are required in your project report (though you are not limited to including only these sections):

1. Project Design: Analyze the problem that you have identified and explain why the problem is significant. [Draft Submitted in Module Four] 2. Project Implementation: If you implemented your project, describe the implementation. If your project was not implemented, how would you

implement it? As you work on the project each module, the status of the project will be updated in this section. Describe the status of the implementation to date. [Draft Submitted in Module Five]

3. Project Test Plans and Results: If you implemented and tested your project, describe how you tested your project. If your project was not implemented or tested, how would you test it? [Draft Submitted in Module Five]

4. Recommendations for Future Enhancements: Explain what you might add to the project if you had more resources. What risk(s) would you need to consider before the enhancement was implemented at some future point in time? What would have to happen first before the future enhancement was even considered seriously? [Draft Submitted in Module Seven]

5. Appendix: Supporting Evidence of Project Implementation: Include your supporting documents in this section. For example, your screenshots or user

manual should be included here. [Draft Submitted in Module Seven]

Component 2: IT Project Report Draft I Rubric Overview: The IT project report draft due in Module Four should contain the following section:

o Section 1: Project Design Your draft should address the following:

 Discuss the problem or challenge you addressed

 Apply knowledge of stakeholder needs to report

 Evaluate how well the model worked

 Discuss the successes and challenges of the pilot

 Develop a modification strategy for the pilot Guidelines for Submission: Your draft must be submitted as a 2–3 page Microsoft Word document with double spacing, 12-point Times New Roman font, and one-inch margins. Be sure to cite all sources in APA format, including a properly formatted references list and the inclusion of in-text citations. Include a title page with the title of the project, your name, and the date.

Critical Elements Proficient (100%) Not Proficient (0%) Value

Problem Statement

Clearly articulates the problem or challenge addressed

Does not clearly articulate the problem or challenge addressed

Stakeholder Needs:

Application of Knowledge

Applies knowledge of stakeholder needs to the project design

Does not apply knowledge of stakeholder needs to the project design

Overview of Design

Describes the project design, e.g., stages of development, challenges faced, etc.

Does not describe the project design 30

Articulation of Response

Submission has no major errors related to citations, grammar, spelling, syntax, or organization

Submission has major errors related to citations, grammar, spelling, syntax, or organization

Earned Total 100%

Component 2: IT Project Report Drafts II and III Rubric

Overview: The IT project report drafts due in Modules Five and Six should contain the following sections:

o Section 2: Project Implementation o Section 3: Project Test Plans and Results

Your draft should address the following:

 Describe the implementation of the project or the plan for implementation

 Describe the project testing or testing plan

 Summarize your implementation and testing or develop a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project

Guidelines for Submission: Your draft must be submitted as a 2–3 page Microsoft Word document with double spacing, 12-point Times New Roman font, and one-inch margins. Be sure to cite all sources in APA format, including a properly formatted references list and the inclusion of in-text citations. Include a title page with the title of the project, your name, and the date.

Critical Elements Proficient (100%) Not Proficient (0%) Value

Project Implementation

Clearly articulates the implementation of the project or provides a detailed implementation plan

Does not clearly articulate implementation of the project or provide a detailed implementation plan

Project Testing Describes how the project was tested or a detailed testing plan

Does not describe how the project was tested or a detailed testing plan

Report Summary Summarizes the implementation and testing of the project or develops a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project

Does not summarize the implementation and testing of the project or develop a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project

Articulation of Response

Submission has no major errors related to citations, grammar, spelling, syntax, or organization

Submission has major errors related to citations, grammar, spelling, syntax, or organization

Earned Total 100%

Component 2: IT Project Report Draft IV Rubric

Overview: The IT project report draft due in Module Seven should contain the following sections:

o Section 4: Recommendations for Future Enhancements o Section 5: Appendix

Your draft should address the following:

 Discuss how the successes/challenges/lessons learned from the project

 Describe a modification strategy/plan with actionable steps to improve upon the project

 Explain any potential issues (e.g., resource limitations or technical problems) that arose from the project

 Make sure your submission has no major errors related to citations, grammar, spelling, syntax, or organization

Critical Elements Proficient (100%) Not Proficient (0%) Value

Successes, Challenges, and Lessons Learned

Discusses how the successes, challenges, and/or lessons learned from the project could be applied to enhance the project in the future

Does not discuss how the successes, challenges, and/or lessons learned from the project could be applied to enhance the project in the future

Modification Strategies and

Actionable Steps

Develops a modification strategy/plan for the project and describes actionable steps to improve upon the project

Does not develop a modification strategy/plan for the project or does not describe actionable steps to improve upon the project

Potential Issues Explain any potential issues identified from the project (e.g., resource limitations or technical problems)

Does not explain potential issues identified from the project

Appendix Supporting materials included provide validating, reinforcing, and/or supplemental evidence that strengthens the project report

Supporting materials are not included or do not validating, reinforcing, and/or supplemental evidence that strengthens the project report

Articulation of Response

Submission has no major errors related to citations, grammar, spelling, syntax, or organization

Submission has major errors related to citations, grammar, spelling, syntax, or organization

Earned Total 100%

Component 2: IT Project Report Draft V Rubric

Overview: The IT project report draft due in Module Eight should contain the following sections:

o Section 1: Project Design o Section 2: Project Implementation o Section 3: Project Test Plans and Results o Section 4: Recommendations for Future Enhancements o Section 5: Appendix

Guidelines for Submission: Be sure to cite all sources in APA format, including a properly formatted references list and the inclusion of in-text citations. Include a title page with the title of the project, your name, and the date. Your report should be approximately 8–10 pages in length.

Critical Elements Proficient (100%) Not Proficient (0%) Value

Problem Statement

Clearly articulates the problem or challenge addressed Does not clearly articulate the problem or challenge addressed

Stakeholder Needs: Application

of Knowledge

Applies knowledge of stakeholder needs to the project design

Does not apply knowledge of stakeholder needs to the project design

Overview of Design

Describes the project design, e.g., stages of development, challenges faced, etc.

Does not describe the project design 10

Project Implementation

Clearly articulates the implementation of the project or provides a detailed implementation plan

Does not clearly articulate implementation of the project or provide a detailed implementation plan

Project Testing Describes how the project was tested or provides a detailed testing plan

Does not describe how the project was tested or provide a detailed testing plan

Report Summary Summarizes the implementation and testing of the project or develops a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project

Does not summarize the implementation and testing of the project or develop a model, simulation, prototype, or proof of concept as an alternative to developing a fully implemented project

Successes, Challenges, and Lessons Learned

Discusses how the successes, challenges, and/or lessons learned from the project could be applied to enhance the project in the future

Does not discuss how the successes, challenges, and/or lessons learned from the project could be applied to enhance the project in the future

Modification Strategies and

Actionable Steps

Develops a modification strategy/plan for the project and describes actionable steps to improve upon the project

Does not develop a modification strategy/plan for the project or does not describe actionable steps to improve upon the project

Potential Issues Explain any potential issues identified from the project (e.g., resource limitations or technical problems)

Does not explain potential issues identified from the project 10

Appendix Supporting materials included provide validating,

reinforcing, and/or supplemental evidence that strengthens the project report

Supporting materials are not included or do not validating, reinforcing, and/or supplemental evidence that strengthens the project report

Earned Total 100%