Assessment tasks for MGT8022 There are two assessment tasks for this course. Assignment 1 requires you to provide a critical analysis focused on two management · Problems (refer below). You will...

1 answer below »
Please refer to the attached... Please follow the instruction


Assessment tasks for MGT8022 There are two assessment tasks for this course. Assignment 1 requires you to provide a critical analysis focused on two management · Problems (refer below). You will provide your critical analysis in a report format (refer Below). For both assignments you have the choice of using your current workplace (or an organisation you are familiar with) as a case. Alternatively, you can use a case study in the Literature which has sufficient information for you to meet the assignment requirements. For further information on selecting your project, refer to the ‘How to pick your MPM project assignment’ document provided. Extra Instruction; · Choice company and applied the above and below instruction · Be thorough and apply the project management knowledge · Discuss your project depths and us relevant information from Module 1 topic and Module 2 topic below. Together these assessment activities will help to demonstrate compliance with the Australian Qualifications Framework (AQF) requirements for students to develop appropriate research skills. AQF states that ‘graduates of a Master’s Degree (Coursework) will demonstrate the application of knowledge and skills to plan and execute a substantial research-based project, capstone experience and/or piece of scholarship’ (Australian Qualifications Framework Council 2013). Use of Endnote (or other bibliographic software) You are strongly urged to use Endnote for this assignment and for other assessment activities in your studies across all courses. Endnote and other referencing, bibliographic or citation software programs: · manage and organise references into personalised groups · serve as a personal record of your research notes and annotations on PDFs · search those notes and annotations as well as the full text of PDFs · enable collaboration using shared libraries either as read/write or read only · May have a cloud based version which performs all the functions of the desktop and keeps libraries on different computers in sync (the Endnote cloud version needs a licenced desktop copy to fully enable all features). There are many different products, some freely downloadable such as Zotero and Mendeley; and others built in to the word processor, as in MS Office Word. Those that are most reliable are commercial products such as RefWorks, BibTeX and EndNote. 2 ASSIGNMENT 1 REQUIREMENTS Context You are working as a project manager in the organisation you have chosen for this case study, and a senior manager has asked for your assistance with understanding and resolving two problems (refer below). The senior manager has asked that you provide a justified response to the two problems in the form of a written report (refer report structure below). Your responses are to be justified by recent and relevant scholarly (journal articles and eBooks) literature. The two problems 1. Problem 1 – The nature of work and its management (refer to Module 1 below): · Module 1 - The management of work · For your chosen organisation, objectively examine the day-to-day activities that other employees undertake in their respective roles across the organization. · Based on the definitions of ‘work’ in the academic literature, critically argue (i.e. support your argument with scholarly literature) which of those activities undertaken within the organisation can be classified as ‘operational’ work and which activities can be classified as ‘project’ work. NOTE: This analysis is about what happens across the organization and is not focused on just · work that may happen within specific projects. · Evaluate, with the use of scholarly literature whether the managerial approaches (e.g. project management, scientific management, bureaucratic management) adopted by the management of the organization for the operational work and project work are appropriate. · Make recommendations for any suggested changes to these managerial approaches based on the findings of your analysis. 2. Problem 2 – Structuring project work (refer to Module 2): · Module 2 - Delivering change through project work · Module 3 - Alternative views of project work · Considering only those activities that you have identified as ‘project’ work, evaluate, using scholarly literature, whether your chosen organisation is using the concept of ‘portfolios, programs and projects’ for structuring and organising project work. · If the organisation is currently using those structures, using scholarly literature, critically assess whether their use is appropriate; or alternatively · If the organisation is not currently using these structures, using scholarly literature, critically assess whether there would be any benefit in doing so. · Make recommendations based on the findings of your analysis. [Course module 2] Report structure For assignment 1, provide the following: Mark sheet/rubric (see separate mark sheet / rubric on the course study desk. Your assignment and mark sheet must be attached together when submitted for marking) Report cover sheet (similar to what you would use for a workplace report) Executive summary (200 - 300 words – not included in word count) Table of contents, List of Tables (if required), List of Figures (if required) 1. Introduction (100 words) Introduce the purpose of your report and its structure. 2. Organisational context (250 words) • Provide sufficient detail about the organisation so that the reader can understand 3 your responses to the two issues. • Generally, the type of information to include would be the type/sector of business that the organisation is in, the size of the organisation (this may be through listing the number of staff or annual turnover), and management structures/organisational hierarchy. 3. The nature of work and its management (Problem 1 Analysis) (800 - 1000 words) • As per the description above provide a response justified by scholarly literature to the problem. 4. Structuring project work (Problem 2 Analysis) (800 - 1000 words) • As per the description above provide a response justified by scholarly literature to the problem. 5. Conclusion (100 words) • Summarise your overall findings (i.e. what are the key insights from your analysis of the two problems). Reference List • Only include references that you have actually cited in your report • For each issue you must cite at least six scholarly references. Of these six references at least three must be peer-reviewed journal articles less than 10 years old. Websites and videos are not suitable for use in this course’s assignment. Report formatting and referencing • The total length of your assignment 1 is to be approx. 2250 words (excluding executive summary and reference list). There is a +/- 10% allowance to this word count. • Please follow general formatting guidelines as outlined in the Communication Skills Handbook (Summers & Smith 2014). • Remember that the assignments in the project management courses require referencing to use Harvard AGPS6 formatting and not APA. • Your assignment must contain citations and only references that you have cited in your report should be included in the reference list. Use of aliases for organization names University markers will not share your assignment with any other organisation. As such from University’s perspective it is not a requirement for you to seek permission to write about an organisation. However, if you have concerns about this you can either choose to rename the organisation and use aliases as appropriate, or confirm with your manager that they provide permission for you to use the organisation for your assignment. Remember, you just need to give us sufficient organisational context that we can assess your response to problem 1 and Problem 2. MGT8022 ASSIGNMENT 1 MARK SHEET – PROJECT-BASED MANAGEMENT MGT8022 ASSIGNMENT 1 MARK SHEET – PROJECT-BASED MANAGEMENT (Note to markers – indicate level of achievement for each row by highlighting relevant text or cell - do not provide a numerical score for each row) Non-compliant Poor/inadequate Basic Adequate Good Excellent Mark 0 0 to 49 50 - 64 65 - 74 75 - 84 85 - 100 /100 Executive summary No ES provided. Poor quality ES that does not provide the required information. Basic ES that provides limited information, or does not provide information in a clear and concise manner. Adequate ES that provides sufficient information. Good ES providing the required information in a clear and concise manner. Comprehensive ES providing the required information in a clear and concise manner, and able to function as a stand-alone document and/or presentation to a CEO. 1. Introduction No introduction provided. Poor introduction provided, or irrelevant information. Basic introduction provided. Adequate introduction provided. Good clear introduction provided. Clear, concise and comprehensive introduction providing essential details. 2. Organisational context No description is provided. The description of the organisational and project context is poor. The description of the organisational and project context is basic. The description of the organisational and project context is adequate and permits some understanding of the context. The description of the organisational and project context is good and permits an understanding of the context. The description of the organisational and project context is excellent and permits a full understanding of the context. 3. Problem 1 analysis No discussion of the topic is provided. The discussion of the topic is poor. A minimal amount of the discussed literature is relevant and reliable. The use of the literature to examine the organisation is basic. The section has a basic structure, minimal sign-posting and weak line of argument. Some of the recommendations are somewhat logically derived. There is evidence of a basic understanding of the topic. Some of the literature discussed is highly relevant and reliable. The use of the literature to examine the organisation is adequate. The section has an adequate structure, some sign-posting and an adequate line of argument. Some of the recommendations are logically derived and justified. There is evidence of an adequate understanding of the topic. The majority of the literature discussed is highly relevant and reliable. The use of the literature to examine the organisation is good. The section has a good structure, sign-posting and line of argument. Tables and/or figures may have been used to add value to the report. The conclusions and recommendations are logically derived and are justified. There is evidence of a good understanding of the topic. The literature discussed is highly relevant and reliable. The use of the literature to examine the organisation is critical and insightful. The section has an excellent structure, sign-posting and line of argument. Tables and/or figures have been used to add significant value to the report. The recommendations are logically derived, are well justified and are aligned. There is evidence of an excellent understanding of the topic. 4. Problem 2 analysis No discussion of the topic is provided. The discussion of the topic is poor. A minimal amount of the discussed literature is relevant and reliable. The use of the literature to examine the organisation is basic. The section has a basic structure, minimal sign-posting and weak line of argument. Some of the recommendations are somewhat logically derived. There is evidence of a basic understanding of the topic. Some of the literature discussed is highly relevant and reliable. The use of the literature to examine the organisation is adequate. The section
Answered 3 days AfterJul 31, 2021

