Assessment item 3 Charter Value: 30% Due date: 15-Jan-2018 Return date: 06-Feb-2018 Submission method options Alternative submission method Task You are to prepare and submit Assessment 3 as an...

Provides an MOV and identifies the target and expectations of all stakeholders in a suitable format.

(15 Marks)

The MOV illustrates the student’s detailed consideration of the target and a thorough analysis of the expectations of all stakeholders.
The format is logical, clear and well-structured.

The MOV illustrates the student’s detailed consideration of the target and an attempt at analysis of the expectations of all stakeholders is evident.
The format is logical and appropriate to the information presented.

The MOV illustrates the student’s generalised consideration of the target and an attempt at analysis of the expectations of most stakeholders is evident.
The format is suitable to the information presented.

The MOV illustrates the student’s generalised consideration of the target; however analysis of the expectations of all stakeholders is not clear.
The format is suitable to the information presented.

The MOV fails to cover one or more specified project requirements.

Utilising MS Project, provides a list of resources associated with the project – including reference to people, technology, and facilities and associated costs

(10 Marks)

Evidence of expertly utilising MS Project to create a comprehensive list of resources, demonstrating in-depth analysis of the project’s needs.

Evidence of expertly utilising MS Project to create a list of all resources required for the project; demonstrating analysis of the project’s needs.

Correctly utilising MS Project to provide a list which identifies most of the resources required for the project; some evidence of analysis of project needs.

Key resources are correctly identified and documented.

Key resources have not been identified.

Produces a Scope Management Plan (SCM).

(10 Marks)

Consistent application of industry standard language and formatting.

Well written with some demonstration of industry standard language and formatting.

Well written with demonstration of academic standard language and formatting.

Well written but lacks acceptable formatting.

Writing is not of an acceptable standard.

Utilising MS Project -evidences the processes involved with a WBS, including budget.

(20 Marks)

Demonstrates high level project management skills, integrating and applying project management tools in meaningful and purposeful ways towards completion of WBS design, correctly and comprehensively addressing all project requirements.

Demonstrates competent management skills, applying project management tools in meaningful and purposeful ways towards completion of the WBS design, correctly addresses the all project requirements.

Demonstrates essential management skills, applying project management tools in meaningful and purposeful ways towards completion of the WBS design. Essential project requirements addressed.

Demonstrates minimal management skills and needs some improvement in applying project management tools in meaningful and purposeful ways towards completion of WBS. Not all project requirements are clearly addressed.

The WBS design fails to correctly address one or more essential project requirements.

Provides a project risk analysis and plan using the risk identification framework as a basis for discussing alternate strategies for the management of such risks.

(15 Marks)

All steps in project risk analysis and alternate strategies are comprehensively discussed and presented in the context of the project, with evidence of thorough consideration of the framework to validate the alternatives.

All steps in project risk analysis and alternate strategies are clearly discussed and presented in the context of the project, with reference to the framework to validate the alternatives.

Evidence that key steps in project risk analysis and alternate strategies are discussed and presented in the context of the project, with some linkages back to the framework to validate the alternatives.

Key steps in project risk analysis and alternate strategies are accurately presented. Minimal reference to framework in the discussion presented.

One or more key steps in project risk analysis and alternate strategies are not presented.

Produces a quality management plan which includes a statement about the team’s philosophy and verification and validation activities.

(10 Marks)

All required project steps are correctly identified and appropriately contextualised for the selected project.

All required project steps are correctly identified and are applied to the selected project with some contextualisation.

All required project steps are correctly identified and are applied to the selected project.

Most required project steps are correctly identified and applied to the selected project.

Multiple project steps are missing or not applied to the selected project.

A closure checklist is produced alongside the development of a project evaluation that is evidenced by research.

(10 marks)

The closure checklist is detailed, and has been used accurately to close the project. The evaluation has been professionally documented and is evidenced by research.

The closure checklist is detailed, and has been used accurately to close the project. The evaluation has been well documented and is evidenced by research.

The closure checklist has been used appropriately to close the project, and the evaluation has been adequately documented and is evidenced by research.

The closure checklist has been used to close the project, and the evaluation has been addressed and is evidenced by research.

The closure checklist has not been addressed adequately, the evaluation is lacking detail and is not evidenced by research.

Referencing of sources (APA 6th ed citation) to reinforce findings.

