Project Start Date: as given in the case study Project End Date: < duration is 8 months, calculate the end date> Budget Information: Project Manager: < Name>, < Email>, <Telephone No> Project Objectives • Clear, concise reasoning for why the project is being performed • Clear, concise definition of what the project’s activities will entail ( high level scope) • Brief description of primary deliverable(s) • Clear description of the project’s benefits to the organisation • Recognition and description of any limits that the project will not cover and address MOV - Measurable Organisational Value (This is the goal of the project and is utilised to define the value that your team project will bring to your client) Identify the desired area of impact - Rank the following areas in terms of importance: Strategy / Customer / Financial / Operational / Social With reference to your project, identify one or two of the following types of value: • Better - is improving quality important to your client? • Faster - does your client want to increase efficiency? • Cheaper - is cutting costs important? • Do more - does your client want to continue its growth? Develop an appropriate metric - this sets the target and expectation of all the stakeholders. It is important to determine a quantitative target that needs to be expressed as a metric in terms of an increase or decrease of money. ( 5 Bullet Points) (Note: the MOV should inform everyone what the project will achieve, not how it will be achieved. It should also focus on the organisation, not on the technology that will be used to build or support the information system). Acceptance Criteria • Identification of specific factors against which the project can be compared to determine success/failure • Identification of specific deliverables not only for class, but for the project as a whole • Agency-specific deliverables • Inclusion of due dates for the deliverables • Clear identification of milestone and milestone exit points • Factors should include a specific metrical comparison Assumptions and Constraints • Any assumptions made during the course of the project • List of constraints that entail the limitations that are required to be addressed Stakeholder List Stakeholder No Name and Signature Role and Responsibility Position Contact Information 1 2 3 4 5 6 7 Lessons Learned • Identification of pitfalls to be avoided, based on the student’s past experience • Evidence of thought as to what can and cannot affect the project in terms of how the project will run Charter Signoff • This section should include the stakeholders signing off the charter for commitment. • Some key stakeholders must comment make comments Communication Plan Template Plan purpose – A brief description of why and how the plan was developed, and an overview of the overall team communication philosophy. Also states types of communications planned, for lateral, downward, and upward communication. Change management – Description on how the team will handle changes in the project, whether it is in terms of project scope, schedule, or resources. This includes how the team plans to communicate changes as well as how the team plans to make decisions about changes. Meeting agenda – Gives a brief overview of what the team plans to accomplish in each of its meetings, how it documents goals and objectives for meetings, and defines and assigns actions for the team to accomplish project objectives. Stakeholder Information to be shared Frequency of information exchange Location of information exchange Purpose of communication Mechanism for communication Who What When Where Why How </h3> <div id="footer"></div></html>