Reference no: EM131497678

Assignment 1 - Project Initiation

Task - Various tasks as outlined below after the case background.

Case Background

As the project manager you are required to present an initial project report to the project sponsor that shows how you propose to implement this project. As the project manager you may make any assumptions you think are necessary.

Case study - Social Media Research Centre

During a meeting with his boss (David Wright), Bruce has been asked to establish a researcher centre. The research centre, which will commence operations in February 2018 first as an informal research group, should be established by June 2017. Alex's decision to proceed with this major project is spurred by the fact that an associated organizational centre, which researches in a closely related area, has recently ceased operations. There is also a tremendous pressure from David's senior executives to produce high quality research that is focused in nature. In fact one of David's senior executives' comments was that David's Unit does not have a clear identity when it comes to its scholarly research output compared to the one in Australian National University. After several meetings with subject matter experts (consultants) and a rigorous analysis of the current trends in research in the area of information technology it has been decided that the most appropriate research area for the proposed research centre to focus on is social media. Fortunately several of David's Unit staff are active researchers in this area. What made this direction even more attractive is that demand from Master and Doctoral students has been largely for programs in this area. David's Unit also enjoys a very good relationship with an international expert Craig Bamworth in the social media area who has kindly agreed to offer his expertise to Bruce (the program manager).

One of the projects within the Social Media Research Centre larger project that Bruce has identified as important is the development of a web application for the proposed centre.

This application would include an internet website and section for members on the intranet. Bruce has appointed. You as the manager of this project commencing work on 1 April 2017. Bruce's team has conducted the feasibility study and financial analysis to confirm that project must go ahead and must commence as you join your role.

You must assist Bruce in preparing the project charter that need to be submitted within first week of May 2017 via a kick-off meeting to be held with all major stakeholders presenting and discussing the charter before they all signoff and approve charter.

This website should contain information about the major research projects, list of supervisors, Masters and PhD student projects, publications (conference and journal papers), and project reports. The application manager Sonia Reed should update all these details on the website using the intranet login. Members can also update their project details via their member account. It has also been identified by Bruce that displaying the information, program, recorded presentations and reports/publications of the events held in the area of social media research will help in promoting the centre. Sonia would collect this information from the events manager and update the information on the web application before, during and after the events as needed.

Your team must include appropriate experts to assess the application, network and database software and hardware needs to support this project.

Your manager, Bruce has given you guidance that the project needs to be completed within 8 months and that costs should be minimised wherever possible with given budget of AUD 50000.00

Task 1: Prepare Project Charter as per below template -

Basic details Including: Title of the project, Name and email of the Project Manager (yourself), Duration of the project, and High level budget

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.