(10 marks)

All written evidence is professionally communicated using correct referencing.

All written information is good with appropriate referencing

All written information is generally well organised but more clarity of communication is required in terms of referencing.

All written content is loosely connected, and there is ineffective use of referencing.

No apparent logical order of written content, and there is a lack of referencing.

INDEX

S.No

Topic

Page No

1

Team

3

2

Scope

3

3

Team Members and Responsibilities

4

4

Team Values

5

5

Meeting Guidelines

5

6

Team Objectives

6

7

Communication

6

8

Code of Conduct

6

9

Rules and Regulations

7

10

Team Sign off

7

11

Kick off Meetings

8,9,10,11

12

Learning Cycles

12,13

13

Stakeholders

14,15

14

Personal Reflection

16

15

References

17

TEAM

Name

Roles Assigned

Telephone

E-mail

Kanwalpreet Kaur

Management

420514591

[email protected]

Mandeep Kaur

Technical

414106334

[email protected]

Srikanth Chinthalapelli

Networking

424077373

[email protected]

SCOPE

Introduction

The Riverina Agriculture and Lifestyle Show (RALS) is strongly connected to Globex, the coordination and management part for the exhibitors is still managed by Globex. The RALS community have decided to extend their areas from lower to higher range and can be overseas too.For this venture, Globex is funding an online management system for the development of ALS in different locations. Currently, the process is done manually with RALS management staff. For such an expansion, they need an online booking system where data can be stored in spreadsheets and payments can be done online.

Having long term relationship with Virtucon, Globex has given this contract to develop such a management system. Virtucon is a consultancy which provides all the services and solutions with their professional technologists and business people and also helps various businesses to turn profitable by upgrading to technology.

Objectives

The online system of RALS would allow exhibitors to confirm their bookings and make online payments.The details of exhibitors can be digitally accessed and it can be scanned at the entry and therefore a number of reports can be created by the system.Although, booking via phone calls would still be one of the options but it is expected that this online system will reduce the admin staff of RALS committee for the event.

Scope

The scope of this project can be achieved by making an online system in a time phase of 11 months so that the management staff for booking can be reduced to minimum and online passes can be provided to the exhibitors.

TEAM MEMBERS AND RESPONSIBILITIES

Name

Skills

Responsibilities

Kanwalpreet Kaur

Plan and define scope,Time and cost estimation, Creating documentation, Leading team, Managing Risks and Issues,Working with vendors

Understanding the requirements, leading the project, assigning tasks to all team members, planning and organising the project, handling all the risks and issues in project or team, Having direct links with the vendors, Preparing all the reports, presentations and documentation of the project required.

Mandeep Kaur

Execution of the planning phase, Identifying best technology to be used,Handling designing and coding,Testing before final delivery.

Identifying project, compliance and handling the project backend and front-end, Understanding objectives, scope, time estimates, responsibilities and further using technologies accordingly.

Execution part of planning phase, identifying specifications.

Reporting project manager after every phase, Handling day to day execution part, Handling project deliverables, improvements required during the project, testing of the project before delivery

Srikanth Chinthalapelli

Installation of network devices, upgrading systems, providing security

Installing and configuring various network services and devices.

Maintenance of network and up gradation of systems

Monitoring performance

Select and implement security tools

Approving and selecting networking infrastructure.

TEAM VALUES

As said by (Anne Hoey, 2013), team values can be successful by proper management of project and different skills are required for it such as management of time, solving problems, organised, detailed and most importantly team work.

Commitments :

· Commitment should be done only to the task which can be accomplished.

· Realistic work needs to be in the reporting part.

· Volunteer needs to be active and ready with the answers of the team leaders.

· Any change should have clear effect with complete knowledge.

· Focus should be on the successful ideas of whole project.

Ground Rules

· Any team meeting should be confidential.

· Everyone’s viewpoints should be encouraged.

· Discussions needs to be tracked.

· Blaming others should be avoided.

· Every task should be assigned equally and need not to be biased.

MEETING GUIDELINES

· Every Monday is the time when we have to share our work done.

· Each meeting goal should be clear.

· The topics needs to be discussed with the team members.

· The deliverables should be approved by every team member.

· Timely delivery of every meeting agenda is expected.

· Expectation of everyone viewpoints and ideas.

