Information Technology Project Assignment | Essay Help Services

Adolescents with a Major Depressive Episode in the Past 12 Months Assignment | Online Homework Help
June 16, 2020
Argumentative Blog Post Assignment | Get Paper Help
June 16, 2020

Overview
The final project for this course is the creation of a project closure document.

Information technology (IT) is a field in which practitioners are valued for their ability to plan for and implement solutions. In this course, you will create a project closure document that will include evidence of verification (verification plan) and implementation, or a plan for implementation, based off the design you developed in IT 415 (the prerequisite for this course). Your project closure document, submitted in the form of a report with accompanying documentation, will allow you the opportunity to showcase your ability to translate a design into a real solution to leverage IT.

Don't use plagiarized sources. Get Your Custom Essay on
Information Technology Project Assignment | Essay Help Services
Just from $13/Page
Order Essay

The design and project plan created in IT 415 will be the foundation on which your project closure document should be built. Note that while implementation of your solution design from IT 415 may be helpful in evidencing success in your chosen discipline, there will also be cases in which full implementation is not feasible, not possible given the available tools and environment, or would prove to be unsuccessful given the knowledge obtained during this course. The key to success in this final project does not rest on whether you can fully implement your design. Instead, success will be based on how well you are able to evidence the skills, knowledge, abilities, and dispositions required for successful implementation with the tools and environment available. This means that your explanations of why you cannot implement your project will be just as important as implementation would be. Analysis, communication, strategic planning, research and evidence collection, and many other skills will be emphasized. Regardless of available tools and environments that might limit implementation, the same skills will be needed for planning, predicting, and measuring success.

Your deliverables (including those submitted in support of your project closure document) should reflect your best writing and your highest level of competency in IT and should demonstrate that you possess the critical soft skills required to effectively contribute to a business’s organizational environment.

The project is divided into two milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. These milestones will be submitted in Modules Three and Five. The final project will be submitted in Module Seven.

In this assignment, you will demonstrate your mastery of the following course outcomes:

• IT-420-01: Draft plans and criteria for effectively collecting and evaluating feedback that can improve information technology system designs
• IT-420-02: Develop recommendations in support of decision making that capture and illustrate information system enhancements and opportunities
• IT-420-03: Communicate accurately and efficiently to inform project stakeholders of risks, risk mitigation strategies, and information technology project status
• IT-420-04: Plan for the implementation of effective information technology solution designs using appropriate methods, tools, and technologies
• IT-420-05: Develop effective maintenance strategies for given information systems that meet organizational needs and ensure health and sustainability of the system
Prompt
Your project closure document will evidence the skills, knowledge, abilities, and dispositions required of IT professionals within the specific sub-discipline your chosen topic reflects. You should focus on communicating the required information effectively throughout the project closure document. Remember that stakeholders who read your project closure document are not likely to have contributed to the project development and will require additional context and clear communication.

Specifically, the following critical elements must be addressed:

I. Introduction: Present an overview of the problem that the project addressed, the significance this project has, and objectives that the project should have met. Much of this can be taken from the project proposal submitted in IT 415 but including any necessary alterations or adjustments you made during this course. The aim of this section is to provide context to the rest of the project closure document so that the audience can critically evaluate the completed project and provide feedback. [IT-420-03]

II. Verification Plan: A verification plan will provide an organized way to conduct verification of the system, which can be done through execution of formal test cases that exercise the functionality and performance of the system. It can also include obtaining verbal feedback through focus groups, usability testing of prototypes, and other means. The following sections should be included:
a) Feedback Plan: Construct a comprehensive plan for showcasing your system and collecting feedback from stakeholders. Explain what you will present as regular artifacts of the system to your stakeholders so you can obtain feedback. The stakeholders from whom you must collect feedback will vary depending on your IT issues. [IT-420-01]
b) Criteria: Establish the criteria you will use to determine whether or not feedback received is relevant and actionable. [IT-420-01]
c) Test Cases: In this section, you will describe how you will (or would) test the implemented project to ensure it fulfilled all requirements and that the promised objectives/functionality were met. You will be required to fully test your system and supply the test results as part of the appendix of your project closure document, if implementation of your project is possible. [IT-420-01]