Answer To: Assessment tasks for MGT8022 There are two assessment tasks for this course. Assignment 1 requires...

Parul answered on Aug 03 2021
144 Votes
Project Report on Building Information System
Project Report on Building Information System
Submitted to - <> Submitted by - << Please add your name or name of the group here>>
Contents
Introduction    3
Organisation Context    3
Problem faced by Organisation    4
Goals and Scope    4
Organisational Project Objectives and Milestones    4
Scope of Problem    6
Agreed-on Team meetings    7
Structuring project work -Schedule and Budget    7
Work Breakdown Structure    7
Tools and Framework used    9
Deliverables    11
Quality Management    11
Quality Management Requirement    11
Quality Planning    12
Quality Assurance    13
Quality Control    14
Conclusion    15
References    17
Appendix    18
Milestones    19
Budget    20
Gantt Chart    22
Introduction
The project is for establishing the information systems for one of the prestigious aviation companies, ‘New India Air’ for its charity project, ‘Pilot Aerials’. The IS will work as a support system for providing smooth operation for the ‘Pilot Aerial’ and increase its effectiveness to deliver value around its objective. New India Air arranges a magnanimous help, in relationship with the Government of India, called Pilot Aerials. Working with Government and some private clinics, medical care offices and
organ banks, New India Air matches volunteer pilots from numerous business aircrafts, willing to give their time and planes, with penniless individuals whose medical care issues expect them to make a trip to get demonstrative or therapy administrations in significant emergency clinics in the metropolitan urban areas in India. Moreover, Pilot Aerials will likewise give transportation to giver organs, supplies, and clinical work force. All flights are for nothing, and the expenses are borne by the volunteer aircrafts who give their pilots and planes.
The pilots of the business carriers who volunteer for the Pilot Aerials program need no clinical preparing and offer no clinical help. The planes don't convey any clinical gear nor do they oblige any cots. Patients, in any case, should be restoratively steady and have the option to enter and leave the airplane with next to zero help. The Pilot Aerials travellers commonly travel to and from an emergency clinic or facility for finding, medical procedure, or some other therapy. Sidekicks, like a family member, companion, or medical attendant are permitted.
Organisation Context
New India Air opened for business in India in January 2015 when a group of corporate investors pooled their life savings and secured a large loan from the Punjab National Bank. Located at Indira Gandhi International Airport in New Delhi, New India Air is a fixed base operator (FBO) facility offering a full range of services to the growing demands of business and private aviation. Currently, the company has 23 employees composed of pilots, mechanics, and office staff.
As a FBO, New India Air provides the following services:
· Business jet, propjet, helicopter, and propeller airplane charter
· Refuelling
· Airframe, engine, propeller, and avionics (in association with HAL and the British Airways)
· Airplane rental
· Flight instruction
· Pilot supplies
New India Air has been receiving increasing attention throughout India for its charter service, maintenance, and flight instruction from other domestic and international airlines companies such as Air India, Jet Airways, Indigo, Malaysian Airlines, Go Air, and others.
Problem faced by Organisation
Presently, a pool of pilot volunteers from different business aircrafts is kept in a record organizer. On the off chance that a clinic or an individual with a clinical issue with monetary difficulty contacts New India Air, the name of the explorer, the objective, dates/times, and the quantity of partner in crime are mentioned. On account of restricted weight limitations in little airplanes, the loads of the travellers, tourists and their baggage are required too.
After the underlying data is given, New India Air contacts the volunteer pilots to decide their accessibility. Albeit a volunteer pilot might be willing and accessible for a Pilot Aerials flight, the plane might not have the reach or weight-conveying necessities. The New India Air the board thinks this is a wasteful utilization of time, since many pilots might need to be reached until a pilot and a reasonable transporter airplane can be found.
Goals and Scope
Various project goals have been categorized as mentioned below.
Organisational Project Objectives and Milestones
    Project Objectives    
    Priority
    Comment/Description/Reference
    Functional Goals:
    1
    Remarks
    
    
    An integrated information system which may automate the work and provide real time information to all stakeholders
    
    
    Hardware & Software to be installed for application access
    
    
    
    Business Goals:
    1
    
    
    
    
    < Increase the efficiency>

    
    Measurable impact on operations
    Technological Goals:
    2
    
    



    
    Key Stakeholders – Volunteer Pilots, Participating Airlines, Patients, Hospitals, NGOs, Government
