Uncategorized

MIS798 Graduate Learning Outcome

MIS798
Trimester 1, 2020
Assignment Details

DUE DATE AND TIME: Part A – Week 8, 8th May 2020, 11:59PM
Part B – Week 10, 22nd May 2020, 11:59 PM
PERCENTAGE OF FINAL GRADE:
HURDLE DETAILS
50% (Part A: Group Project Plan 40%, Part B: Reflection 10%)
Team Work Plan, Week 4, 3rd April 2020, 11:59PM
*Note: Team Work Plan submission is a hurdle but not graded.

Table of Contents
Learning Outcome Details……………………………………………………………………………………………….. 2
Assessment Feedback …………………………………………………………………………………………………….. 2
Assignment Description / Requirements …………………………………………………………………………… 3
Introduction …………………………………………………………………………………………………………………………. 3
Hurdle Requirement – Team Work Plan (ungraded)……………………………………………………………………. 3
PART A – Group Project Plan…………………………………………………………………………………………………… 3
Possible components for the project plan ……………………………………………………………………………4
1. Proposal and feasibility…………………………………………………………………………………………………4
2. Project organisation……………………………………………………………………………………………………..4
3. Management issues & effectiveness ……………………………………………………………………………….4
4. Plan (schedule) ……………………………………………………………………………………………………………4
5. Resource and cost plan…………………………………………………………………………………………………5
6. Project risk assessment…………………………………………………………………………………………………5
7. Contracts & quality management plan …………………………………………………………………………….5
Part A deliverables – Project plan ………………………………………………………………………………………5
Notes…………………………………………………………………………………………………………………………….6
PART B – Reflection………………………………………………………………………………………………………………… 6
Your reflection………………………………………………………………………………………………………………..7
Essential background – reflective writing ……………………………………………………………………………..7
Part B deliverables (4-5 minute reflection) …………………………………………………………………………..7
Submission instructions ………………………………………………………………………………………………….. 8
Hurdle …………………………………………………………………………………………………………………………………. 8
Part A Group Project Plan ………………………………………………………………………………………………………. 8
Part B Reflection……………………………………………………………………………………………………………………. 8
Notes …………………………………………………………………………………………………………………………… 8
Page 2 of 9
Learning Outcome Details

Unit Learning Outcome (ULO) Graduate Learning Outcome
(GLO)
ULO 1: Identify and apply the conceptual skills to
successfully solve complex project management
problems;
GLO 1: Discipline-specific
knowledge and capabilities
GLO5: Problem Solving
ULO 2: Explain the principles and practices of effective
Project management within current and historical
contexts;
GLO 1: Discipline-specific
knowledge and capabilities
ULO 3: Demonstrate knowledge about a selection of
relevant tools and techniques which can be used to solve
project management problems; and
GLO 1: Discipline-specific
knowledge and capabilities
GLO5: Problem Solving
ULO 4: Apply the key learning as a team by solving a
project management problem based on a case scenario
or industry problem.
GLO5: Problem Solving
GLO07: Teamwork

Assessment Feedback
Students who submit their work by the due date will receive their marks and feedback through
CloudDeakin within 15 working days of their submission, as per University policy.
Page 3 of 9
Assignment Description / Requirements
Introduction
Assignment Hurdle and Part A is to be conducted with 4 to 5 team members. Part B is to be
completed individually.
Part A is a consultancy style project plan delivered as a summary report based on a real
organisation or project scenario (see below). Part A is a project plan that has multiple sections of
analysis to address your clients’ problems/requirements. Below is a recommended structure to
complete the assignment.
Part B is a reflection based your team experiences to be completed individually by each team
member.
Hurdle Requirement – Team Work Plan (ungraded)
The Team Work Plan is a hurdle requirement and must be submitted by the due date to receive a
mark for the assignment Part A. Submit a short and simple (one page) high-level plan for your
assignment work. List key responsibilities, tasks, deliverables and due dates for each team
member (team members can share work). This document forms the basis for your work but can
also be used for individual grading by the unit team in case of significant quality differences
between sections of the project plan. No feedback provided on the Team Work Plan Hurdle.
PART A – Group Project Plan
Select a project:
 OPTION 1: Your team should approach a real organisation as a project client and prepare a