III. Project Closure
a) Postmortem Summary: An important part of IT system development is to capture what worked well and what did not. You should be able to effectively communicate this to stakeholders during a project closure meeting and effectively document this to be referenced as a learning opportunity by other IT developers.

  1. Methodologies: Articulate the methods you used, or would use, for full implementation of your project design. These should speak to the methods and techniques identified in your planning stage from IT 415. [IT-420-04]
  2. Method Evaluation: Evaluate the appropriateness of the methods, tools, and technologies used during project implementation based on the results or based on research evidence in the event you cannot implement your project. [IT-420-04]
  3. Risk Mitigation: Articulate any risks that need to be or would need to be mitigated so that future developers can anticipate these risks in similar projects. [IT-420-03]
    b) Project Status: In this section, discuss the status of your project. You will describe whether it is fully complete and evaluate the effectiveness of the system design.
  4. Objectives: Evaluate whether or not the objectives stated in the original project proposal were met, including those to ensure the design meets organizational/user needs in the long-term. If you cannot implement your proposal, evaluate your implementation plan for its potential to lead to meeting the objectives based on research. [IT-420-05]
  5. Issues: Identify any project objectives that were not fulfilled and explain the risks that prevented fulfillment to inform stakeholders of completion risk, mistakes, and so on. [IT-420-03]
  6. Alternative/Recommendations: If a shortcut or alternative to the planned design was implemented to allow the project to move forward, describe what this was and whether or not it should be corrected or improved in a future version for development. If you could implement your design without any changes, defend your design in terms of ease, efficiency, and effectiveness. It is unlikely that you will be able to fully implement without adjustment to your design, however, so if you did not make changes, defend your reasoning. In the event you could not implement your design, discuss what limited your process and the recommendations you might have for success in the future. [IT-420-02]
  7. Communication: Communicate this section effectively so that stakeholders have a realistic, accurate view of the project’s status. [IT-420-
    03]
    c) Future Enhancements: Recommend future enhancements for the design/system that may further improve decision making or provide additional opportunities for your organization or stakeholders. This could include ideas for developing the system to be used for additional domains or operating environments as well as other uses for the system. [IT-420-02]
    d) Implementation Support: Craft a support plan for implementation that will ensure successful transition for stakeholders, users, and others.
    Describe change management and support strategies that can be implemented if your IT project/system was used in a real world environment.
    [IT-420-05]
    e) Maintenance Plan: Develop a maintenance plan for your design/project that will help to ensure the health and sustainability of the system. Use research to support your conclusions where appropriate. [IT-420-05]
    f) Appendix: Package the design from IT 415 and the various deliverables, documentation, graphics, and other elements in the appendix to provide supportive evidence for the verification plan and for elements A through F of the project closure document. The items included in your appendix may vary depending on the type of project you chose to complete, but some examples could include: [IT-420-04]
  8. All executable files and source codes
  9. Various documentation associated with implement support
  10. All associated webpage and script files for a website. Provide the URL if the website is hosted on a server.
  11. Screenshots or video that demonstrate implementation
  12. Network diagram with photo images/screenshots that prove implementation
  13. Narrated presentation that presents the implemented system
  14. Associated database files and data
  15. Prototype files
  16. Simulation and/or evidence of simulation running

    Milestones
    Milestone One: Draft of Introduction and Verification Plan (Sections I and II)
    In Module Three, you will submit a draft of Section I (introduction) and Section II (verification plan) to include all critical elements listed above. The introduction provides an overview of the IT problem you are addressing. When completed, it should provide sufficient context to facilitate quality feedback from the reviewing audience. Your draft introduction will largely consist of the information from the system proposal and should continue to be updated as required.

The verification plan (Section II) will describe how to verify that the system meets original design specifications, for example, by performing various tests that demonstrate functionality and performance. It should include a detailed feedback plan and comment adjudication guidelines. The submission should be one to two pages. This milestone will be graded with the Milestone One Rubric.

Milestone Two: Draft of Project Closure Document (Section III)
In Module Five, you will submit a draft of the project closure document (Section III). Your draft project closure document must contain a postmortem summary, project status, future enhancements, implementation support, maintenance plan, and appendix. Also, be sure to explain how you incorporated any feedback that you received. The submission should be three to five pages. This milestone will be graded with the Milestone Two Rubric.

Final Submission: Project Closure Document
In Module Seven, you will submit the project closure document. It should be a complete, polished artifact containing all of the critical elements of the final product. It should reflect the incorporation of feedback gained throughout the course. The submission should be seven to eight pages. This submission will be graded with the Final Project Rubric.

Final Project Rubric
Guidelines for Submission: Submit assignment as a Word document with double spacing, 12-point Times New Roman font, and one-inch margins.

Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value
Introduction
[IT-420-03] Meets “Proficient” criteria, and introduction is exceptionally well-written Creates an introduction that provides a clear and comprehensive overview of the issue, the significance of the solution, and the objectives of the project Creates an introduction that provides an overview of the issue, the significance of the solution, and the objectives of the project but with gaps in detail or clarity Does not create an introduction that provides an overview of the issue, the significance of the solution, and the objectives of the project 6.3
Verification Plan:
Feedback
[IT-420-01] Meets “Proficient” criteria and evidences keen insight into crafting successful feedback processes in accordance with the needs of specific IT domains and sub-disciplines Constructs a comprehensive, logical plan for showcasing the system and collecting feedback from stakeholders Constructs a plan for showcasing the system and collecting feedback from stakeholders but with gaps in detail or logic Does not construct a plan for showcasing the system and collecting feedback from stakeholders 6.4
Verification Plan:
Criteria
[IT-420-01] Meets “Proficient” criteria and evidences keen insight into critical evaluation of feedback quality Establishes reasonable and relevant criteria for determining whether or not feedback received is relevant and actionable Establishes criteria for determining whether or not feedback received is relevant and actionable, but criteria are not reasonable or relevant Does not establish criteria for determining whether or not feedback received is relevant and actionable 6.4
Verification Plan: Test
Cases
[IT-420-01] Meets “Proficient” criteria and evidences keen insight into testing procedures and processes for success measurement Articulates a sound process for testing the implemented project to ensure requirement fulfillment Articulates a process for testing the implemented project to ensure requirement fulfillment but with gaps in logic or reason Does not articulate a process for testing the implemented project to ensure requirement fulfillment 6.4
Postmortem Summary:
Methodologies [IT-420-04] Meets “Proficient” criteria and evidences keen insight into integrating methods across design and implementation Articulates methods used for full implementation of the project design that align to those used during design Articulates methods used for full implementation of the project design Does not articulate methods used for full implementation of the project design 6.3