Modularity or Coupling level between the modules must be as low as possible and technology enhancement as per various upgradations must be kept in mind
Use of APIs and Web Services wherever necessary
Database/Data warehouse with suitable reporting or business intelligence tools
    
    
    
    Quality Goals:
    2
    
    



    
    Must not fail under all possible inputs
Must not impact all modules after failure
Provide enough support for quick learning
    

    
    Sub-softwares, code or modules must be latest and open for extension
    Constraints:
    3
    
    
    
    Follow if any
    
    
    Secure enough and does not impact any security systems related to government
    
    
    Follow protocols prescribed in standard security systems for semi-government projects
    
    
    
Scope of Problem
Project will provide an eco-system of hardware and software which will enable the customer to access the required data for performing the functions in an integrated environment. It will also shift the traditional way of working to new ways. As part of project, Pilot Aerial, the customer would be able to access the historical and new data dynamically (real-time) through software application. The algorithms behind the software packages will enable the consumer (patient/hospital/NGO/Family members of the patient) to submit their request for travel which will automatically look for volunteer pilots and airlines available on the same route and stipulated time.
Information for baggage and no. of family members accompanying would be matched accordingly and would help the algorithm to finalise the booking and provide a record for the same to all respective stakeholders.
IS will also open for extension (if any), like no. of pilots increased, new airline wanted to participate in the charity work or any other.
As per the project requirement, the IS will also keep record of various contributions made by specific pilot of specific airline under the initiative.
Included
Project deliverable include the below mentioned items –
· A software application for desktop terminals
· Web application on top of it
· Mobile App for end consumers
· Hardware – Data Centre and Disaster Recovery Centre
Excluded
· Training of end-users is excluded- Not mentioned specifically for project deliverable
· Annual Maintenance Contract after the expiration of two years of service agreement
The nature of work and its management
Agreed-on Team meetings
· Daily web-calls at 8PM for the review of work, Attendees- All Stakeholders from Customer and ITIA
· Weekly review meeting with all stakeholders (Internal) on Friday, 9:30 AM
· Project Status and Milestones discussion on every Monday with all stakeholders, internal and external
Structuring project work -Schedule and Budget
The schedule and Budget has been extracted through WBS built in ProjectLibre by giving the inputs to it by thorough study of software requirement specification.
Work Breakdown Structure
    #
    Level 1
    Level 2-3
    Output (Deliverable)
    Duration (Days)
    Resource
    1.0
    Kick Off
    1.1 Feasibility Testing
