HCRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 1 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Task Team Project Management Plan Due Date Week 11 – Friday, 5:00 pm – Team Project Management Plan Worth 20% (80 marks) Course Objectives This assessment task relates to the following course objectives:  Identify traditional and agile approaches and lifecycles for managing information technology projects;  Employ a systems thinking approach to identify critical roles and stakeholders in information technology projects;  Explain the basic components of a project management plan and its importance in improving the success of information technology projects;  Adopt a project management framework to write a project management plan, for a simulated real world contemporary information technology project;  Apply the process groups model to manage information technology projects of various complexities and scales;  Demonstrate decision-making processes to solve a range of information technology project issues;  Classify and discuss current issues in information technology project management;  Value the importance of effective communication to solve problems on information technology projects; and  Value the significance of software quality in it projects.CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 2 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Overview As stated by Schwalbe (2014) a project management plan (PMP) is a document used to coordinate all project planning documents and helps to guide a project's execution and control. She also states that a good PMP is vital to the coordination and integration of information across project management knowledge areas and across the organisation. In this assignment, you will work in teams of 2-3 people to produce a PMP, a description of updates to the PMP and related documents and a record of your experiences working in the team. The teams will be assigned by your lecturer and will be based on your tutorial/laboratory classes. There will be time allocated in the tutorial/laboratory to work on this assignment. One team member is to be elected the project manager for the duration of the project. Teams are expected to meet regularly – at least once a week – and prepare a PMP based on the IT project case study on page 7. They are then expected to provide descriptions of changes to that PMP and related deliverables based on the sequence of events described in the case study. Teams should use their own initiative regarding the scheduling of all deliverables. Teams will NOT be required to produce 'product related deliverables' as part of this assignment. The focus is primarily on 'project management related deliverables'. However if an event would trigger a change to the product deliverables, it may be of assistance to the reader if you include information about that change. Finally over the course of the assignment, individuals are expected to record information about team meetings, their work and contributions and the contributions of others as well as reflect on their learning about project management through the completion of the assignment. .CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 3 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Requirements Deliverables for this assessment are divided into three areas, a) Team PMP Deliverables; b) Team Project Update Descriptions Report; and c) Individual Report Deliverables. Following are detailed requirements of each. Team PMP Deliverables: It is recommended teams use the structure as suggested by Schwalbe (2014) as a guide for preparing and creating their PMP. PMP section headings include:  Introduction  Organisation  Management and Technical approaches  Work to Perform  Schedule  Budget It is recommended that teams understand the inputs to the PMP and include reference to ancillary plans and deliverables from other knowledge areas (see Schwalbe (2014)). You may use Microsoft Project or other tools to plan the project and include screen shots in your report. A quality team PMP will demonstrate a synthesis of plan content, templates and ideas acquired from project management professionals and academic authors with details from the case study provided. Team Project Update Descriptions Report Each team needs to produce a report describing what needs to be done at each of the time points identified in the case study:  Two weeks after project commencement;  One month after project commencement;  Four and a half months after project commencement; and  Six months after project commencement The report may be included as an Addendum to the baseline PMP and is to include for each time point:  Description of the situation;  Description of response to the situation;  Summary of actions to be undertaken including: o Processes followed/executed; o Activities completed; o Deliverables altered/produced;CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 4 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Individual Report Deliverables: Each student should submit a separate, individual report of approximately 800–1000 words including the following sections:  Statement of Contribution This statement should provide: o a clear description of all roles and responsibilities taken on by the student; o a table describing all project and assignment team deliverables created/altered by the student. The table should include: o Deliverable Name; o Description; o Purpose; and o Estimate (elapsed and expended) of how long each took to complete.  Weekly Assignment Status Reports Individual weekly status reports should be completed by each student, and submitted to team project managers' in team meetings. Copies of each student's weekly status reports should also be included with their individual report. A Status Report - ITECH2250_Weekly_Assignment3_status_report – accompanies this assignment document on Moodle.  Peer Review of Assignment A confidential statement estimating each team member's: o contribution percentage (all team member values should total to 100%); o justification of contribution percentage given; o meetings attended; o weekly status reports submitted; o any issues and how they were dealt with.  Project Management Lessons Learned in Assignment A reflective statement documenting project management lessons learned whilst working on the assignment, including technical and non-technical lessons. These lessons should include those aspects which worked particularly well, and also those which were problematic. Lessons Learned template - ITECH2250_PM_lessons_learned_in_Assignment3_report.doc – accompanies this assignment document on Moodle.CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 5 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Academic Presentation: The Team PMP and the Team Project Update Descriptions Report should both be presented as business reports, in accordance with the suggested layouts (see pages 3 and 4 above), and adhere to academic writing presentation standards and be consistent with Federations University's referencing requirements, see General Guide for Referencing. For help on report writing, see Federation University's General Guide to Writing and Study Skills, in particular pp. 33 – 43 on Reports or Murdoch University's Guide to Business Report Writing Submission: Team PMP's should be submitted in electronic format by the team project manager via Moodle (one per team). Individual reports should be submitted by each student in electronic format via Moodle (a separate link will be provided for the individual report). Please refer to the "Course Description" for information regarding late assignments, extensions, special consideration, and plagiarism. A reminder all academic regulations can be accessed via the university's website, see: http://federation.edu.au/staff/governance/legal/feduni-legislationCRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 6 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques Assessment Feedback Student: Team: Criteria Marking Scale Individual Mark Poor Excellent 0 .................... 5 Team PMP – introduction 0 – organisation 0 – management and technical processes 0 – work to be done 0 – schedule 0 – budget 0 Team Project Update Descriptions Report – time point 1 0 time point 2 0 time point 3 0 time point 4 0 Team Total [50 marks] 0.0 Individual Percentage for Team Total (Derived from detail below) Individual – statement of contribution 0 – weekly status reports (weeks 7-11) 0 – peer review 0 – lessons learned 0 – academic presentation – attendance at meetings 0 0 Individual Total [30 marks] 0.0 Total Overall Mark [80 marks] 0.0 Total Worth [20%] 0.0 Comments Marked by DateCRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 7 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques CASE STUDY—THE WOWS PROJECT Refer to the WOWS project specifications in Assignment 1. WOWS executives believe in hiring highly talented and motivated individuals who can work well on self-managed teams. Smart and Bright formed a search committee to find the best candidate for managing the project. After reviewing many strong candidates, they decided to hire you to manage this critical project. You have previously worked for a system development firm and had successfully implemented several multimedia application development projects in large organizations. Since this was a high priority project that should be completed in 6 months, they felt it was appropriate to pay a premium for your contract at $140 p/hr for 2 d/wk. But a lot was at stake, therefore, Smart and Bright agreed to be joint project sponsors, and they also hand-picked Lance Sweets to be the main internal IT liaison. They would let you form the rest of the project team. You proposed that you would like to use some form of hybrid SCRUM project management methodology, particularly by incorporating SCRUM in the software development. However, after meeting with Smart, Bright and Sweets, you all agree that both the goal and solution are clear (since they are leveraging their existing expertise). You also agree that you will be able to clearly establish the requirements and that WOWS executives knows the technology well. For all these reasons you decide to use a more traditional predictive project management methodology including a traditional waterfall model for the SDLC. You predict that they will need to provide new hardware for the development team and upgrade the test bed for system and acceptance testing. You will also need to eventually a team of 6 analyst programmers to work on the system. Two will be hired for the Requirements/Analysis and Design SLDC phases and the remaining four will be hired for the remainder of the project. The programmers will spend the equivalent of half a day a week on project management related activities and the remaining four and a half days on development. They will be paid at a rate of $80 per hour. To use the existing knowledge of the organization, you hope to second some existing programmers to the project and use some of the hired programmers to backfill the vacated positions. The existing programmers may be charged at a higher rate than the $80 per hour. You also hope to use two existing employees in some capacity to help with Acceptance Testing of the apps – at this stage you budget for three days per week for seven weeks at $80 per hour. For all team members excluding the sponsors and externally hired consultants, an indirect cost rate of 25% is applied. You will also need to access a machine learning scientist and network security specialist consultant. Their pay rates are negotiable.CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 8 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques After looking at the Business Case and creating a Stakeholder Register, you have completed the Project Charter and hold a Project Kick-Off Meeting. The estimated project budget on the Project Charter is listed at $700,000 (including reserves) and states that you will have the final versions released to market 6 months after commencing the project. From your knowledge of previous projects and PMBOK you think it best to understand the project in a traditional project management sense i.e. as a series of four sequential phases: • Starting • Organizing and preparing • Carrying out • Finishing. You realize you have completed the required processes for the starting phase and now must focus on the organizing and preparing phase of this project. A key process group in this phase is the planning process group. You must understand and produce the appropriate outputs from the core and facilitating knowledge areas relevant to the planning process of this phase and integrate these into the Project Management Plan (PMP). You must then perform progressive elaboration of the PMP over the life of the project and particularly with respect to the situations that follow. Based on the project specifications, you should make assumption wherever it is necessary. …Two weeks later… You are having several challenges on this project including a key staff having to take two weeks paternity leave and a possible change to the original plan. After a consultation with a WGCI specialist and a machine learning scientist, WOWS executives would like to see some flexible/extensible functionalities in the system as shown in the following • Linking Multiple Events to a Single Event: Currently, an event can be linked to only one other event (which leads to the formation of chains). There may be a need for a single event object to be linked to more than one event objects, forming branches to the main chain. • Chronological Aligning of Multiple Chains: It will be visually very helpful to align multiple chains chronologically. Additionally, it will be easier, with such a representation, to analyze a patient's condition and possibly relate occurrences of events across multiple chains. • Chronological Ordering of Patient Chains: Order patient chains by diagnosis start date such that the oldest chain displays topmost on the website.CRICOS Provider No. 00103D itech2250_a3_s2_2016_pmp development.docx Page 9 of 9 Assignment 3 ITECH 2250 IT Project Management Techniques As the result, they have set aside a $300,000 contingency fund for the possible extension. The flexible functionality should only be done if the originally planned system is done within time and budget, and it should be completed within two months. …One month after project commencement… A memo that the project sponsors and you sent had mixed reviews, but the monthly meeting was very effective in airing everyone's concerns and clearing up misconceptions. The project team realized that in addition to high-level monthly meetings, they would need to have more detailed meetings and reports to help keep the project on track. The project team was assigned a user representative. It was critical that the team develop a good list of requirements for these new apps and work towards delivering these. A new requirement to create a testing function that will allow the users to benchmark their progress is proposed as a desirable requirement by the project sponsors and you need to evaluate the effect of this out of scope request but are quite positive about being able to include it. …Four and a half months after project commencement… You have reached a significant milestone on the project; all core requirements have been constructed and are ready for system testing. You think that you need to review the quality of the testing before a scheduled quality audit. You hope to be able to continue with final development integration of noncore features and final testing (system and acceptance) before final release of the system. However, your reviewing discovers some issues and you need to resolve them. At this point, you also know that final versions are planned for release on time at the completion of the project. You therefore also resolve to measure the project progress and decide if the final versions will be released on time and on budget. …Six months after project commencement… The project has been considered a success, coming in on budget, within agreed scope and key stakeholders have been pleased with the communications and reporting process. The final versions are released to the market with great success and you close the project. The team is now considering the flexible extension.