project plan based on their requirements. This can be any type of project, a small project
(e.g. the acquisition of a new computer system for a medium sized organisation) or a
subproject of a larger project (e.g. Install computer and audio/visual fittings as part of a
newly built university building).

OPTION 2: Alternatively you may use a real project that has already been completed. If the
information required for you to tackle the project could be obtained, either through
publically available sources or through consultation, then you may proceed with this option.
Any information gaps could be filled in by making reasonable and realistic assumptions.
OPTION 3: The least preferred option would be to use a fictitious project.

You need to demonstrate your learning in this unit (Topics 1 to 7), i.e. tools and techniques, use
appropriate templates and apply learning to prepare a feasible project plan which the organisation
would accept and find useful. Use the components of the project plan below as a guide.
Discuss possible projects in your team and plan for the staffing of your project team. Normally only
one team member would need access to the organisation, providing the project background and
therefore this team member is required as liaison-officer for the project. Other roles could be
project manager, budget manager, risk manager etc. Assign roles as you see fit (see deliverables
and Team work Plan Hurdle below).
Page 4 of 9
Components for the project plan
The components below each section could be used as a guide and could form the overall structure of
the report. Not all aspects under each component will be relevant for every project and additional
aspects may be required. Choose the most suitable structure and content to best present your
project plan as appropriate for your project and your clients’ requirements.
1. Proposal and feasibility
Working as a project team needs to be planned carefully. Consider a SWOT analysis based on
any available information, assumptions and research. Consider a macro environmental
analysis keeping in mind the relationships with potential third parties or external entities.
Present this section with an analytical review that addresses the following question, supported
by your analyses: Is this project feasible and suitable for the organisation?
2. Project organisation
Organisational Structure: Consider a suitable project based organisational structure. Consider
the relevance of interdependencies, economies of scale, organisation size etc. in selecting the
suitable structure.
How many locations are required by the proposed project? Reflect on location specific factors
in recruiting personnel. Determine typical outsourcing processes and analyse how the
recruiting process can occur.
Present with an analytical summary of the overall corporate requirements in the project
organisation with justifications for your choices.
3. Management issues & effectiveness
Teams will likely be culturally diverse, often headed by teams from different geographic
locations. Consider the various schools of management thought. In your viewpoint, which of
these would apply to this venture? There may be a need for a particular management style.
When people or teams come together, conflict is likely. Reflect on possible conflicts that may
arise and if conflict occurs. Should there be an overarching corporate policy? Or will there be
a need for multiple approaches? Consider performance measures that can apply. E.g.
consider the relevance of a 360-degree appraisal or a common code of ethics. Provide an
analytical summary with justifications. If outsourcing project components is an option, how is
this controlled? What are possible variables for success for this project? Consider types of
best practices. Justify your stance in an analytical summary.
Present this section by justifying your viewpoints regarding management styles and conflict
management approaches as well as providing recommendations. Present effectiveness by
providing relevant summaries, best practices justifying them e.g. supported by
tables/diagrams.
Page 5 of 9
4. Plan (schedule)
Prepare a Statement of Work (SoW); specifications for the project; and work break down
structure (level 3 is sufficient). Identify the schedule, milestones and dependencies. Identify
slack time, earliest start and latest finishing for the/each project.
Prepare an overview and use Microsoft Project
(available to you on http://software.deakin.edu.au/apps-and-desktops-anywhere/).
If you prefer other tools such as Smartsheet, ProjectLibre, Project.net, etc. feel free to use
these instead of MS Project. Present only a short summary and submit your full MS Project
plan as a separate .pdf file, or as an appendix to your summary report.
5. Resource and cost plan
What types of estimates are relevant for this project? Prepare relevant pricing estimates.
Allocate cost against schedule for the project(s) under 4 above. Consider the risks that would
affect costing and schedules. Explain and justify how you propose to monitor performance in
the project.
Prepare a short summary and use Microsoft Project to input costs against the project plan
(see above). Include high level pricing and exemplary resource allocation.
6. Project risk assessment
Select an appropriate risk approach. There can be a combination of strategies or only one.
Prepare a risk assessment. Identify and classify the project risks associated with the project.
Recommend exemplary methods for risk response/mitigation.
Present this section by addressing the above questions with appropriate summaries and tables.
Part A deliverables – Group Project Plan (3000-4000 words)
Prepare a consultancy format summary report of your project plan with relevant and concise
information based on detailed analysis and research. Only present in this report the outcomes of
your work. This requires detailed background work and preparation to identify and develop all
required outcomes, present this background work as an appendix to your report (not included in
word count). In your appendix include any relevant attachments you wish to include, including
e.g. your project schedule (MS Project saved as a .pdf), SOW, quality management plan, etc. to
demonstrate your background work. Ensure your report strongly and convincingly relates to the
project (client requirements) in an applied fashion and does not reiterate any theory. Your
audience knows the relevant theory
Page 6 of 9
Each member of the team is expected to participate equally – you can use Microsoft teams
(https://teams.microsoft.com – use your Deakin username and password to sign in) for all your
group discussions and communication needs. The expected minimum is weekly contribution.
Alternatively you can use your CloudDeakin group discussion area. Regardless of the communication
system your group decides to use, your group must provide a weekly summary of progress in the
discussion area of Cloud Deakin (refer to this area under “Discussions” for more information). Nonparticipation in discussions or team meetings is deemed not to have participated. Notify the Unit
Chair early in case of problems or significant deviation from the Team Work plan.
Notes
1. A Project Plan report is to be wither in PDF or Microsoft Word format.
2. You are not expected to provide technical background on the domain of your project.
Focus on the project management aspect of the assignment only.
3. Make any assumption necessary, the focus is the demonstration of Project Management
knowledge, not the technical detail of the project.
4. You are expected to supplement the theoretical concepts learnt in the topics via wider
research e.g. into current trends and apply these to your project context.
5. The team has to work together to develop the project plan. Ensure parts relate and are
consistent.
6. This assignment does not require a set number of references. However if you rely on work
from others, ensure sources are referenced. Ensure that you have read/understood all
related information regarding Plagiarism/Collusion/Citation. A list of references and/or
bibliography using Harvard style are expected.
PART B – Reflection
“Tell me and I will forget. Show me and I may remember. Involve me and I will understand”
(Confucius 450 BC). The same principles underlie and are applied to ‘experiential learning’ for
project management in this unit. Project management today involves ‘people management’ and
this reflection is an activity that will help you build this skill through the experiential learning
process. This process will not only help you work through each week, but also will be a long term
reference for real life roles.
Not unlike an organisation, in this unit your team may consist of members from varied educational
backgrounds and different cultures. When you join an organisation, you find established teams
and individuals that come into the organisation. These people are also varied in culture,
background, knowledge and experience. It is therefore imperative that you not only understand
‘project management’ principles, but also understand and become aware of your environment, its
strengths and weaknesses. Your environment however includes your team, those external to your
team in the organisation and yourself. All your experiences, behaviour and attitude will contribute
to the team development/performance, which is critical for project management in organisations
today.
One objective of the exercises is to take you through an ‘experiential learning’ journey, where you
are given a chance to acquire and apply knowledge from this unit, in a relevant pre-determined
setting. The second objective is that you become aware of inherent qualities, strengths,
weaknesses, skills, abilities and behaviours within your team – so that you are able to work with
each member. Therefore, throughout the learning period, you are on a constant experiential
learning cycle.
Page 7 of 9
Your Reflection
Critically evaluate and complete the Individual Team Work Process Evaluation Form and the Group
Process Evaluation Form (see Individual and Team Work Process Evaluation Form.doc on
CloudDeakin). Based on your evaluation, the Team Work Plan submitted in week 4 and your notes
and observations throughout the trimester use reflection to identify relevant happenings (as you
deem useful) and prepare a reflection.
Your reflection should relate to the team development process and your individual contribution
through the stages, specific incidents that are relevant and all key learnings. Reflect on the team
and how each member committed to the team. Reflect and evaluate each team members
contribution against the Team Work Plan and reflect on your and others role in the team.
Remember that your learning processes and highlights may conflict and are varied. Reflect on
significant events e.g. how you responded to conflict or late deliverables etc. What did you and the
team do to achieve the desired outcome and what you would do differently etc.
You are encouraged to discuss your observations with your team to inform your individual
reflection. This is the forum for you to get to know your peers fully, clear misunderstandings and
continue team building – perhaps lead to a longer term professional friendships/alliances.
Essential background – reflective writing
http://www.deakin.edu.au/students/study-support/academic-resources/reflective-writing
Part B deliverables (500-1000 word reflection report)
Complete and submit the Individual and Team Work Process Evaluation Form. Also, write up the
reflection report informed by your observations throughout the trimester, relating to team
development and reflection on your role as a team member and the Team Work Plan.
Submit both the completed Individual and Team Work Process Evaluation Form and reflection report
into Assignment Part B Dropbox.
Not all stages of your project would have been relevant or applicable for each team. Use only what
actually occurred and what was relevant. If there are e.g. no conflicts in your team it may be
worthwhile mentioning how this was achieved.
Before submission of the reflection, undertake a brainstorming session with other team members
and consolidate all your learning. Once submitted your reflection will be treated confidentially.
Page 8 of 9
Submission instructions
Please refer to the due dates on the first page of this assignment description.
There is no need for a specific requirement to name your files but you should choose a meaningful name.
Hurdle:
Only ONE member of the team, usually the project leader, must post the Team Work Plan document on
CloudDeakin to your ‘Team Work Plan’ submission dropbox by the due date. The Team Work Plan is not
graded and no specific feedback will be given.
Part A Group Project Plan
Only ONE member of the team must submit the project plan report file and any other relevant supporting
documents via CloudDeakin using the ‘Part A’ submission dropbox. Your team can provide these supporting
documents as appendices in the main report, or as separate files (name them accordingly).
Part B Reflection
EVERY team member must submit a reflection report and process evaluation form via CloudDeakin using
the ‘Part B’ submission dropbox.
Notes
1. No hardcopy submissions of assignment or any assignment attachment sheets required or
accepted.
2. Do not post more than one submission to the Assignment Dropbox. Only the latest will be graded.
3. If approved by the Unit Coordinator, the team can submit the optional Group mark allocation form. Teams must
alert the Unit Coordinator early regarding non-participating team members. Informing the Unit Coordinator close to
the due date of team issues is too late for any rectification.
4. Any submissions after the due date will be considered late. Any reference made to time is
deemed to be Melbourne (AEDT) time. It is your responsibility to make provisions for any time
differences.
5. Extensions must be requested at least 5 working days before the due date (except for
emergencies); all requests for extensions must include the work completed to date.
6. The following marking penalties will apply if you submit an assessment task after the due date
without an approved extension: 5% will be deducted from available marks for each day up to five
days, and work that is submitted more than five days after the due date will not be marked. You
will receive 0% for the task. ‘Day’ means calendar day for electronic submissions. The Unit Chair
may refuse to accept a late submission where it is unreasonable or impracticable to assess the task
after the due date.
7. For more information about academic misconduct, special consideration, extensions, and
assessment feedback, please refer to the document Your rights and responsibilities as a student in
this Unit in the first folder next to the Unit Guide of the Resources area in the CloudDeakin unit site.
8. Building a portfolio that evidences your skills, knowledge and experience will provide you with a
valuable tool to help you prepare for interviews and to showcase to potential employers. There
are a number of tools that you can use to build a portfolio. You are provided with cloud space
through OneDrive, or through the Portfolio tool in the Cloud Unit Site, but you can use any storage
repository system that you like. Remember that a Portfolio is YOUR tool. You should be able to
store your assessment work, reflections, achievements and artefacts in YOUR Portfolio. Once you
Page 9 of 9
have completed this assessment piece, add it to your personal Portfolio to use and showcase your
learning later, when applying for jobs, or further studies. Curate your work by adding meaningful
tags to your artefacts that describe what the artefact represents.

The post MIS798 Graduate Learning Outcome appeared first on My Assignment Online.

Leave a Reply

Your email address will not be published. Required fields are marked *