1.1.1 Financial Feasibility
1.1.2 Technical Feasibility
    Feasibility Reports
    4
    Business Analyst & Architect
     
     
    1.2 Meetings and Approvals
1.2.1 Arrange meeting of major stakeholders
1.2.2 Take approval of Head of company for Go-Ahead
1.2.3 Ensure everyone understand the project
    Approvals
    4
    PMO
    2.0
    Software Requirements Analysis
    2.1 Requirement Gathering
2.1.1 Identify and consult information sources (customer, users, previous systems, documents, etc.) in order to get new requirements
2.1.2 Gather identified requirements
    Requirements Specifications
    19
    Business Analyst
     
     
    2.2 Elicitation, analysis and specification of customer’s requirements
2.2.1 Analyse gathered requirements to determinate the scope and feasibility
2.2.2 Verify the correctness and testability of the Requirements Specification and its consistency with the Product Description
2.2.3 Generate or update the Requirements Specifications
2.2.4 Structure and prioritize requirements
    SRS Document Validated
    25
    Business Analyst & PM
     
     
    2.3 Verification and validation of requirements
2.3.1 Validate that Requirements Specification satisfies needs and agreed upon expectations, including the user interface usability
2.3.2 Approval of Management
    SRS Document Approved
    4
    Business Analyst & PM
    3.0
    Software Component Identification
    3.1 Understand Requirements Specification