· Attendance of every team member is a must.

· Full participation and response of every team member.

· Involvement in all the group discussions is expected.

· On time arrival is must.

· In between misbehaviour or indiscipline is not accepted.

· Ad-hoc meetings can be called on prior notice of 12 hours.

· There should be some target achieved before any meeting to occur.

· At the end of every meeting, there should be a conclusion.

GROUND RULES

· Everyone has the chance to speak.

· No interruption.

· Meetings should be held in polite manner.

· Ideas should not be criticised, instead they should be motivated.

TEAM OBJECTIVE

· Definition of project should be clear.

· Analysis of up and downs should be discussed.

· Examine each and every phase of the project in weekly meetings.

· Present each step of execution phase.

· Develop various approaches.

· Review outcomes.

· On-time delivery of project.

Communication

· A shared folder in Google Drive.

· Team Viewer for sharing screens.

· Face to face meetings.

· Video calling through Skype.

· Conference Calling.

· Emails.

CODE OF CONDUCT

According to ("ACS Code of Professional Conduct", 2014), there are a number of ethics that we need to follow :

· The Public Interest’s Primacy : Public Interests should be at the priority instead of business or personal interests.

· Quality of Life should be enhanced : The project done should be for the benefit and also improve the life quality.

· Honest : There should be transparency in terms of skills, products and services.

· Competency : The project needs to be done efficiently and skilfully.

· Development : Professional and personal development should be one of the priority.

· Professionalism : Work needs to be done respectfully and integrity should be enhanced.

Also,
PMI Code of Ethics and Professional Conduct
says that
vision and purpose
should be applied to all PMI members. Secondly, one has to be
responsible
for all the decisions to take place. Also, it is our duty to respect and show high regard to others and the resources. We should listen and
respect
everyone for all the decisions in professional manner.Than comes
Fairness, we need to fair enough for all our decisions.Our decision making should have to be free from favouritism and pre-justice.Last but not the least, we should be
honest
and truthful in our communications. Accurate information should be provided with respect to time.

RULES AND REGULATIONS

· Understanding of goals and commitment to achieve them on time is the basic rule for the project.

· Risks should be considered and team members should not be punished for disagreement.

· Listening to team members and understanding of everyone’s ideas is initialed.

· Every team member should commit to understand and maintain relationship guidelines.

· Every team member has their experiences and we should take advantage and make a better project.

· Innovation, New ideas, creative work is appreciated.

· Examining the team itself through different process and practices.

· Team agreement on every procedure to reduce the conflicts or clashes.

· One leader should be assigned for every decision recording or commitments.

· High Quality decisions with team members needs to be supported.

(M. Heathfield, 2017) said that for any teamwork to be successful, there should be functional and cooperative team members.

TEAM MEMBERS AND SIGN OFF

Name

Signature

Date (DD/MM/YYYY)

Management

Kanwalpreet Kaur

Kanwal

18/12/2017

Technical

Mandeep kaur

Mandeep

18/12/2017

Networking

Srikanth Chinthalapelli

Srikanth

18/12/2017

KICK OFF MEETINGS

Date :

30/01/2017

Organiser :

Kanwalpreet Kaur

Scribe :

Mandeep Kaur

Meeting Objective :

Introduction of the project and team members, assigning their roles and responsibilities

Agenda :

· The project scope and objectives needs to be accomplished.

· Assigning the roles of technical, networking team.

· Discussion on how the project comes out to be.

· Planning of the entire project with estimation of cost and time.

· Target dates needs to discussed.

· Identification of risks and challenges that can be faced.

Date and Time of next meeting :

26/03/2017

KICK OFF MEETINGS

Date :

26/03/2017

Organiser :

Mandeep Kaur

Scribe :

Kanwalpreet Kaur

Meeting Objective :

Technical team will present their layout to the entire project team and discuss about frontend and backend.

Agenda :

· IT Support needed for the tasks listed in project management.

· Updating the management on the progress, track of the website design, designed for the RALS.

· YIT Technical details of the web design page mockups are to be provided for approvals.

· RALS Management have to get this reviewed and approved so that the team working under will continue to complete the tasks

Date and Time of next meeting :

02/06/2017

KICK OFF MEETINGS

Date :

02/06/2017

Organiser :

Mandeep Kaur

Scribe :

