Project Scope Assignment 1 2016-2017
The aim of this assignment is for you to put into practice the skills and knowledge that you have learnt in the module. You are provided on the KLE with an initial outline from the client of what they require. Based on that information and the information you gain from interviewing the client you are required to provide the following:-
A scope statement
A work breakdown structure
A scope management plan
A list of the stakeholders for this project
An initial stakeholder communication management analysis
The Scenario
You are being asked to undertake the entire conference organisation for a two day conference to be held at Keele in the School of Computing and Mathematics. You will be given access to an experienced conference organiser who will be able to provide you with information relevant to your undertaking this project.
You need to concern yourself with the actual running of the conference, but not with paper management.
You will need to liaise with Keele Hospitality in terms of numbers attending, booking refreshments for during the conference and specifically for a conference dinner on day 1 of the conference.
You have been asked to undertake this activity but the client requires that you have approval for your project plans before any further project activities occur. In order to give their approval the client requires the following information:
A scope statement
A work breakdown structure (high level)
A scope management plan
A list of the stakeholders for this project
An initial stakeholder communication management analysis
You also need to supply
- An outline of the process you would use to manage risks to the
successful completion of the study [10%] - A reflection on how the errors were addressed and how they occurred [10%]
Marking Scheme
The detailed guidelines are provided under marking criteria. The percentage breakdown within topics is detailed below
| Area | Percentage of total mark |
| scope statement | 30 |
| work breakdown structure | 15 |
| scope management plan | 20 |
| list of stakeholders stakeholder analysis | 5 10 |
| Risk Process | 10 |
| Reflection | 10 |
Submission Details
Individually submit a single word or PDF document via the drop box on the KLE. The document must be submitted by 1300 on June 8th 2017.
If you are unsure on the quantity of work to be completed, please consult the lecturers in the tutorial sessions.
Marking Criteria
Scope Statement
The scope document will be assessed against its coverage, clarity, consistency and realism.
An excellent scope statement will be consistent with itself and show an understanding of all elements.
A merit scope statement will have all elements there but will have a small level of inconsistency and error.
A passing scope statement will have all elements there but will have a higher level of inconsistency and error when compared to a merit level scope statement.
A failing scope statement will be missing elements and/or contain significant inconsistencies and errors.
Work Breakdown Structure
The work breakdown structure will be assessed on the basis of the completeness and logical structure.
An excellent work breakdown structure (WBS) will have elements to the appropriate level of abstraction and will provide a complete coverage of all the activities involved in the potential process.
A merit WBS will have all elements there but will have a small level of inconsistency and error
A passing WBS will have all elements there but will have a higher level of inconsistency and error than was present in a merit level response.
A failing WBS will be missing elements and/or contain significant inconsistencies and errors.
Scope Management Plan
The scope management plan will be assessed on the basis of how well it addresses the elements of the scope management plan other than scope statement.
An excellent scope management plan will cover all the elements with a reasonable level of detail and applicable approaches to the main activities documented in the scope management plan.
A merit scope management plan will have all elements there but will have a small level of inconsistency and error.
A passing scope management plan will have the majority of the elements, but there will be a higher degree of inconsistency when compared to a merit plan
A failing scope management plan will be missing a majority of elements and/or contain significant inconsistencies and errors.
Stakeholder Communication Management List and Analysis
The list of stakeholders is marked on completeness.
The Stakeholder Analysis is assessed on your evaluation of the different stakeholders and your chosen methods for communication.
An excellent list of stakeholders will identify all relevant stakeholders
An excellent analysis will correctly position these within the matrix and identify appropriate approaches to communication.
A merit list of stakeholders will be missing no more than 1 of the potential stakeholders.
A merit analysis will have only 1 or 2 stakeholders missing or incorrectly positioned on the matrix and will have an appropriate approach to communication taking due account of any mis-positioning.
A passing list of stakeholders will have the majority of stakeholders identified.
A passing analysis will have several missing or mis-positioned stakeholders on the matrix and only some appropriate communication approaches taking due account of any mis-positioning.
A failing list of stakeholders will only have a minority of stakeholders identified.
A failing analysis will have the majority of stakeholders missing and/or mis-positioned and communication approaches will be inappropriate having taken due account of any mis-positioning
Risk Process
An excellent description of the approach to managing risk will demonstrate a sound understanding of the Risk, Cost and Time Management elements of project management.
A passing description of the approach to managing risk will demonstrate a reasonable understanding of the Risk, Cost and Time Management elements of project management.
A failing description of the approach to managing risk will demonstrate no clear understanding of the Risk, Cost and Time Management elements of project management.
Reflection on Errors
An excellent reflection on the error will consider all elements of the feedback, identify root causes of the problem and address these with the changes made to the submission
A merit reflection whilst still addressing all elements of the feedback will not identify all root causes but will address those they have identified fully
A passing level reflection will not address all elements of the feedback nor identify all root causes but will address those they have identified
A failing reflection will fail to meet any of the above criteria.
Introduction
Scope Statement
- Scope Objectives
- Acceptance Criteria
- Project Milestones
- Deliverables
- Technical Requirements
- Project Exclusions
- Constraint
- Assumptions
High Level Work Breakdown Structure
Key date to be included in the Work Breakdown Structure
28/10/16: Meeting with Client
14/11/16: Start Date
10/4/17: Hand in the project
17/4/17: Training Session
24/4/17: Day 1 0f Conference
25/4/17: Day 2 of Conference (The End)
8/5/17: Assets handover (2 weeks after the Conference)
Scope Management Plan
Scope Management Roles and Responsibilities
Scope Management Planning
Scope Control
Scope Verification
Approvals
List of Stakeholder holders for this project
Client, Project Managers, Suppliers, Keele Hospitality, Keynote Speakers, Guests, Keele Staff, Volunteer, 24 Hour Receptionist, Security, On Campus Drivers, Doctors, Administrator, Accommodation and Hotel, Technical Team, Organisational Experts, Keele Office Staff.
| Stakeholder Analysis Part 1 | |
| Stakeholders Name | Roles Within The Project |
| Client | |
| Project Managers | |
| Suppliers | |
| Keele Hospitality | |
| Keynote Speakers | |
| Guests | |
| Keele Staff | |
| Volunteer | |
| 24 Hour Receptionist | |
| Security | |
| On Campus Drivers | |
| Doctors | |
| Administrator | |
| Accommodation and Hotel | |
| Technical Team | |
| Organisational Experts | |
| Keele Office Staff | |
| Stakeholder Analysis Part 2 | ||||||
| Stakeholders Name | ||||||
| Client | ||||||
| Project Managers | ||||||
| Suppliers | ||||||
| Keele Hospitality | ||||||
| Keynote Speakers | ||||||
| Guests | ||||||
| Keele Staff | ||||||
| Volunteer | ||||||
| 24 Hour Receptionist | ||||||
| Security | ||||||
| On Campus Drivers | ||||||
| Doctors | ||||||
| Administrator | ||||||
| Accommodation and Hotel | ||||||
| Technical Team | ||||||
| Organisational Experts | ||||||
| Keele Office Staff | ||||||
Risk Process
| Project Risk Management Paradigm | |
| Communicate | Steps |
| Identify | |
| Analyse | |
| Plan | |
| Implement | |
| Track/Control | |
Reflections
