Report代写 | School of Business

Agenda items
1. Discussed task delegation and broke down which members should do which parts of the
assignment
2. Rough deadlines discussed with clear goals in mind
Action items Owner(s) Deadline Status
Due Date Justine 29/9/19 In progress
Staff Management Plan Haomin 27/9/19 Complete
Project Progress Report Justine, Haomin 29/9/19 Complete
Staffing Management Plan
Project Name:
The Staffing Management Plan of the Dancing School
Project Summary (Description):
The project is a staffing management plan for the dancing school. The purpose of the project
is to design a practical staffing management plan to ensure the normal operation of the
dancing school and promote the company’s development. The plan mainly includes five parts:
methods of communications, staff deliverables / requirements, success criteria, training &
support and conflict resolution.
Stakeholder Name Stakeholder Role eg. sponsor, champion
Bank lender
Students and their parents client
The Real estate leasing company supplier
Commodity company(shoes etc) supplier
Methods of Communications
1. Daily standing meeting (about 10 minutes)
(1) Meeting time: after daily performance or after class.
(2) Purpose of the meeting: 1) To deal with the problems encountered today and sum up the
experience; 2) To properly plan the team’s tasks for the next day; 3) To discuss the problems
encountered when communicating with students or parents the same day and solve them in time.
(3) Basic requirements: each member of the team must attend the meeting if nothing goes wrong.
2. Monthly summary meeting
(1) Meeting time: after the last working day of the month
(2) Purpose of the meeting: 1) Every staff should share the problems and gains encountered this
month; 2) To set the tasks of the next month.
(3) Basic requirements: each member of the team must attend the meeting if nothing goes wrong.
3. Ad hoc meeting
(1) Meeting time: when requested by members
(2) Purpose of the meeting: gather the wisdom of the team to solve the big problems encountered
and grasp the development opportunities in time.
(2) Basic requirements: each member of the team must attend the meeting if nothing goes wrong.
Staff Deliverables /Requirements
1. Manager
(1) Be responsible for coordination and communication of different members of the team.
(2) To organize daily standing meetings, monthly summary meetings and ad hoc meetings.
(3) To formulate the team’s long-term development plan and promote the execution of the
plan.
(4) Be responsible for measuring and managing the completion of task which set by team
members
2, The teacher
(1) Be responsible for the teaching of the workshop and to organize students to perform
regularly.
(2) Be responsible for communicating with students in the workshop in order to understand
their needs and recommendations.
(3) To investigate the satisfaction of the students every month.
3. Members who are responsible for marketing promotion
(1) Be responsible for communicating with parents and gathering parents’ needs or
suggestions for the team.
(2) Be responsible for introducing and encouraging art to the wider community and
increasing the number of applicants.
(3) Be responsible for operating mobile applications and communicating with parents in time.
4. Support staff
(1) Be responsible for the procurement of office supplies and teaching equipment, etc.
(2) Be responsible for the maintenance and management of teaching space and office space.
5.Financial staff
(1) To manage the income and expenses of team.
(2) To report the income weekly at the monthly summary meeting.
Success Criteria
1. The manager should organize the team members to set the tasks for the next month every
month in order to determine the mission of each different member.
2. Specific success criteria for team members:
(1) Manager: 1) ensure that the entire team is in a harmonious atmosphere;2) ensure that the
entire team is functioning normally; 3) ensure that the team size and the number of students
naturally grow.
(2) Teacher:1) ensure normal teaching and performance; 2) ensure that students’ satisfaction
reaches the target every month.
(3) Members who are responsible for marketing promotion: the number of new students
every month.
(4) Support staff: ensure the normal operation of the entire team.
(5) Finance staff: ensure that financial management is carried out smoothly every month
without financial errors.
Training & Support
1. Manager: register for the MBA class at the nearest school for manager.
2, The teacher:
(1) The team conducts training for teachers to find courses in the study of the dance culture of
Nrithyopasana.
(2) To looking for Nrithyopasana dancing teachers from other places for teacher.
(3) The team will focus on the problems encountered in the teacher’s teaching work at the
daily standing meeting to help the teachers to meet the needs of the students.
3. Members who are responsible for marketing promotion:
(1) Enrolling marketing courses for members to improve their propaganda ability.
(2) Providing propaganda equipment for members who are responsible for marketing
promotion.
4. Support staff: Team managers help administrative logistics personnel communicate with
suppliers of administrative supplies
5. Financial staff:
(1) Registering for financing courses for members in order to improve the financial ability of
the staff.
(2) Other members of the team should consciously report to the financial staff when using
funds in order to facilitate the work of financial staff.
Conflict Resolution
1.Conflicts resolution between team members:
(1) To formulate the basic principles of dealing with team members’ conflict. One of the most
important principles is that conflicts must be resolved openly. To deal with conflicts openly
can resolve conflict quickly and effectively.
(2) To set a committee which is responsible for publicly resolving conflicts when conflicts
arise.
(3) To dealing with conflicts should first communicate with the parties to find out the reason
for the conflict.
(4) After understanding the general situation of the conflict, manager should choose different
treatment methods according to whether the conflict is a private conflict or a work conflict; If
the conflict is a private conflict, then the parties should be resolved quickly in private or
communicate each other through HR, so that private conflict does not affect Team work; If
the conflict is a work conflict, manager should analyze the reasons for the conflict and the
conflicting views. Then manager should organize the conflict committee to deal with the
conflict to make the conflict resolved openly and effectively.
2. Conflict resolution between customers and teams.
(1) When a conflict occurs, the team should listen carefully to the customer’s needs and the
reasons for the conflict.
(2) To clarify the team’s principles and bottom line firstly, and then try to meet the needs of
customers within the principle and the bottom line or patiently explain the reasons to the
customer.
(3) If the customer’s needs have passed the bottom line of the team, it is necessary to clearly
express objections and handle the customer’s refund in time.
Project Execution (Progress)
Report
Project Name: Name:Nrithyopasana School of Bharatanatyam (NSB) app development
Project Summary:
The project is to create an android application to aid communication with the school, parents
and students in order to increase publicity and potential students. The app should include a
splash screen, with options to create a profile, take attendance, add notes, scheduling
capabilities, quick communication, social media links and have different options for students
and teachers.
The primary goal is to provide good clear communication and to eliminate the chances of
messages being lost, second is to additionally promote the core values and mission to
distinguish itself from other schools, increasing overall enrolment target, community
involvement and to promote the art of Bharatanatyam
Project Team Members: Justin Tan, Omair Qureshi and Haomin Qian
Report Date: 17/09/19
Reporting Period:
Progress: Tasks completed to date:
Project Management documents (Stage 1)
Business Case Financials
Business Case
Project Charter
Meeting Minutes
Student Contribution Statement
Timesheet
Project Management documents (Stage 2 )
Business Diagram
Cost Baseline
Gantt Chart
Timesheet
Work Breakdown Structure
Project Management documents (Stage 3)
Project progress report
Staff Management PLan
Team Contract
Meeting Minutes
Timesheet
STudent Contribution statement
Project Deliverables
App Breakdown
In App Development we brokedown the fundamental variables and code in order to reverse
engineer the app to suit our own needs
Cost Baseline
This was made as an estimate for financials for the client in order to best meet the basic
requirements and improve upon them
Work Breakdown Structure
This broke down the core aspects of the project procedure including who was involved and what
processes went on in the background
Business Case
This refers back to the initial project specifications in the first stage and helped specify and
breakdown any further requirements, risk factors, and how best to approach situations if there were
any to occur.
Project Charter
Project charter was a core document in detailing the fundamental aspects of the project, delegating
specific roles within the group and determining the best approach.
Progress: Tasks yet to be completed:
App design (3.2)
CMS website
Product demonstration
List all PM documents & project tasks to be completed (project deliverables) to be submitted in the
coming weeks. Include any deadlines.
In particular record any tasks outstanding ie. involving slipped milestones. Justify any variations
between planned and actual schedule and the corrective actions (if required).
Propose a new date for any outstanding tasks in the Change Requests section below.
Progress: Costs:
According to the original Cost Estimate baseline, We Would have spent an estimated $40,600 on the
project.
According to the timesheet for stage 1 and stage 2, we have spent a total of $6347,61 projecting a
lot over then the rough estimate in the Cost baseline.
Quality Control (Including Testing)
Quality objectives
1. Splash screen
2. Teacher options
3. Enrolment details
4. Profile creation
5. Notes via subject
6. Attendance
7. Scheduler
8. Communication via email
9. Social media links
10. Budget estimate
11. risks/issues
12. Project timeline
Objectives 1-9 aren’t going to be met until a later stage of the assessment.
Budget estimate
Budget estimate has been completed in an earlier stage and was repeated further up and we have
seen how it was slightly under what was expected meaning we need to adjust this in an appropriate
manner seeing why it came up shorter then calculated
Risks/ issues
Risks and issues are not going to be tested until a later stage however by keeping in mind the project
specifications we can ensure that a lower amount of risks or issues occur by carefully reviewing each
stage.
Project timeline
This has been met and thoroughly checked by the group to contain accurate goals and deadlines.
However we can make adjustments as future more specific goals are revealed in a later stage.
Usability testing
In order to make sure the mobile app is easy to use, we should test the ease of navigation by
ourselves (the team) and also get an outside opinion such as a teacher or classmate, preferably one
who doesn’t know too much about app design as this well simulate the client who doesn’t have a lot
of experience in this area and will also ensure that the app is easy to use for complete beginners
Other things to take into consideration is does the app itself make sense, by breaking down the core
app navigation via the folder structure we can say does it make sense for an activity to be in this
folder or to follow this path, and if it seems too confusing we should consider auditing or changing
the path completely.
Compatibility testing
In order to ensure the mobile application works on different devices we should be coding with older
versions in mind i.e we should be coding something that can work well on android 4 and is also
optimised for android 7+.
In order to achieve this we need to be minimising the colours and animation as this is more limited in
older versions, by keeping the code relatively simple and clean makes it compatible against multiple
versions. We should also keep scaleability in mind as well, meaning we should be able to cater
towards smaller devices (4.5 inch or less) as well as larger devices such as tablets by having multiple
versions of icons and activities we can achieve this in a professional manner.
Interface testing
In order to achieve a simple to use interface, buttons and other navigation items should be both
clearly visible and well contrasted to the res of the app, making sure the text itself is readable and it
leads to where the user expects it to. We can achieve this by having buttons with a little padding
around text making it easy to click, with hover or click option to ensure a user knows where it leads
to.
Services testing
In order to test the services of the application online and offline we first need to test it on different
devices without internet access simply by turning off internet connection or simulating it through
android studio. To test it online we can also test on different devices ensuring internet capabilities
are enabled. We should test how well the data syncs between devices and also test what is visible
offline
Installation testing
In order to validate the installation process we should test different ways of installing the project i.e
1. Directly through android studio
2. Online through github or a file sharing service
3. Through an app store or similar
By doing this then we can ensure there aren’t any issues when installing the app through multiple
ways.
Security testing
In order to test the validity of data we should test in separate areas. This will ensure syncing can
occur over distance and online, we should also check if login and password are reliable seeing if the
information is displayed at all when it should is key in testing this (i.e the username and password
accidentally show up in the debug or run log)
Risks & Issues (Including Resources)
– Not enough parents will be willing to install the app and render the project useless.
– The school shuts down before the project is completed
– The school is unable to procure funding in order to maintain and update the app
– Users refuse to use the app
– Database server goes offline
– User information is leaked by a third party
– Lack of compatibility (i.e majority of users are on older devices or ios)
The Risks identified beforehand are mostly referring to after launch of the app, so that can’t be
determined whether we have or haven’t averted that.
Other issues to factor in from previous stages:
Financials – Our financial estimate seemed to be too low compared to what actually was recorded
and thus would be an issue from a client having to pay more than projected almost 25% more.
Time – The team seems to be consistently pushing the work back towards the closer date each stage
it is due, this leads to insufficient quality in reports and makes the quality lower of the overall plan
itself. Ways to avoid this would be starting earlier, having earlier deadlines or goals within the group
itself
Meetings – in both the last 2 stages there was only ever at most one team meeting at a time this lead
to issues when delegating staff and lead to confusion or poorly managed documents as a direct
result.
Effort – overall group morale seemed to be low when researching, planning and executing certain
aspects of this project, it led to a loss of work quality and a large volume of work being done last
minute, ways to avoid this would be starting earlier, encouraging each member and setting clear
plans and goals.
Change Requests (eg Scope & Time)
Time management
As the project is progressing we are unable to finish work in a timely manner, it is important to
address this as soon as possible in order to prevent loss of quality s will be required from all parties.
What’s going well and why?
Overall the core aspects of the project itself are met in a simple easy to follow way, the base
requirements are always kept in mind and clear goals are set to meet those objectives. The
timesheet is also always down appropriately and sections such as risks/ success are always met at a
good standard.
This is going well as the members who are stronger in certain areas stick to what they are most
comfortable with e.g one member focusing on things to do with success and fail criteria, one
member to deal with financials and estimates and another to fill in base requirements and potential
other requirements needed.
What’s not going well and why?
Tasks are always done late or last minute leading to some parts of the project being rushed or
overlooked sometimes, other times some project members don’t do as much work as others leaving
the other members having to do more work overall.
Suggestions/Issues
Suggestions for future group assignments
include regular meetings as to discuss and
delegate individual tasks early on to avoid
confusion
Timeliness – Managing time wisely and not
leaving important tasks to the last minute is
very clearly a large issue and needs to be
addressed to ensure higher quality work and to
make sure things aren’t overlooked.
Acceptance of Deliverables & Changes
Record the name, position, signature and date of all appropriate stakeholders signing this
performance report.
Name Position Signature Date
Radhu Supervisor 29/9/19
Nicky Supervisor 29/9/19
Timesheet – Justine
Day Date Project Process Group Task Description Start time End time Actual time spent Task Cost
Sat 28 Aug Execution Project Plan 19:00 23:00 4:00:00 $400.00
Sun 29 Aug Execution Project Plan, Final Draft 13:00 18:30 5:30:00 $550.00
Sun 29 Aug Execution Finalising Submission 19:00 20:30 1:30:00 $150.00
Hourly Rate
$100.00
Total Time Spent:
11:00:00
Total Current Spend:
$1,100.00
Timesheet – Haomin
Day Date Project Process Group Task Description Start time End time Actual time spent Task Cost
Fri 27 Sept Execution Staff Managment Plan 13:00 15:00
2:00:00 $180.00
Fri 27 Sept Execution Staff Managment Plan 19:00 21:30
2:30:00 $225.00
hourly rate:
$90.00
Total Time Spent:
4:30:00
Total Current Spend:
$405.00
Timesheet – Omair
Day Date Project Process Group Task Description Start time End time Actual time spent Task Cost
0:00:00 $0.00
0:00:00 $0.00
hourly rate:
$90.00
Total Time Spent:
00:00
Total Current Spend:
School of Vocational Business Education
Student Contribution Statement
Assessment information
Program Name: C5341 Diploma of Information Technology
Course(s) COSC 7370C Manage ICT Projects
Semester & Year Semester 1, 201
Teacher Name &
Contact Details
Nicky Sephton
nicky.sephton@rmit.edu.au
Student Name(s) / Number(s): Signature
Justine Tan
s3719279
Omair Qureshi
s3481011
Haomin QIAN
s371674
Project Manager: JustineTan
Team Name:
Student Contribution
Student Name(s) /
Number(s):
%
Contribution
List or description of the
tasks contributed
No of hours worked for this
assessment
Justine Tan
50 Organizing
Editing
Writing
Planning
11
Omair
0
Haomin QIAN
50 Editing
Writing
4.5
Team Contract
Project Name: NSB Mobile Studio
Project Team Members Names and Sign-off:
Name Sign-off on Team Contract
Justine
Haomin
Omair
Code of Conduct: As a project team, we will:
● Meet Project Deadlines
● Discuss any necessary changes
● Work together
Participation: We will:
● Work on delegated tasks
● Attend meetings or discussions
● Help others when needed
Communication: We will:
● Communicate on a regular basis
● Conduct communication and meeting in a professional manner
● Communicate with each other problems or issues when undertaking this project
Problem Solving: We will:
● Work out issues as a team
● Resolve any conflicts
● Delegate roles and tasks
Meeting Guidelines: We will:
● Meet regularly
● Discuss important tasks and points
● inform others of apologies or absentee