Srikanth Chinthalapelli

Meeting Objective :

Checklist on network connection points along with security installs

Agenda :

· To review the status of the Network connectivity and security protocols needed for the website launch.

· To maintain open lines of communication and faster team building.

· To discuss roles and responsibilities of every individual or team members assigned to the tasks.

· Listing out next week tasks under Networking, estimating the manpower/tasks assigned.

Date and Time of next meeting :

15/08/2017

KICK OFF MEETINGS

Date :

15/08/2017

Organiser :

Srikanth Chinthalapelli

Scribe :

Mandeep Kaur

Meeting Objective :

Network & Security - IT support needed for the web page

Agenda :

· Estimating IT support for the network connectivity and relative change in application.

· Communicating the output of this meeting to the other stakeholders.

· Listing out Risks & Support needed to address them.

· IT Support team assignees for the tasks created under Network.

Date and Time of next meeting :

11/10/2017

KICK OFF MEETINGS

Date :

11/10/2017

Organiser :

Kanwalpreet Kaur

Scribe :

Srikanth Chinthalapelli

Meeting Objective :

Networking, Security & Documentation work for upcoming warranty period and Prod Live

Agenda :

· Review of the weekly tasks assigned to Networking team, going through high risk items for the go live.

· Website flow test with dummy logins, payments & transactions are to be considered and added to go – live.

· Final Review of the pending items under Project Plan and estimate the work for the upcoming weeks.

· Server setup, backend DB, connectivity and Support document were to be attached to the HELP Button on the website, for future communications.

Date and Time of next meeting :

30/11/2017

KICK OFF MEETINGS

Date :

30/11/2017

Organiser :

Mandeep Kaur

Scribe :

Kanwalpreet Kaur

Meeting Objective :

Status Updates, next steps, pending tasks and blockers

Agenda :

· Updating the Project Management Office on the tasks completed, with pending items.

· Discussing on the next upcoming tasks along with IT resources needed for the future work.

· Technical difficulties are explained and made it a point to make sure reaches out to Management, as a Risk.

· RALS met with both the teams and had come on sync with the updates, tracking, website draft flow.

Project Delivery Date

30/12/2017

Learning Cycles

Facts

Assumptions

Questions

Seats arrangement and allocation has to be coordinated and updated instantly

Seat assignments might change even after selecting and at the final checkout due to parallel transactions

Do we need to lock the seats until the final checkout is done so that there will be no situation of disappointment for Customers?

Exhibitor Details need to be furnished before the booking is made to validate the authenticity

There can be an option to fill only few details like Name & Contact, this should also suffice the authenticity of Admission,

Can we place other fields as optional like Address, if so do we need to add any ID verification documents list as an alternative?

Seat arrangements should be in spreadsheet format, easier to track/update/ online

The format of the seats can be in the order of first come first serve basis, or updating them on the fly

Being new to the online system, the seat arrangements should be aligned to make sure the dates /timings are getting updated?

Online payment system needs a secured authorization module

Automated payments might be of various types like connecting to 3^rd
party payment application

Do we need to add all modes of payments in the website?

Login Credentials are required to access and make payments

Accessing website can be done with Guest Option or sometimes with Login credentials

Making login credentials mandatory might be inconvenient to the customers, need options?

Once Online, the system will generate reports on the percentage of show admission

We can generate diff sets of reports, audit, finance, seat capacity, etc.

Do we need to add separate section on website for this type of reporting?

A Database has to be created in order to maintain the seat allocation sheets, payment transactions, login users, etc.

A storage location might be needed to enter/access the data containing different sets of reports, this could be a shared location as well

We would need privacy authorization from online users to maintain/store data?

Employee cut down will happen once the system goes online

The staff who used to take care of admissions, entry checkpoints, will have to be shifted to different departments

We might need the staff until the system is fully on its own with no issues?

IT Facility Building have to be setup within the campus or admissions building

There can be a central location in nearby area or can be given to 3^rd
party to maintain this so that no facility is needed.

Where ever the facility is setup, the access to that should be restricted, so do we need to get a list and the same has to be maintained by a lead?

The system should be running round the clock to make it accessible to the exhibitors

The system can go under maintenance during some days that can be notified in advance

Do we need to list out maintenance dates, timings to post ahead on the system so that exhibitors are aware?

Stakeholders

