Grading Rubric

Gradin" rel="nofollow">ing Rubric Course: IT299 Unit: 8 Poin" rel="nofollow">ints: 50 Copyright Kaplan University Assignment 8 Outcomes addressed in" rel="nofollow">in this Assignment: Unit Outcomes:  Complete project tasks.  Main" rel="nofollow">intain" rel="nofollow">in the correct updates of detail in" rel="nofollow">in a WBS/Schedule.  Respond appropriately to change requests.  Update project task documentation.  Research technical areas for possible project enhancement items and refin" rel="nofollow">inements.  Create a Change Request document. Course Outcomes: IT299-1: Technical Skills: Use technical skills and methods to solve problems. IT299-3: Application: Construct Information technology solutions. Note – Very Important – Product versus Project - Throughout your Assignments in" rel="nofollow">in this course it is expected that you will be simultaneously workin" rel="nofollow">ing on your actual product. The technological solution needs to be explored, in" rel="nofollow">investigated, detailed, and prototyped. There are no deliverables for the actual product until Units 7 and 9. However, product documents and results are required to be submitted in" rel="nofollow">in Unit 9 and will be completed as the product is developed on a weekly basis. Project Management (PM) documents will be created and updated on an ongoin" rel="nofollow">ing basis and will form all of the Assignments in" rel="nofollow">in the course. All these PM documents will be assembled in" rel="nofollow">into an archive and submitted as a .zip file for the Unit 10 Assignment. Your Fin" rel="nofollow">inal Product needs to be complete and delivered at the end of Unit 9. You will zip up all files related to your product. And deliver them to the Unit 9 Dropbox by the Unit 9 deadlin" rel="nofollow">ine. Programmin" rel="nofollow">ing and website products should be deployed to a Web Application Server so that the professor may test functionality. All related code files will need to be in" rel="nofollow">included in" rel="nofollow">in the fin" rel="nofollow">inal product .zip file. All design documents (for all product types) will have refin" rel="nofollow">ined and professional level formats and presentation. You will need to in" rel="nofollow">include a table of contents document in" rel="nofollow">in the .zip file in" rel="nofollow">indicatin" rel="nofollow">ing the name of the document and type of document for all items in" rel="nofollow">in your .zip file. Your in" rel="nofollow">investigations in" rel="nofollow">into how to create your product/solution will in" rel="nofollow">inform your project management activities. PM work cannot be done in" rel="nofollow">in isolation. The product and the project exist and support each other in" rel="nofollow">in a simultaneous ongoin" rel="nofollow">ing process. Your Fin" rel="nofollow">inal Project Management Documentation Archive will be delivered in" rel="nofollow">in Unit 10. The project management plannin" rel="nofollow">ing activities and documents that form your deliverables for Units 2 through 9 are only part of the solution. They are there to support your actual objective of product creation. They will be delivered for each Assignment and as a PM Archive in" rel="nofollow">in Unit 10. Assignment Gradin" rel="nofollow">ing Rubric Course: IT299 Unit: 8 Poin" rel="nofollow">ints: 50 Copyright Kaplan University Assignment Instructions Project – Execution and Communications In this Assignment you will create/update a Project Task Trackin" rel="nofollow">ing document and contin" rel="nofollow">inue to develop your Fin" rel="nofollow">inal Project. You will also create a Change Request document for any change (your selection) to be made to your product. The actual change does not need to be made to your Fin" rel="nofollow">inal Project unless you choose to implement it. The approved change request will require updates to other project documents, which are also part of your tasks for this Assignment. Attach the change request and proof of update to your completed WBS – Schedule Task Trackin" rel="nofollow">ing spreadsheet. Zip both documents together for Dropbox submission. Important note: Do Research. Search these terms: “Check Lists”, “Project Guides”, and “Characteristics of a successful project” for your project type. Usin" rel="nofollow">ing the in" rel="nofollow">information you have obtain" rel="nofollow">ined from your research, and from extendin" rel="nofollow">ing the scenario in" rel="nofollow">in an imagin" rel="nofollow">inative direction to add detail, you will develop your project task list as you work on the project. Your research this week should be focused on identifyin" rel="nofollow">ing specific technical areas and tasks related to your project that you may not have previously identified as bein" rel="nofollow">ing important. These tasks should in" rel="nofollow">involve new, and / or extended learnin" rel="nofollow">ing in" rel="nofollow">in the subject area of you project type. 1. Update your WBS/Schedule to in" rel="nofollow">include any newly identified tasks and completed tasks, Highlight past due tasks. Use and extend your pre-existin" rel="nofollow">ing WBS/Schedule. See below for some detail on the meanin" rel="nofollow">ing and in" rel="nofollow">information contain" rel="nofollow">ined within" rel="nofollow">in these documents. You will have already completed a detailed WBS/Schedule. Now, you will look to add detail to it based on what you are actually doin" rel="nofollow">ing. When the Assignment is complete you will really have a sin" rel="nofollow">ingle document WBS/Schedule/Task Trackin" rel="nofollow">ing document. The updated document will show the tasks have already been completed and will in" rel="nofollow">include new tasks that were not in" rel="nofollow">in your origin" rel="nofollow">inal WBS. Did you miss detail in" rel="nofollow">in your origin" rel="nofollow">inal task breakdown? If so, now is the time to add those tasks. If a task is already complete, in" rel="nofollow">indicate the date the task was completed. Your updated and more detailed WBS/Schedule/Project Task Trackin" rel="nofollow">ing will in" rel="nofollow">include the new tasks, completed tasks, tasks that should have been completed, and provide an in" rel="nofollow">indication of the status. Your boss wants to be able to immediately identify new tasks added to the spreadsheet sin" rel="nofollow">ince your last update in" rel="nofollow">in Unit 6.Indicate new tasks added sin" rel="nofollow">ince the last update with the color Purple. Statuses should be used (complete/in" rel="nofollow">in process %/not started/at issue). Include data (add these columns to the spreadsheet): status, date completed, planned start date, actual start date, reason description for tasks that are behin" rel="nofollow">ind schedule or at issue. Highlight problem issues with Red font color and Green font color for successfully and 100% complete tasks. You will need to modify the spreadsheet to in" rel="nofollow">include status and completion dates as well as explanatory text area. Assignment Gradin" rel="nofollow">ing Rubric Course: IT299 Unit: 8 Poin" rel="nofollow">ints: 50 Copyright Kaplan University 2. Create a Project Change Request Template document. Select a reasonable and realistic change for your project. The change may have been precipitated from product or project reviews with stakeholders and may come from any stakeholder. Detail the change and accept the request. Update the project documents, WBS/Charter/Scope Statement and any other related documents to reflect the in" rel="nofollow">inclusion of the change in" rel="nofollow">into the project. Note in" rel="nofollow">in the changed documents the special addition of the change, the source (Change Request Document name), and date of the change. Proof of Update - Copy and paste the changes (document snippets) made to other documents to a new page of the completed change request form, so that your professor can see that you made the appropriate changes. Note – You do not need to build or implement the change in" rel="nofollow">into your fin" rel="nofollow">inal product, unless you choose to do so. Attach your updated and more detailed WBS/Schedule/Task Trackin" rel="nofollow">ing document, and Project Change Request with Proof of Update. Zip both for Dropbox submission. Directions for Submittin" rel="nofollow">ing Your Assignment: Compose your Assignment by providin" rel="nofollow">ing a .zip file with a Microsoft Word document and Excel Spreadsheet and save it as IT299_YourName_Unit_8.doc and submit it to the Dropbox for this unit. Written Assignment Requirements Answers or website materials contain" rel="nofollow">in sufficient in" rel="nofollow">information to adequately answer the questions and contain" rel="nofollow">in no spellin" rel="nofollow">ing, grammar, or APA errors. Poin" rel="nofollow">ints deducted from grade for each writin" rel="nofollow">ing, spellin" rel="nofollow">ing, or grammar error are at your in" rel="nofollow">instructor’s discretion. Please be sure to download the file “Writin" rel="nofollow">ing Center Resources” from Doc Sharin" rel="nofollow">ing to assist you with meetin" rel="nofollow">ing APA expectations for written Assignments. Review the gradin" rel="nofollow">ing rubric below before begin" rel="nofollow">innin" rel="nofollow">ing this activity. Assignment 8 gradin" rel="nofollow">ing rubric = 50 poin" rel="nofollow">ints Assignment Requirements Poin" rel="nofollow">ints Possible Poin" rel="nofollow">ints Earned 1. Updated the WBS to in" rel="nofollow">include new tasks. a. New tasks were added based on research. 0–10 b. All tasks were updated with status, descriptions and date as appropriate. 0–10 c. Tasks are color coded for easy review. 0–5 2. Created a Change Request Document and properly reflected the change through all Assignment Gradin" rel="nofollow">ing Rubric Course: IT299 Unit: 8 Poin" rel="nofollow">ints: 50 Copyright Kaplan University project documents a. Clear, complete, and professional content. 0–5 b. Provides all in" rel="nofollow">information necessary to document the change request. 0–10 c. Provide Proof of update of other project documents. 0–10 Total (Sum of all poin" rel="nofollow">ints) 0–50 Less - poin" rel="nofollow">ints deducted for spellin" rel="nofollow">ing, grammar, and APA errors. Plagiarism is totally unacceptable. Adjusted Total Poin" rel="nofollow">ints