1 Unit Name/Code ISY2004 Information Systems Project Management Assessment Type Report – Group Work Assessment Number Two Assessment Name Project Plan - Part 1 Unit Learning Outcomes Assessed ULO1:...

attached


1 Unit Name/Code ISY2004 Information Systems Project Management Assessment Type Report – Group Work Assessment Number Two Assessment Name Project Plan - Part 1 Unit Learning Outcomes Assessed ULO1: Demonstrate comprehension of the different phases of the project life cycle and design planning, costing, scheduling and controlling. ULO3: Demonstrate a working knowledge and understanding of ley project management software applications tools and techniques, including critical path analysis, and PERT and Gantt Charts. ULO5: Apply the principles and tools to monitor and evaluate IT projects. Graduate Attributes Addressed: GA1: Communication GA4: Critical Thinking & Problem Solving GA1: Communication GA2: Collaboration GA1: Communication GA2: Collaboration GA4: Critical Thinking & Problem Solving Due Date and Time Week 6, Friday, 18/12/20 5:00pm Weighting 25% 2 Assessment Description You are required to form groups of Four/Five (4/5) students and choose an IS/IT project. See Appendix 1. You need to develop the Initial Project Plan which should include the following: • Project charter, including a detailed Scope Statement, Out of scope, Goal, Objectives, a draft project “Work Breakdown Structure” (WBS) or Task List, that must also show dependencies • Stakeholder Register • Stakeholder Management Strategy (In Assessment 2, you will continue to develop the full Project Plan). Referencing and Plagiarism It is essential to use IN TEXT referencing. If you are using the exact words from a reference then you must use quotation marks. You can use Chicago Style referencing with numbers, with a listing at the end of the essay. Microsoft Word has an EndNote plugin that makes this style very easy and clear to follow. http://www.chicagomanualofstyle.org/tools_citationguide.html Alternatively, you can use the more traditional Harvard style, which is more verbose. http://www.citethisforme.com/harvard-referencing. Remember that this is a Turnitin assignment and plagiarism will be subject to severe penalties. Please refer to the AIH Academic Misconduct Policy: http://www.aih.nsw.edu.au/content/1-home/8-more-info- tabs/3-official-policies/academic-misconduct-policy.pdf DO NOT COPY AND PASTE FROM THE INTERNET OR COPY OTHER STUDENTS’ WORK! http://www.chicagomanualofstyle.org/tools_citationguide.html http://www.citethisforme.com/harvard-referencing http://www.aih.nsw.edu.au/content/1-home/8-more-info-tabs/3-official-policies/academic-misconduct-policy.pdf http://www.aih.nsw.edu.au/content/1-home/8-more-info-tabs/3-official-policies/academic-misconduct-policy.pdf 3 Detailed Submission Requirements Before submission, ensure the submitted work satisfies the following requirements: • The assignment is to be written in a report format. It must have separate sections for each of the THREE tasks • Submit as a PDF file through the Turnitin assignment submission tool on Moodle. • Include a cover sheet that has your name, subject, date, report title and WORD COUNT • The assignment should not exceed 8 pages and 2,000 words. Peer Review Forms EACH member of the group is to submit a Peer Review Form in the Moodle Assignment Submission Tool. See Appendix 2 for instructions on group member performance. Marking Criteria Assessment Criteria Fail Competent Good Excellent (50) 0-20 20-30 30-40 40 - 50 1. Project Charter, Superficial Good choice of Well-presented and Excellent choice of Goal, Objectives, Inappropriate exhibits. written. Logical and exhibits and Scope statement, choice of exhibits Consistent. precise. presentation. out of scope, / Too short or Concise and Well documented draft WBS with exceeded. relevant dependencies, Approach, Roles and Responsibilities (20) 0-8 8-12 12-16 16-20 2. Stakeholder Incorrect format Correct format and Very good format Excellent Register and incomplete. most stakeholders and all presentation and all in the case study. stakeholders details are correct. included. (30) 0-12 12 - 18 18-24 24-30 3. Stakeholder Incomplete and Reasonable All stakeholders Excellent and Management illogical. strategy to handle considered and a insightful analysis Strategy most stakeholders. good strategy presented TOTAL 100 Scaled to 25 marks 3 Appendix 1 Some examples of IS/IT projects: 1. Creating an additional net-worked lab of computers at a local private College in Sydney. 2. e-Commerce Website Development for a Company selling shoes. 3. Health Information System for patients' remote monitoring. 4. Migration to Office 365 in a Travel Agency. 5. Customising a Data Base Management System for a Real Estate Agency. You can also choose any other IS/IT project outside of this list as well; refer to the prescribed text book or other project management related sources to get ideas on which project to choose. Irrespective of the project you choose; you could incorporate some of the following tasks, if appropriate for your project. • Hire a consultant to assist with identifying a suitable System. • Recruit the project team of internal and external staff. • Trial a short list of suitable systems with input from the Project Management Champions about their major pain points. • Gain agreement with major Stakeholders on the preferred System. • Negotiate with the Vendor, with the assistance of the Purchasing Department and procure the licenses. • Implement the chosen System, and measure the Return on Investment (ROI) and degree of customer satisfaction. • Train users and IT maintenance staff across the whole organisation. Work out the project budget. The goals are to gain project approval, determine the best solution, implement the solution, monitor performance and ensure benefits realisation. 4 The project manager will act as the liaison between internal and external stakeholders. The project is expected to be completed within 8 months. CIO, John Clinton is very keen to get this project off the ground as quickly as possible. As a result, he is happy to put in a word for the nominations from the software centres. This is the first step in getting buy-in from the software centres. The Project Management Champions will then form their centre specific teams with your help. You will report to the Steering Committee on a monthly basis on the progress of the project and discuss road blocks/issues if any. APPENDIX 2 Equal Contribution of Group Members It will be assumed that all group members contribute equally and hence will receive the same mark for the group part of the assignment. You are required to complete the Peer Review Form. This can be downloaded as a Word file and submitted individually by all group members through the Moodle assignment submission tool. • If you consider that a group member has not contributed significantly, then you can nominate that person in the form. • If you do not want to list the name of that student, you should contact your lecturer directly and inform him. • Each member of the group should complete and submit a Peer Review Form. A common problem encountered with students is that some members of groups do not contribute sufficiently. This includes not attending the weekly workshop/laboratory sessions. If a member of any group is not acting in a responsible manner, please attempt to resolve the problem with the student in question in a mature, adult fashion. If such a course of action fails, it is the duty of the group to email to the lecturer so that alternative assessment arrangements can be made. If the problem is not outlined in writing to the lecturer before the end of Week 10, the group will have to live with the problem. The final decision about assessment will rest with the lecturer. In extreme cases this will involve the non-contributing student(s) undertaking all of the group assessment tasks individually. 5 Example of Team Ground Rules Our attitude and culture • We treat each other with respect. • We aim to develop personal relationships to enhance trust and open communication. • We value constructive feedback. We avoid being defensive and give constructively (positive and task-focused) • We treat all team members equally • We strive to recognize and celebrate individual and team accomplishments. • As team members, we will pitch in to help where necessary to help solve problems and catch- up on behind schedule work Team meetings • We will hold a regular weekly meetings, either in person or on the course discussion board (or other) • We will organise additional meetings if critical issues arise. • All team members are expected to attend team meetings unless they are out of town, on holidays or sick. • The team leader can cancel or reschedule a team meeting if sufficient team members are unavailable or there is insufficient subject matter to meet about. • The team leader will publish the meeting agenda 24 hours before the meeting. • Meetings will start promptly and all members are expected to be on time. • The recorder will keep an action list, and allocate each action to a team member. • Responsibilities for actions arising from meetings must be agreed to by the individual(s) Concerned. • Meeting minutes will be distributed within 24 hours after the meeting. Communication and Decision-Making • One person talks at a time; there are no side discussions • Each person is given a chance to speak their mind while at the same time respecting the group's time and the meeting timetables. We will be brief and focus on facts, not opinions. 6 • We will be open and honest about our interests and position. • We will address issues and will not accept attacks on team members as people. • We will listen, be non-judgmental and keep an open mind on issues until it is time to decide. • We accept that each team member deserves to be heard • We will seek group consensus for all important issues. • We will reach agreement and commit to explicit team objectives. • We will follow the team plan and schedule for completing tasks. • If a team member is asked to do something outside of their nominated tasks, they will inform the team leader. • When we raise an issue or a problem, we will also try to present a solution. • Team commitments shouldn't be made lightly, but we will keep those that we do. Other • We will focus sufficient time on team process and conduct process checks when one member believes we are deviating from our ground rules. NB: This ground rules example was adapted from an NPD Solutions document, viewed 20 March 2009,