Cover Sheet
Project Name: | |||||
Date: | Release: | Draft/Final | |||
Author: | |||||
Owner: | |||||
Client: | |||||
Document Number: | |||||
Note: This document is only valid on the day it was printed | |||||
Revision History | |||||
Date of next revision: | |||||
Revision Date | Previous Revision Date | Summary of changes | Changes Marked | ||
Approvals | |||||
This Document requires the following approvals. A signed Copy should be placed in the project files. | |||||
Name | Signature | Title | Date of Issue | Version | |
Distribution | |||||
This Document should be distributed to: | |||||
Name | Title | Date of Issue | Version |
Overview
Overview | ||
Purpose | A Risk Register provides a record of identified risks relating to the project, including their status and history. It is used to capture and maintain information on all of the identified threats and opportunities relating to the project. | |
Contents | Page 3 contains the Risk Log | |
Advice | Derivation: - The composition, format and presentation of the Risk Register will be derived from the Risk Management Strategy - Entries are made on the Risk Register once a new risk has been identified - There may be one or more risks inherent in the project mandate - New risks may be discovered when creating the Project Brief, designing and appointing the project management team, establishing the project’s controls and developing its plans, when issuing Work Packages, when reviewing Work Package status, or when reviewing stage status - Daily Log/Issue Register - often issues raised to the Project Manager and captured in the Daily Log or Issue Register are actually risks and only identified as such after further examination. | |
Format and Presentation: A Risk Register can take a number of formats, including: - Document, spreadsheet or database - Stand-alone register or a carry forward in progress review minutes - Entry in a project management tool - Part of an integrated project register for all risks, actions, decisions, assumptions, issues, lessons etc. | ||
Quality Criteria: - The status indicates whether action has been taken - Risks are uniquely identified, including information about which product they refer to - Access to the Risk Register is controlled and it is kept in a safe place. |
Risk Register
Risk ID | Author | Date Registered | Risk Category | Description | Impact | Probability | Expected Value | Proximity | Risk Response Categories | Risk Response | Risk Status | Risk Owner | Risk Actionee | |||||
Cause | Event | Effect | Inherent | Residual | Inherent | Residual | Inherent | Residual | ||||||||||
1 | ||||||||||||||||||
2 | ||||||||||||||||||
3 | ||||||||||||||||||
4 | ||||||||||||||||||
5 | ||||||||||||||||||
6 | ||||||||||||||||||
7 | ||||||||||||||||||
8 | ||||||||||||||||||
9 | ||||||||||||||||||
10 | ||||||||||||||||||
11 | ||||||||||||||||||
12 | ||||||||||||||||||
13 | ||||||||||||||||||
14 | ||||||||||||||||||
15 | ||||||||||||||||||
16 | ||||||||||||||||||
17 | ||||||||||||||||||
18 | ||||||||||||||||||
19 | ||||||||||||||||||
20 | ||||||||||||||||||
21 | ||||||||||||||||||
22 | ||||||||||||||||||
23 | ||||||||||||||||||
24 | ||||||||||||||||||
25 | ||||||||||||||||||
26 | ||||||||||||||||||
27 | ||||||||||||||||||
28 | ||||||||||||||||||
29 | ||||||||||||||||||
30 | ||||||||||||||||||
31 | ||||||||||||||||||
32 | ||||||||||||||||||
33 | ||||||||||||||||||
34 | ||||||||||||||||||
35 |
Running Header
Module #
Course Name
Your Name
Keiser University
Date
Abstract
A one paragraph quick summary of the paper goes here. It’s not an introduction to the
topic it’s a summary of the whole paper. Make sure to Double Space.
Title of Your Paper
Note this paper is only for how to set up a paper, it’s not an example of what you need to do to write a paper. Your paper should follow APA format. NOTE ALL new paragraphs are indented five spaces on the first line. This sample is the layout and format and references need to be cited properly in the body (Author, Year). Do not simply list out a website (
www.cdc.gov/saftey
) for example is NOT correct. This section is your introduction and you should always make sure to give an introduction with a basic overview of your topic. Comment by User: NOTICE each NEW paragraph is indented 5 Comment by User: Notice never any additional spaces after you start a new paragraph.
In this area, you will give a background and introduction to the scenario. Provide a general overview to the scenario as well as the key setting and personnel involved. Include all personnel you met with as you worked toward writing your recommendation. Describe your role as a consultant. Write your problem statement here.
Total Quality Management
In this area provide a define Total Quality Management (TQM) as it relates to health care settings. Be clear and specific regarding health care quality and how TQM concepts help improve quality. Cite scholarly and peer reviewed sources.
Management Role
Clearly describe what role does management play in play in TQM? How does TQM address internal customer needs and who are they in healthcare?
Data Collection in TQM
Describe some of the key TQM data and how it’s collected in TQM? What role does TQM play for patient safety? What recommendations do you have for the three key areas that need improvement based on the scenario’s patient survey? How is data collected in TQM?
Donabedian Model
Define the Donabedian model and explain it. Then, provide an over view of this model’s relevancy to the urgent care facility. Describe the four key areas found in the scenario. How does one of the four C’s, “correctness”, address medical errors? What are care outcomes and what types of standards must be met to ensure quality care? What role does TQM play in patient safety?
Patient Satisfaction
In this area provide an overview of the patient satisfaction issues noted in the scenario. Describe the four key areas found in the scenario and describe how correctness addresses medical errors. Include your analysis of how the rising cost of healthcare affect patient satisfaction.
Patient Safety
Define care outcomes and standards that ensure quality care. Describe the role of TQM in patient safety.
Patient Satisfaction Recommendations
Make recommendations to address the issue of rising costs of health care. Be specific to the patient. Research options for patients/customers to help overcome rising costs of health care. Make recommendations for the facility as well. What recommendations do you have for the three key areas that need improvement on the scenario’s patient survey?
Make recommendations for the facility as well.
Regulatory Bodies
Describe the connections between policy and social forces and access to healthcare. Include an assessment of the given scenario and the Iron Triangle. How does the rising cost of healthcare affect patient satisfaction? What recommendations can be made to address these costs? Describe at least on regulatory body or policy that affects healthcare to healthcare.
Communication in Health Care
Based on the scenario and additional research, what are some key areas of communication in health care needed to ensure quality and patient satisfaction? Describe what issues with communication the urgent care facility facing? What are your recommendations to reduce the patient wait time? What are care outcomes and types of standards that must be met to ensure quality care? What role does TQM use in patient safety?
Recommendations for Communication Improvement
Based on your analysis of the scenario and additional research, make recommendation for improvement. What recommendations do you have for the three key areas that need improvement based on the Customer Service scenario's patient survey?
Critical Practice Guidelines
Explain critical practice guidelines and how they can influence quality of care and improve physician efficiency. Where can physicians easily find evidence based practice guidelines?
Patient Focused vs. Technology Focused
Describe the difference between a patient-focused philosophy of treatment and a technology-focused one? Provide examples from Beth-Isreal in Boston and Cedars-Sinai in LA.
Conclusion
Your paper should have always end with a conclusion. Here you will tie together the key concepts discussed and discuss any assumptions such as barriers, success rates or other pertinent information. Bottom line – summarize it all here. SCROLL DOWN TO SEE REFERENCE PAGE.
References
Arakji, R. Y., & Lang, K. R. (2008). Avatar business value analysis: A method for the evaluation
of business value creation in virtual commerce. Journal of Electronic Commerce
Research, 9, 207-218. Retrieved from http://www.csulb.edu/journals/jecr/
Bower, B. (2008, Feb. 9). Dawn of the city: Excavations prompt a revolution in thinking about
the earliest cities. Science News, 173(6), 90-92. Retrieved from
http://www.sciencenewsmagazine.org/
NOTE these are samples of what references LOOK LIKE - you will use your OWN references in this sample format.
7
<Insert Project Name> Created/updated <date>
PRINCE2™- Plan
Project Name: |
|
||
Date: |
|
Release: |
Draft/Final |
Author:
|
|
||
Owner:
|
|
||
Client:
|
|
||
Document Number: |
|
Note: This document is only valid on the day it was printed
Revision History
Date of next revision:
Revision Date |
Previous Revision Date |
Summary of Changes |
Changes Marked |
|
|
|
|
|
|
|
|
|
|
|
|
Approvals
This document requires the following approvals. A signed copy should be placed in the project files.
Name |
Signature |
Title |
Date of Issue |
Version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
This document has been distributed to:
Name |
Title |
Date of Issue |
Version |
|
|
|
|
|
|
|
|
Overview
Purpose |
A plan provides a statement of how and when objectives are to be achieved, by showing the major products, activities and resources required for the scope of the plan. In PRINCE2, there are three levels of plan: project, stage and team. Team Plans are optional and may not need to follow the same composition as a Project Plan or Stage Plan. An Exception Plan is created at the same level as the plan that it is replacing. A Project Plan provides the Business Case with planned costs, and it identifies the management stages and other major control points. It is used by the Project Board as a baseline against which to monitor project progress. Stage Plans cover the products, resources, activities and controls specific to the stage and are used as a baseline against which to monitor stage progress. Team Plans (if used) could comprise just a schedule appended to the Work Package(s) assigned to the Team Manager. A plan should cover not just the activities to create products but also the activities to manage product creation - including activities for assurance, quality management, risk management, configuration management, communication and any other project controls required.
|
Contents |
The Plan should cover the following topics. 4Plan Description Plan Prerequisites 4 External Dependencies 4 Planning Assumptions 4 Lessons Incorporated 5 Monitoring and Control 5 Budgets 5 Tolerances 5 Product Descriptions 5 Schedule 6
|
Advice |
The Plan is derived from the Project Brief, Quality Management Strategy (for quality management activities to be included in the plan), Risk Management Strategy (for risk management activities to be included in the plan), Communication Management Strategy (for communication management activities to be included in the plan), Configuration Management Strategy (for configuration management activities to be included in the plan), Resource availability, and Registers and logs. The Plan can take a number of formats including: A stand-alone document or a section of the Project Initiation Documentation; Document, spreadsheet, presentation slides or mindmap; Entry in a project management tool. The schedule may be in the form of a product checklist (which is a list of the products to be delivered within the scope of the plan, together with key status dates such as draft ready, quality inspected, approved etc.) or the output from a project planning tool. The following quality criteria should be observed: · The plan is achievable · Estimates are based on consultation with the resources, who will undertake the work, and/or historical data · Team Managers agree that their part of the plan is achievable · It is planned to an appropriate level of detail (not too much, not too little) · The plan conforms to required corporate or programme standards · The plan incorporates lessons from previous projects · The plan incorporates any legal requirements · The Plan covers management and control activities (such as quality) as well as the activities to create the products in scope · The plan supports the Quality Management Strategy, Configuration Management Strategy, Risk Management Strategy, Communication Management Strategy and project approach · The plan supports the management controls defined in the Project Initiation Documentation
|
Plan Description
(Covering a brief description of what the plan encompasses (i.e. project, stage, team, exception) and the planning approach)
Plan Prerequisites
(Containing any fundamental aspects that must be in place, and remain in place, for the plan to succeed)
External Dependencies
(That may influence the plan)
Planning Assumptions
(Upon which the plan is based)
Lessons Incorporated
(Details of relevant lessons from previous similar projects, which have been reviewed and accommodated within this plan)
Monitoring and Control
(Details of how the plan will be monitored and controlled)
Budgets
(Covering time and cost, including provisions for risks and changes)
Product Description (PBS)
(Covering the products within the scope of the plan)
Schedule
This may include or reference graphical representations of the following:
· WBS · Gantt or bar chart
|
· Activity Network
|
|
|
· Table of resource requirements – by resource type (e.g. four engineers, one test manager, one business analyst) |
· Table of requested/assigned specific resources –by name (e.g. Nikki, Jay, Karolina) |
© Kingston Business School.
PRINCE2™ is a Trade Mark of the Office of Government Commerce
page 7 of 7
<Insert Project Name> Created/updated <date>
PRINCE2™- Business Case
Project Name: |
|
||
Date: |
|
Release: |
Draft/Final |
Author:
|
|
||
Owner:
|
|
||
Client:
|
|
||
Document Number: |
|
Note: This document is only valid on the day it was printed
Revision History
Date of next revision:
Revision Date |
Previous Revision Date |
Summary of Changes |
Changes Marked |
|
|
|
|
|
|
|
|
|
|
|
|
Approvals
This document requires the following approvals. A signed copy should be placed in the project files.
Name |
Signature |
Title |
Date of Issue |
Version |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
This document has been distributed to:
Name |
Title |
Date of Issue |
Version |
|
|
|
|
|
|
|
|
Overview
Purpose |
A Business Case is used to document the justification for the undertaking of a project, based on the estimated costs (of development, implementation and incremental ongoing operations and maintenance costs) against the anticipated benefits to be gained and offset by any associated risks. The outline Business Case is developed in the Starting up a Project process and refined by the Initiating a Project process. The Directing a Project process covers the approval and re-affirmation of the Business Case. The Business Case is used by the Controlling a Stage process when assessing impacts of issues and risks. It is reviewed and updated at the end of each management stage by the Managing a Stage Boundary process, and at the end of the project by the Closing a Project process.
|
Contents |
The Business Case should cover the following topics. 3Executive Summary Reasons 3 Business Options 4 Expected Benefits 4 Expected Dis-benefits 4 Timescale 4 Costs 5 Investment Appraisal 5 Major Risks 5
|
Advice |
The Business Case is derived from the: Project mandate and Project Brief – reasons; Project Plan - costs and timescales; The Senior User(s) - expected benefits; The Executive - value for money; Risk Register and Issue Register. The Business Case can take a number of formats, including: Document, spreadsheet or presentation slides; Entry in a project management tool. The following quality criteria should be observed: · The reasons for the project must be consistent with the corporate or programme strategy · The Project Plan and Business Case must be aligned · The benefits should be clearly identified and justified · It should be clear how the benefits will be realized · It should be clear what will define a successful outcome · It should be clear what the preferred business option is, and why · Where external procurement is required, it should be clear what the preferred sourcing option is, and why · It should be clear how any necessary funding will be obtained · The Business Case includes non-financial, as well as financial, criteria · The Business Case includes operations and maintenance costs and risks, as well as project costs and risks · The Business Case conforms to organizational accounting standards (e.g. break-even analysis and cash flow conventions) · The major risks faced by the project are explicitly stated, together with any proposed responses. |
Executive Summary
(Highlight the key points in the Business Case, which should include important benefits and the return on investment (ROI))
Reasons
(Defines the reasons for undertaking the project and explains how the project will enable the achievement of corporate strategies and objectives)
Business Options
(Analysis and reasoned recommendation for the base business options of: do nothing, do the minimal or do something)
Expected Benefits
(The benefits that the project will deliver expressed in measurable terms against the situation as it exists prior to the project. Benefits should be both qualitative and quantitative. They should be aligned to corporate or programme benefits. Tolerances should be set for each benefit and for the aggregated benefit. Any benefits realization requirements should be stated)
Expected Dis-benefits
(Outcomes perceived as negative by one or more stakeholders. Dis-benefits are actual consequences of an activity whereas, by definition, a risk has some uncertainty about whether it will materialize. For example, a decision to merge two elements of an organization onto a new site may have benefits (e.g. better joint working), costs (e.g. expanding one of the two sites) and dis-benefits (e.g. drop in productivity during the merger). Dis-benefits need to be valued and incorporated into the investment appraisal)
Timescale
(The period over which the project will run (summary of the Project Plan) and the period over which the benefits will be realized. This information is subsequently used to help timing decisions when planning (Project Plan, Stage Plan and Benefits Review Plan))
Costs
(A summary of the project costs (taken from the Project Plan), the ongoing operations and maintenance costs and their funding arrangements)
Investment Appraisal
(Compares the aggregated benefits and dis-benefits to the project costs (extracted from the Project Plan) and ongoing incremental operations and maintenance costs. The analysis may use techniques such as cash flow statement, ROI, net present value, internal rate of return and payback period. The objective is to be able to define the value of a project as an investment. The investment appraisal should address how the project will be funded)
Major Risks
(Gives a summary of the key risks associated with the project together with the likely impact and plans should they occur)
© Kingston Business School.
PRINCE2™ is a Trade Mark of the Office of Government Commerce
page 3 of 6
BB7018: International Project Management and Practice
Consultancy Group Report: Marking Criteria
LEARNING OUTCOME |
CRITERIA |
70+ % |
60% - 69% |
50% - 59% |
40 - 49% |
Below 40% |
1. Use and understand the applicability of various project management approaches and models 2. Advise on selection of the best strategy / projects in terms of added value 3. Use and understand various tools and techniques for project planning and monitoring 4. Contrast the suitability of different approaches to managing project budgets, quality and risk 5. Critically appraise the various approaches to managing project teams and oneself
|
Business Case
|
Fully justified topic, with aims and questions excellently articulated and reviewed within context of organisation and academic debate.
|
Addressed the purpose of the exercise coherently with some imagination and within the organisational context.
|
Most of the work is focused on the aims and themes of the exercise.
|
Some of the work is focused on the aims and themes of the exercise.
|
Fails to address the task set.
|
1. Use and understand the applicability of various project management approaches and models 2. Advise on selection of the best strategy / projects in terms of added value 3. Use and understand various tools and techniques for project planning and monitoring 4. Contrast the suitability of different approaches to managing project budgets, quality and risk 5. Critically appraise the various approaches to managing project teams and oneself . |
Project Plan
|
Shows a thorough, polished and imaginative approach to the topic.
|
Carefully and logically organised. Very good use of figures, diagrams.
|
Good attempt to organise in a logical manner. |
Some attempt to organise in a logical manner.
|
Disorganised and/or incoherent analysis.
|
2. Advise on selection of the best strategy / projects in terms of added value 3. Use and understand various tools and techniques for project planning and monitoring 4. Contrast the suitability of different approaches to managing project budgets, quality and risk
|
Risk Management Strategy |
Critical review of theory or models.
|
Very good review of theory or models.
|
Good review of theory or models.
|
Fair review of theory or models.
|
List of sources, rather than review.
|
1. Use and understand the applicability of various project management approaches and models 2. Advise on selection of the best strategy / projects in terms of added value 3. Use and understand various tools and techniques for project planning and monitoring 4. Contrast the suitability of different approaches to managing project budgets, quality and risk 5. Critically appraise the various approaches to managing project teams and oneself
|
Risk Register |
Justifies approach taken. Highly valuable to the organisation in terms of identification, assessment and implementation planning.
|
Justifies approach taken. Risk identification, assessment and implementation planning are accurately analysed and reported clearly in relation to organisational context.
|
Approach taken is sufficient. The risk management process is not in-depth analysed
|
The risks are mentioned, showing only a marginal application of the risk management process.
|
Fails to identify, assess, and implement risks. |
Elements of Business Case (BC) |
Max |
Business Case
Executive Summary and Reasons |
35%
5 |
Business Options |
10 |
Expected Benefits |
5 |
Timescale and Costs (from Project Plan) |
10 |
Investment Appraisal |
5 |
Project Plan
Product Breakdown Structure (PBS) |
40%
5 |
Work Breakdown Structure (WBS) |
10 |
Estimation of Resources Needed (staff, materials, etc.) |
5 |
Network Diagrams, and Critical Path Analysis |
10 |
Gantt |
5 |
Planning Assumptions |
5 |
Risk Management Strategy
Identify, Assess, Plan, Implement, Communicate Elements
|
10%
10% |
Risk Register |
15% |
Total |
100 |
RETAKE ASSIGNMENT BB7018 - CASE STUDY
Date Set: Retake period 2021
Date Due: You must upload an electronic copy to Canvas by 5th of May 2021 by 5pm.
Assignment: Individual Retake Coursework 100%
You have been employed as a Consultant by Kingston University London to organise a Gala Dinner to celebrate the start of the academic year. The event will take place on Friday 24th September 2021 and it is open to all members of staff employed by Kingston University. You are to organise all aspects of the event including, booking the entertainment, advertising and ticketing. The client requirement is to break even and make profit by delivering a successful event.
Prepare a Business Case (1500 words +/- 10%), Project Plan report (1500 words +/- 10%) and Risk Register following PRINCE2 Methodology to present to your client. This is the “who, why, and what” part of the project. It defines all major aspects of the project and forms the basis for its planning and management and also the assessment of overall success. Remember that the quality offered and overall net profit will convince your client to buy your idea.
Notes:
· You need to define when the project will start. You may select the start date.
· Ticket price you offer is entirely up to you, but ticket price per person would never been more than £45 per person. This has to cover your costs and make the desired profit if no other income channels are available.
· Assume that the venue has max capacity of 300 people. Base case scenario for the event is predicted to be 70% of its capacity, best case is fully booked, worse case is only 30%.
· Any costs need to be justified. You may research costs from the Internet, but ensure that you reference where you got them from in your report.
· You may determine the venue where the Gala Dinner will be held. If you cannot find a cost for hiring a venue, assume that it will cost £3,500. This only includes the hiring of the building and does not include, for example, the beverages, food and music costs.
· You can assume that the venue is available for you on Friday 24th September 2021. Do not need to contact the venue directly.
· You may have access to the venue from 5:00am on Friday 24th September 2021 to 12pm on Saturday 25th September 2021 to set up and take down the event (these activities have to be considered in your project plan).
· Make sure the things you offer (promotion channels, entertainment during the event (e.g. live music), quality of food and beverage, reflects the standards of a Gala Dinner.
· You must break even and make profit.
· You do not have an initial budget. This is a bottom up approach to budgeting and you have to identify and decompose each activity into a Work Breakdown Structure, in order to identify the resources needed, activities duration and their cost.
· This is a time sensitive project rather than resource sensitive. Allocate more resources is needed to hit the deadline! However, you will still to make money at the end.
BUSINESS CASE GUIDELINE:
· Clearly define the reasons for undertaking the project and SMART objectives to be achieved
· Consider Business options of do nothing (do not do the project), do the minimum (the minimum products/activities required to break even), do something (following your planned solution).
· Expected benefits and dis-benefits
· Timescale and Costs (from project plan)
· Investment Appraisal based on base case (70%), best case (100%), and worse case (30%) scenario
· Consider Major Risks and Risk management strategy: identify, assess, plan, implement and communicate risks (use the Risk Register provided).
PROJECT PLAN GUIDELINE:
· Complete ALL parts of the planning document and conclude it by producing the following:
· Produce a Product Breakdown Structure (PBS), which is the ‘what’ of the project
· Produce a Work Breakdown Structure (WBS), which is the ‘how’ of the project
· Input all the WBS activities into a Gantt Chart in Microsoft Project
· Produce a table of resources by allocating resources (e.g. material or man hours) to each activity in the Gantt Chart
· Produce an Activity Network by allocating predecessors into the Gantt Chart
· Identify the Critical Path for the project
· For WBS aim at listing a minimum of 30 tasks. Remember that tasks and category headings are different. A category heading, for example, is ‘Marketing’, whereas a task underneath this category heading may be to ‘Print the invitations’. There is no maximum number of tasks and you must illustrate the breakdown with a tree diagram. The breakdown should have a clear logical basis, although technical details may vary. Create your own category heading names as required and remember that there can never be only one right way for a project of this nature, as long as you justify your choice. Explain what basis you use to create the categories and tasks. You must make sure that the tasks are broken down in detail. For example, you would NOT have a task called ‘Invitations’, this should be broken down into the tasks to make sure the invitations have been sent out, for example, ‘Design Invitations’, ‘Create Invitations’, ‘Print Invitations’ and ‘Distribute Invitations’. The work breakdown structure diagram does not count towards the word count, but any assumptions you state will count towards the word count. For example, you may have a category heading called ‘Marketing’ and your assumption will detail how you have approached the students union to help you market the event and recruit student volunteers.
· Category Headings might be but not restricted to: Market Research (venue, suppliers, equipment, menu, etc) – Marketing (advertising and ticketing) – Human Resources (staff) – Operation (during and after event) – Closing (sign off and payments).
· The breakdown structure will not be included into the world count and has to be placed in the appendix.
Checklist – things you may forget about:
• Who are the key resources involved and how much they will cost?
• Where is the venue going to be? If outside have you thought about bad weather and mitigation of this risk (e.g. insurance)?
• What transport and accommodation arrangements do you need to make?
• How much food/drinks to order? (e.g. 1 bottle of wine gives you 6 glasses). Think about this as it will make an impact on budget.
• What are the event details?
• What are the risks for the project?
• Have you created a schedule for the day as well as before the event runs?
• Have you cleaned up after the event and returned any hired items?
This should be delivered in an essay style and should be no more than 3,000 words (+/-10%). The Risk Register, PBD, WBS, Gantt Chart, Table of Resources, Activity Network and Critical Path do not count towards the word count.
RECOMMENDED READING:
[1] Biggs, D. 2010. Management Consulting – A guide for students. Cengage Learning EMEA, Hampshire, United Kingdom.
[2] Davis, K. [Compiler]. 2014. Project Management (2nd edition). Pearson Education Limited, Harlow, United Kingdom.
[3] Johnson, G., Scholes, K., Whittington, R. 2006. Exploring Corporate Strategy (7th edition). Prentice Hall. Pearson Education Limited, Harlow, United Kingdom
[4] Johnson, G., Scholes, K., Whittington, R., Angwin, D., Regner, P. 2017. Fundamentals of Strategy (3rd edition). Prentice Hall. Pearson Education Limited, Harlow, United Kingdom
[5] Koster, K. 2010. International Project Management. SAGE Publications Ltd.
[6] Kotler, P., Armstrong, G., Harris, L.C., Piercy, N. 2017. Principles of Marketing (7th edition). Pearson Education Limited, Harlow, United Kingdom.
[7] Managing Successful Project with PRINCE2. 2017. AXELOS Limited, TSO.

Get help from top-rated tutors in any subject.
Efficiently complete your homework and academic assignments by getting help from the experts at homeworkarchive.com