Name

Information

Frequency

Location

Purpose

Mechanism

Globex (RALS)

Project manager

04/02/2017

Office

Discuss important points related to project like-

· How much time it will take to complete.

· Cost of the project.

· Quality of the project.

· Techniques that will be used for the project.

Power point slides

Senior management

Project manager

15/02/2017

Coffee shop

Share ideas of the project and discuss how it will benefit to the organisation. Moreover, take opinion from seniors related to

· project plan

· schedule

Files

Globex (RALS)

Project Manager

11/04/2017

Conference hall

· To show the rough layout of the project and check stakeholders satisfaction.

· Let them know with the latest trends of the market and what is used for their product.

· If, they need any change then note-down.

Presentation

through slides.

Exhibitors

Project team

28/04/2017

Online

To understand what are the expectations clients have from this project.

Set the final requirements and scope for the project.

Feedback form

Project manager

Program developer

17/10/2017

Conference hall

To have a look of the project before testing.

Technical

Agriculture department

RALS

21/11/2017

Office

To know about the project like

· what are the benefits of this project to agriculture field.

· how it will work.

Oral communication

Project

testers

Program developer

24/10/2017

Lab

To testers explain few things related to project like

· what softwares they used.

· which coding and tools used to design the website.

· explain requirements of the client.

· and provide documentation.

Oral and files

Personal Reflection

Understanding

According to JR Turner, R Muller-2005: The project management completely depends on the leadership style and it results in great output of the project. The coordination and communication skills are the keys to success and the project design, plan and implementation are crucial for starting a project

According to Cicmil.S (2006): The project manager plays a important role in the whole project as he/she has to take the initiation of the project. He has to control the risk management factors and to be clear in explaining each and every team members role in the project.

Comparison

As a Network Analyst in this project, the experience with the team was great and had a chance to put up my skills, techniques and ideas. I have joined the team a bit late and faced a problem of understanding and the project manager as well as another team mate helped me a lot in understanding the project. After understanding the project, I have done my job in giving fantastic output to the team. During Analysation experience, the project design, plan & implementation were the key factors, which driven the keys to success The overall experience with the project work was a learning curve; coordination and communication with the team and I have improved my technical skills in doing this project.

Knowledge

(El-Sabaa, 2001) The two main perspectives are pressure handling and risk management. If any issues comes in the project, project manager should be in the position to overcome it and the basic communication skills and good thinking leads to great output of the project. The practical and technical knowledge also plays important part in the project.

References

1. Anne Hoey, J. (2013).The Top 7 Core Project Management Values.The Top 7 Core Project Management Values. Retrieved 27 April 2013, from
http://www.projectmanage.com/the-top-7-core-project-management-values/

2.
ACS Code of Professional Conduct. (2014).ACS Code of Professional Conduct. Retrieved April 2014, from
https://www.acs.org.au/content/dam/acs/acs-documents/ACS%20Code-of-Professional-Conduct_v2.1.pdf

3.
PMI Code of Ethics and Professional Conduct.Code of Ethics and Professional Conduct. Retrieved from
https://www.pmi.org/-/media/pmi/documents/public/pdf/ethics/pmi-code-of-ethics.pdf

4. M. Heathfield, S. (2017).10 Tips for Better Teamwork. Retrieved 1 August 2017, from
https://www.thebalance.com/tips-for-better-teamwork-1919225

5. Kumar, & Victoria S. (2009).Essential leadership skills for project managers. Retrieved 2009, from
https://www.pmi.org/learning/library/essential-leadership-skills-project-managers-6699

6. Project Management Institute. (2008).A guide to the project management body of knowledge (PMBOK®guide)(4th ed.). Newtown Square, PA: Project Management Institute.

7. Daniel. (2012).Project Manager’s Top 10 Skills To Be An Effective Leader. Retrieved 19 June 2012, from
http://www.mymanagementguide.com/project-managers-leadership-skills

8. Alison Doyle. (2017).Project Manager Skills List and Examples. Retrieved 14 July 2017, from
https://www.thebalance.com/essential-project-manager-skills-2062461

9. Michele McDonough. (2012).10 Critical PM Skills: How Do You Rate?. Retrieved 20 May 2012, from
http://www.brighthubpm.com/certification/105665-ten-critical-pm-skills-how-do-you-rate