Term Project - Project Proposal Notes | MIS 322, Study notes of Information Systems Analysis and Design

Download Term Project - Project Proposal Notes | MIS 322 and more Study notes Information Systems Analysis and Design in PDF only on Docsity! [DRAFT UNTIL OFFICIALLY ASSIGNED] Deliverable 2 MIS 322 – Term Project – Project Proposal Notes Be sure to read the project requirements to ensure your proposal is complete. Note: The front of the deliverable (either the table of contents or the checklist or both) should indicate which teammates were responsible for which parts of the deliverable. Please indicate both which person or people as well as what percentage of that part they completed. Table of Contents  MS Word has a feature that allows you to automatically generate a table of contents. If you chose not to use this feature you should develop a table of contents that would be similar.  Be sure subject headings in the table of contents match subject headings in the document.  Number all pages (including pages with figures) or the table of contents becomes relatively useless.  The table of contents should include subject headings and page numbers. Use subheadings were appropriate. Consider columns for heading and page number and dot leaders between subject headings and page numbers. For example Table of Contents Topic Page Check List............................................................................................................................1 Executive Summary.............................................................................................................2 System Justification.............................................................................................................3 Supporting Documents System Service Request...............................................................................................4 Baseline Project Plan...................................................................................................5 Checklist You are required to turn in a checklist with each deliverable to make sure that what was requested was provided. If you are not providing something that was requested, make sure to note that it was omitted purposefully and why. Failure to provide any part of what was requested will result in a check- unless you explicitly state why it was omitted and why that was appropriate. Explain how you met each key point of the deliverable requirement with a checklist that shows that point by point (in reasonable detail). I would also put associated page numbers and heading names in your checklist responses to allow me to find how you did these things in a way that makes it easier for your “supervisor” or “client” to see that you met their requirements. Remember, you are selling your solutions to a supervisor or client. A solution addresses their list of needs. It is your job to see that they are at ease that their needs will be addressed by your deliverable. You don’t want to “bury the headline” and make it hard for them to see where your solutions are. This checklist summary will give a quick and easy way to make them comfortable in the front end before they look into your document. Remember, that while I will be taking a bit more time to grade your work than a client may take to review your sales document, it is because I am more committed to your 1 team than a client would be in a competitive bidding process. In the real world, if it is not clear that your bid addresses each of the concerns of the stakeholder, they are just as likely as not to throw out your bid and only select from the subset that is clear. Executive summary The executive summary is the abstract for the deliverable. Mangers should be able to read the executive summary and have a good high-level understanding of the project. Details of ideas presented in the executive overview are presented in the body of deliverable.  Introduction and background statement – Who are you, why are you delivering this document?  Brief project description (expanded upon in the narrative description) How or why did the project come about – why was the project selected? (Note: a project description is a quick overview. The baseline project plan is the details.)  Problems statement – what is the nature of the business problem/opportunity  Summary of goals and objectives – what is the project trying to accomplish?  What is the timeline established for the project? What is the current status of the project? What has been done in the period between this deliverable and previous deliverables? What challenges have occurred? How have you addressed these challenges? What resources are necessary to continue work on the project?  Contents statement – what is included in this deliverable. System Justification  Narrative description of the project – org background, specific description of the problems, details process step described in narrative.  Sell, sell, sell –  Have you provided compelling evidence that will convince management to proceed with the project?  Could management make a solid decision to move forward on the project based on your feasibility study? Why/Why not?  In developing your Cost/Benefit analysis, recognize your projects are not big $$$, but there are still clear costs and benefits. Use real numbers whenever possible. Supporting Documents  System Service Request – you should have a document signed by your client that outlines the nature of the project you will build over the course of the semester.  Baseline Project Plan –Why are you including a Statement Baseline Project Plan? Why is this a valuable document to include? Is there any information presented in this document that needs an additional explanation? (Note: a project description is a quick overview. The baseline project plan is the details.)  Team Organization and Role description should be presented in the context of a System Service Request and Baseline Project Plan to show how the group will delegate roles and responsibilities specifically as related to the goals and objectives of the project.  How will the project be managed – how will tasks be assigned? How will time be allocated? What will you do to assure the client that the project will stay on schedule? Be clear, thorough and complete in developing Pert/Gantt charts. System Resources  Recognize this should not be a three month project and then gone – take long range look at what will be required (even – and especially – after you are gone to maintain and upgrade the system. 2