Postmortem
Summary: Method
Evaluation
[IT-420-04] Meets “Proficient” criteria, and the methodologies and approaches were critically evaluated and recommendations for improvements for future projects were presented Critically evaluates the appropriateness of the methods, tools, and technologies used during project implementation based on results or research Evaluates the appropriateness of the methods, tools, and technologies used during project implementation but not based on results or research or with gaps in analysis Does not evaluate the appropriateness of the methods, tools, and technologies used during project implementation 6.3
Postmortem
Summary: Risk
Mitigation
[IT-420-03] Meets “Proficient” criteria and evidences keen intuition regarding risk identification in IT projects Accurately articulates risks that would need to be mitigated during implementation or operations Articulates risks that would need to be mitigated during implementation or operations but with gaps in accuracy Does not articulate risks to be mitigated 6.3
Project Status:
Objectives
[IT-420-05] Meets “Proficient” criteria and evidences keen insight into success measurement Evaluates the implementation process to the extent to which project objectives were or would be met Evaluates the implementation process but not to the extent to which project objectives were or would be met Does not evaluate the implementation process 6.3
Project Status: Issues
[IT-420-03] Meets “Proficient” criteria and evidences keen insight into the relationship between risks, implementation issues, and success Accurately identifies any project objectives that were not fulfilled and explains what risk caused the issue Identifies any project objectives that were not fulfilled and explains what risk caused the issue with gaps in accuracy or detail Does not identify any project objectives that were not fulfilled or explain associated risks 6.3
Project Status:
Alternative/
Recommendations
[IT-420-02] Meets “Proficient” criteria and evidences an intuitive understanding of iterative project processes and best practices in implementation Recommends reasonable
alternatives or additions to address issues that developed during implementation Recommends alternatives or additions that would not reasonably address issues that developed during implementation Does not recommend
alternatives or additions 6.4
Project Status:
Communication
[IT-420-03] Meets “Proficient” criteria and evidences professional and concise articulation Communicates the overall project status clearly and accurately to ensure stakeholders have a realistic view Communicates the overall project status to stakeholders but with gaps in accuracy or clarity that could prevent a realistic stakeholder view of project status Does not communicate the overall project status to stakeholders 6.3
Project Closure:
Future
Enhancements
[IT-420-02] Meets “Proficient” criteria and evidences keen insight into longterm benefits of design and implementation of project Recommends reasonable future enhancements for the design/system to improve decision making or provide additional opportunities for stakeholders Recommends future enhancements for the design/system but would not reasonably improve decision making or provide additional opportunities for stakeholders Does not recommend future enhancements for the design/system 6.4
Project Closure:
Implementation
Support
[IT-420-05] Meets “Proficient” criteria and evidences keen insight into organizational and operation needs to inform decision making or gain support during transition phases Crafts an implementation support plan that incorporates change management and support strategies that would reasonably ensure successful transition for stakeholders Crafts an implementation support plan that does not incorporate change management and support strategies or that would not reasonably ensure successful transition for stakeholders Does not craft an
implementation support plan 6.3
Project Closure:
Maintenance Plan
[IT-420-05] Meets “Proficient” criteria and evidences keen insight into maintenance needs of system in its environment Develops a logical and appropriate maintenance plan for the project to ensure health and sustainability of the system Develops a maintenance plan for the project to ensure health and sustainability of the system, but the plan is not entirely logical or appropriate for the system Does not develop a maintenance plan for the project to ensure health and sustainability of the system 6.3
Project Closure:
Appendix
[IT-420-04] Meets “Proficient” criteria and submission is exceptionally well organized, documented, or professionally crafted Packages the implemented or planned implementation with all relevant and necessary deliverables to provide clear evidence and support of process Packages the implemented or planned implementation with gaps in detail or organization of relevant and necessary deliverables that could prevent clear evidence and support of process Does not package the implementation or planned implementation with relevant and necessary deliverables evidencing and supporting the process 6.3
Articulation of
Response
Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy-to-read format 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 that negatively impact readability and articulation of main ideas Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas 5
Earned Total 100%

                                                                                Place Order