(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 for the project as a whole
• 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

• Complete list of stakeholders including the sponsor, PM, executive members and few important members that are required to contribute to high level decisions

Lessons Learned

• Identification of pitfalls to be avoided, based on the past projects and experience
• Evidence of thought as to what can and cannot affect the project in terms of how the project will run

Charter Sign off

• This section should include the stakeholders signing off the charter for commitment.
• Some key stakeholders must comment make comments

Task 2: Prepare Communications Plan as per the template given -

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.

Identification of stakeholders - The "who" in the project that requires information, (i.e. team members, project sponsor, class professor, etc.) and also the responsible parties to receive and/or communicate information.

Information to be shared - The "what" in terms of project information communication. Describes types of information that the team uses to communicate amongst its own project members, and also to the sponsor

Frequency of information exchange - The "when" describes how often communications will be held (i.e. daily, weekly, monthly, as needed, etc.)

Location of information exchange - The "where" states the location of the meeting or other interactions

Purpose of communication - The "why" description assures that communications are held effectively.

Mechanism for communication - The "how" describes the media for communication (i.e. physical meeting, email, phone, message group, etc.)

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.

Rationale -

This assessment task covers first four topics and has been designed to ensure that you are engaging with the subject content on a regular basis. More specifically it seeks to assess your ability to:

• Identify the responsibilities of a Project manager when participating in a real world project;
• Define the role of management in projects, particularly from the view point of the practitioner as a member of the project team;
• Apply project management skills, methods, techniques and tools to a real world problem typical of a project manager;
• Explain areas of knowledge relevant to project management; and
• Discuss the many problems facing the project manager and to note the "best practices" being utilised in order to produce effective, efficient and quality projects on time and within budget

Assignment 2 -

Task

This assignment follows from the case study used in Assessment 1. For the same case study, complete the following tasks by creating the following:

1. WBS first using indented format.

2. Gantt chart-Take the WBS you have already developed. Define all of the activities that will be necessary to create each deliverable in your WBS. Create a schedule for your project. First create the schedule by hand using Post-it Notes, and then put the information into MS Project. Take screenshots of the schedule to be pasted in your word document that you are submitting. Be sure to include all of the summary rows (including the first row for the project title) and any key milestones. Make sure the critical path is easy to see.

3. Create a time-phased budget for your example project using bottom-up estimating. To the extent your sponsor will supply rates for workers, use those. Approximate rates for ones you cannot get. Ask your sponsor how they treat indirect costs. Be sure to include direct labour costs for you and your team mates and add 20% for fringe. State all assumptions and constraints you have used when creating your budget. State how confident you are in your estimates and what would make you more confident. Give examples of known knowns and known unknowns on your project. Tell how you have budgeted for both of them plus how you have budgeted for unknown unknowns.

4. Create a risk register (4 risks- 3 negative and 1 positive risk) for your example project.

5. Quality Management Plan. It should include:

A short statement that reflects your team's philosophy or objective for ensuring that you deliver a quality system to your client.

Develop and describe 3 quality issues related to this project that your project team could implement to ensure quality

6. Closure checklist and project evaluation.

Develop a closure checklist that the project team will use to ensure that the project has been closed properly.

Develop a project evaluation -outline and discuss how your project's MOV will be evaluated.

Rationale -

This assessment task covers topics 5 to 9 and has been designed to ensure that you are engaging with the subject content on a regular basis. More specifically it seeks to assess your ability to:

• demonstrate how a practicing project manager actually applies project management skills,
• methods, techniques and tools ;
• use an industry standard project management software tool (Microsoft Project);
• apply project management skills, methods, techniques and tools to a real world problem typical of a project manager;

Requirements -

Students are required to submit the range of documents describing their proposed project solution for the above tasks.

Work Breakdown Structure (WBS)

• The first major section (1.0) should be project management and include the various project management deliverables such as charter, WBS, schedule, progress reports, etc.
• Deliverables should match those in the charter.
• Each item on the WBS should have a unique name. If there is possible confusion between two items add an extra adjective to differentiate them. For example, two items could be "first draft report" and "second draft report."
• Each line should be numbered with major sections being 1.0 then 2.0, etc.
• Each major section should be broken down into between three and twelve subsidiary sections. If further breakdown is needed, more levels should be used.
• All items on WBS are deliverables oriented (they are the "whats" of the project). Activities are defined as an outgrowth of the WBS and will appear in the schedule.
• The WBS can be submitted in free-form, org-chart, or indented-outline format.
• The WBS should appear to be complete with all interim and ending deliverables included.

Schedule / Gantt chart

• The schedule should appear to be complete given the charter and WBS.
• The schedule should appear to be reasonable without requiring heroics to complete on time.
• Include WBS column to left of task name column.
• Include overall project name as top row.
• Have all summaries stated in noun only format (or adjective noun - but on present tense verbs).
• Have all tasks (activities) stated in present tense verb-adjective-noun format.
• Have all milestones stated in noun and past tense verb format.
• All tasks should have dependencies shown - no loose ends.
• Display Gantt portion of schedule as large as possible.
• Show critical path in red (or distinctive hash marks if printer is only black).
• Show arrows with dependencies.
• Include no more than 40 lines per page - ensure it is large enough to read easily.
• Include no more pages than necessary so there is little need to align multiple pages for reading unless it is a large schedule.