3.1 Understand Requirements Specification
3.2 Document the Software components identification
    Software Component Identification
    7
    Business Analyst, Design Team, PM, PMO
    4.0
    Software Design
    4.1 Design the Components
4.1.1 Verify the contribution of the Component
4.1.2 Problem solved by components
4.1.3 Design Data of components
4.1.4 Designing architecture of database
    HLD and LLD
    10
    Design Team, DBA
     
     
    4.2 Write code for components
-Coding in decided language
    Software Components
    25
    Developers
     
     
    4.3 Test Cases and procedures
4.3.1 Test case for each component
4.3.2 Provide test cases to customer
    Test Cases
    26
    Testing Team & Business Analyst
     
     
    4.4 Verify the components
4.4.1 Verify the components
4.4.2 Corrections if needed
    Verified Software Components
    4
    Testing Team, Business Analyst, PM & Developers
    5.0
    Software Integration and Tests
    5.1 Setting Testing Environment
5.1.1 Checking availability of components
5.1.2 Understand the test cases
5.1.3 Check for specifications (h/w, OS, browser, DB, etc.)
    -----
    2
    Developers & Testers
     
     
    5.2 Integration and Testing
5.2.1 Integrate the S/w Components
5.2.2 S/w test using test cases
5.2.3 Check for problems in results of Integrated S/w
5.2.4 Fix the problems
5.2.5 Designing of report format
    Progressive Test Report
    21
    Testing Team, DBA, BI Expert
     
     
    5.3 Verification and Closing Testing
5.3.1 Checking results' compliance with requisites
5.3.2 Checking product improvement through test cases
5.3.3 Prepare a report for testing iterations
    Final Test Report
    4
    Testing Team Lead
    6.0
    Product Delivery
    6.1 Readiness for Delivery
6.1.1 Understand delivery requirements
6.1.2 Prepare deliverables
6.1.3 Prepare manual of software
    Manual
    5
    Business Analyst & PM
     
     
    6.2 Perform Delivery
6.2.1 Check s/w components meet acceptance criteria
6.2.2 Arrange customer meeting
6.2.3 Conduct User Acceptance Test
6.2.4 Consider the feedback of customer and make necessary changes
6.2.5 Get UAT approved from customer
    UAT Document
    5
    Business Analyst & PM
    7.0
    Product Assistance
    7.1 Check for the specifications of s/w at customer premise
     
    3
    Application Support Team, Team Lead
     
     
    7.2 Deploy S/w at customer's premise
     
    5
    
     
     
    7.3 Check for smooth functioning
     
    7
    
     
     
    7.4 Assist with problems faced by customer
     
    30
    
Tools and Framework used
The tools choses depend on whom and what to communicate. In order to keep moving the information an effective channel is chosen depending on the target and level of seriousness of information flow so that the receiver gets the best impression that the sender wants to make. Method used for communication are, Meeting summaries and Status reports after every milestone achieved, Newsletters and Formal presentations to educate the users and customers, Surveys for gathering information and informal meetings for team building/informal communication/feedbacks etc.
The project Communication Plan made for Pilot Aerials is given below:
     
    Status Report
    Employee meetings
    Project Updates
    Message...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here