DOCSLIB.ORG

An Application to PRINCE2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Application to PRINCE2 Bringing Model-based Systems Engineering Capabilities to Project Management: an Application to PRINCE2 Diana Coppola1, Andrea D’Ambrogio2, and Daniele Gianni1 1 Dept. of Applied Sciences and Technologies 2 Dept. of Enterprise Engineering Guglielmo Marconi University University of Rome Tor Vergata Rome, Italy Rome, Italy [email protected], [email protected] [email protected] Copyright © held by the author. Abstract—PRINCE2 is arguably one of the most adopted performance indicators and the maturity level of the process-based methods for project management. adopted project management methodology [2]. Currently, PRINCE2 is defined in a textual specification, PRINCE2 is arguably one of the most adopted which describes the principles, the themes, and the standard project management methodologies in various processes that project managers should apply in their systems engineering domains. PRINCE2 has been more management activities. Although the specification is well structured and mature, the specification does not provide and more adopted since 2009, for three reasons: a browsable digital representation that can be interactively used for learning and/or for the specification application 1. the overall trend of business to use a project- during project management activities. This paper aims to based approach to develop products or overcome these limitations with the application of a model- transformations within increasingly collaborative based systems engineering approach to represent the contexts with multiple partners; PRINCE2 specification in a model-based format. This can 2. the overall trend of capitalizing on knowledge of bring several benefits to the specification, including the best practices in project management; availability of a graphical, comprehensive and digitally 3. the inherent PRINCE2 characteristics, such as the browsable visualization of the PRINCE2 processes, their inputs/outputs, and the constituting tasks. The model- general approach (i.e. application/domain based format has been obtained by a top-down mapping of independent), the product-based planning or the the PRINCE2 specifications, beginning with the process product breakdown structuring. architecture in IDEF0 down to the individual tasks, roles, and tools in BPMN 2.0. Besides supporting PRINCE2 However, PRINCE2 is still relatively complex to learn understanding and application, the model-based format and to apply as the specification sequentially presents all can also serve as a baseline for further exploitations, such the PRINCE2 elements (particularly the processes), as consistency verification of the PRINCE2 specification which are highly interleaved during a PRINCE2 project and model-based process simulation for the governance of execution. As a consequence, the project manager is the PRINCE2 processes and of the project management activities. required to build a detailed mental map of the interconnections to directly access the relevant parts of Keywords—project management; business process; the specifications. Expert project managers, who have model-based; systems engineering. been using PRINCE2 for ten or more years, have likely mastered all these interconnections. However, younger and aspiring project managers may require more I. INTRODUCTION assistance and time to become fully familiar with these Project management methodologies have been interconnections. In the wider systems engineering increasingly adopted to structure, monitor, control, and community, model-based approaches have often been execute temporary and cross-functional organizational introduced to represent document-based specifications activities in order to support managers with the with the implicit objectives of providing an automated information, tools, and processes to increase processing, a direct (i.e. non linear access to the predictability in the delivery of the expected output. individual parts), and an integration with other These methodologies have also been shown to increase supporting tools for decision making [1]. the overall efficiency in terms of resource optimization, In this paper, we apply a model-based systems risk management, and cost management [1]. More engineering approach to the representation of PRINCE2 tangibly, in the last decades, several studies have in order to facilitate the communication, the provided evidence about the link between the enterprise understanding, and the application of the PRINCE2 method. Our model-based approach consists of: IDEF0 diagrams for the representation of the PRINCE2 process project documents, such as detailed business cases (from architecture; BPMN diagrams for the detailed the initial project brief) and guidelines to assess the description of the PRINCE2 processes; a set of achievement of the expected benefits. Differently, the supporting tables to further assist the project manager in process SB produces a detailed planning for the reading the model and in following the development of execution of the following stage. the project in PRINCE2. The paper is structured as follows. The background section provides the fundamental terminology used in PRINCE2 and in business process modeling. The related work section positions this paper’s contribution with respect to the state-of-art. The method section illustrates and motivates the model organization, from the architecture to the details of PRINCE2. Finally, the conclusion section provides closing remarks and directions for further developments. II. BACKGROUND This section briefly recalls the main concepts Fig. 1. The PRINCE2 processes—Starting Up a Project (SU), introduced by project management methodologies (i.e., Directing a Project (DP), Initiating a Project (IP), Managing a PRINCE2), modeling methodologies (i.e., IDEF0) and Stage Boundary (SB), Controlling a Stage (CS), Managing modeling languages (i.e., BPMN). Product Delivery (MP), Closing a Project (CP). A. PRINCE2 B. IDEF0 PRINCE2 has been introduced in 2006 by the UK’s IDEF refers to a family of modeling methodologies Department of Commerce, and is now developed by widely adopted in the field of systems and software AXELOS [6]. PRINCE2 is a best practice for the engineering [9]. Specifically, IDEF0 is a function organization, management, and control of projects of modeling methodology for describing manufacturing any size within any organizational context. Although functions. IDEF0 provides a functional modeling PRINCE2 is of general purpose application, it is based language consisting of three elements: on a structured method which guides the project 1. Diagrams, which represent the structure of the manager in the application of the best practices for the process architecture in terms of activities (boxes) project definition and execution. As further advantages, and their dependencies (arrows). PRINCE2 offers means to standardize the 2. Text, which are labels that can provide further communication among the actors, to focus on the information on the elements in a diagram (e.g. product to be delivered, and to ensure responsibilities name of the activity, etc.). assignment to the actors, and also to embed agile 3. Glossary, which define extensively all the labels, approaches within the PRINCE2 specification. names, and acronyms defined in the diagrams. PRINCE2 consists of the following elements: seven principles—which define the fundamental rules satisfied However, IDEF0 also allows the use of by the following elements; seven themes—which define supplementary material, also known as FEO (For the areas of concerns in a project; and seven inter-linked Exposition Only) pages, which can be used to processes—which define the activities to be performed represent flow diagrams or technical design using any during the project life-cycle, seven themes, and seven formalism. processes; nine roles (e.g. project manager, supplier, Graphically, a diagram consists of a frame, and one customer, executive, team, etc.)—which define the or more boxes and arrows. Asides from delimiting the responsibilities in the project; and 26 internal project area for the drawing of boxes and arrows, the frame products (business case, project plan, risk register, provides also a preassigned location for the diagram etc.)—which inherently define the dependencies among name. For the top-level (or context) diagram defining the processes. Fig. 1 shows the seven processes along the overall process, the name must be “A-0”. This the four stages of a PRINCE2 process and the three diagram “declares” the process and also indicates the levels of actions (directing, managing, executing). parameters related to the model purpose and scope, The Pre-project phase regards the preliminary which are needed to check the consistency and evaluation of the validity and the convenience of project. appropriateness of child diagrams. The first child In this phase, the process SU develops two key diagram must be named “A0” and defines the documents: Project Brief and Plan for the Beginning of composition of overall process. This diagram must the Project. These documents are taken as input by the contain between 3 and 6 activities, which boxes are to process DP, in which the project board assesses the plan be located on the upper-left/lower-right diagonal of the to decide whether or not to authorize the project. In the diagram’s frame, following a temporal order in the positive case, the project execution moves to the development of the activities. Further child diagrams Initiation stage phase, in which the processes IP and SB can be introduced by recursively
Load more

Recommended publications
  • The Marriage Proposal of PRINCE2™ and PMBOK®
    The Marriage Proposal of PRINCE2™ and PMBOK® Dr Anthony Yeong DBA MBA MAIPM PMP PRINCE2 Practitioner Nov 2009 Edition PRINCE2™ Age: 34 years old Nick Name: PRINCE2 Practitioner Birth Certificate: Managing Successful Projects with PRINCE2™ Nationality: British Family: Office of Government Commerce (OGC) Father: Portfolio Management Guide (PfM) Mother: Managing Successful Programmes (MSP) PRINCE2™ stands for Project In Controlled Environment Version 2 and it is originated from Simpact Systems dated back to 1975. Simpact Systems has invented the proprietary project process called PROMPT and was partially adopted by the UK government as its preferred project management process. In 1989, UK government bought over PROMPT and have renamed it to PRINCE™ and placed it in the public domain. The UK government’s Central Computer and Telecommunications Agency (CCTA), now the Office of Government Commerce, (OGC) continued to develop PRINCE™ and has been evolved into newer version termed as PRINCE2™ and issued in 1996. OGC decided to keep the PRINCE2 name regardless of the future editions, ie there will not be PRINCE3 or 4 for newer versions. PRINCE2 has been adopted widely in UK and Europe and getting more recognition in Australia and other parts of the world. In 2005 an updated manual entitled, “Managing Successful Projects with PRINCE2” is released. It is the fourth edition of the manual. The history of the manual is as followed: First Edition 1996 Second Edition 1998 Third Edition 2002 Fourth Edition 2005 Fifth Edition 2009 PRINCE2™ is made of seven principles themes, seven themes and seven processes. The Seven PRINCE2 Principles are: 1. Continued business justification: A PRINCE2 project has continued business justification.
    [Show full text]
  • Application of PRINCE2 Project Management Methodology1
    Studia commercialia Bratislavensia Volume 10; Number 38 (2/2017); pp. 227-238 DOI: 10.1515/stcb-2017-0021 ISSN 1339-3081 Application of PRINCE2 Project Management Methodology1 Radka Vaníčková2 Abstract The methodology describes the principle of setting a project in PRINCE2 project man- agement. The main aim of the paper is to implement PRINCE2 methodology to be used in an enterprise in the service industry. A partial aim is to choose a supplier of the project among new travel guides. The result of the project activity is a sight-seeing tour/service more attractive for customers in the tourism industry and a possible choice of new job opportunities. The added value of the article is the description of applying the principles, processes and topics of PRINCE2 project management so that they might be used in the field. Key words Small and medium-sized enterprises, services, tourism sector, life cycle of the project, project management, PRINCE2 methodology. JEL Classification: L 83, L 84, O 22. Introduction After joining the European Union, the business environment is characterized by a relatively high degree of openness of the economy, harmonization of national regulations with EU legislation, decreased income tax rates, a high level of employee protection (termination of employment), a limited capital market, a consolidated banking sector, rights, inflows of foreign investment, and improving choice of industrial green-field projects (Vochozka, Mulač a kol., 2012). As reported by Kovář, Hrazdilová and Bočková (2016), small and medium-sized enterprises account for almost 90 % of the total number of enterprises with a share of 50-70 % of total employment and a share of 30-70 % of GDP.
    [Show full text]
  • The Timeboxing Process Model for Iterative Software Development
    The Timeboxing Process Model for Iterative Software Development Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur – 208016; India Aveejeet Palit, Priya Kurien Infosys Technologies Limited Electronics City Bangalore – 561 229; India Contact: [email protected] ABSTRACT In today’s business where speed is of essence, an iterative development approach that allows the functionality to be delivered in parts has become a necessity and an effective way to manage risks. In an iterative process, the development of a software system is done in increments, each increment forming of an iteration and resulting in a working system. A common iterative approach is to decide what should be developed in an iteration and then plan the iteration accordingly. A somewhat different iterative is approach is to time box different iterations. In this approach, the length of an iteration is fixed and what should be developed in an iteration is adjusted to fit the time box. Generally, the time boxed iterations are executed in sequence, with some overlap where feasible. In this paper we propose the timeboxing process model that takes the concept of time boxed iterations further by adding pipelining concepts to it for permitting overlapped execution of different iterations. In the timeboxing process model, each time boxed iteration is divided into equal length stages, each stage having a defined function and resulting in a clear work product that is handed over to the next stage. With this division into stages, pipelining concepts are employed to have multiple time boxes executing concurrently, leading to a reduction in the delivery time for product releases.
    [Show full text]
  • PRINCE2® Vs Agile: a Comparison
    PRINCE2® vs Agile: A comparison Author: Simon Buehring ® Copyright © 2015-2018 Knowledge Train. All rights reserved. | PRINCE2® is a registered trade mark of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. There's no doubt that PRINCE2 [1] is the most widely-recognized project management methodology in the world. PRINCE2 qualifications are a standard feature of project management job specifications and have been growing in popularity since PRINCE2’s launch in 1996. Currently, over 150,000 PRINCE2 exams are sat somewhere in the world every year. There remains a lot of confusion between PRINCE2 and agile [2], and indeed debate about whether PRINCE2 or agile methods should be used on projects. In fact, both can and are being used increasingly on projects – often together. This article will explore some of the key features of both PRINCE2 and agile and will dispel some of the myths as well. Differences between PRINCE2 and agile The most fundamental difference between PRINCE2 and agile is that the former is a project management methodology whereas agile refers to numerous software development approaches used by teams which subscribe to the 12 Agile principles. There are many different agile approaches, the most famous being Scrum, Kanban, Extreme Programming, and Lean. 1 Who is PRINCE2 aimed at? PRINCE2 is a customer-focused project management methodology. It offers a set of principles, themes and processes to enable an organization’s key managers to justify a project. It helps them understand “why should we do it (the project)?” and “are the benefits worth the costs and risks of doing the project?”.
    [Show full text]
  • Basics of Project Planning
    BASICS OF PROJECT PLANNING © Zilicus Solutions 2012 Contents The Basics of Project Planning ............................................................................................................. 3 Introduction ..................................................................................................................................... 3 What is Project Planning? ................................................................................................................ 3 Why do we need project planning? ................................................................................................. 3 Elements of project plan .................................................................................................................. 4 1. Project Scope Planning ...................................................................................................... 4 Triangular Constraints (TQR) ............................................................................................................ 5 2. Delivery Schedule Planning ............................................................................................... 5 3. Project Resources Planning ................................................................................................ 6 4. Project Cost Planning ......................................................................................................... 8 5. Project Quality Planning .................................................................................................... 9
    [Show full text]
  • Earned Value Management Earned Value Management
    Earned Value Management Earned Value Management Earned value management is a project management technique for measuring project performance and progress. It has the ability to combine measurements of the project management triangle: • Scope • Schedule, and • Costs In a single integrated system, Earned Value Management is able to provide accurate forecasts of project performance problems, which is an important contribution for project management. Essential features of any EVM implementation include: • a project plan that identifies work to be accomplished, • a valuation of planned work, called Planned Value (PV) and, • pre-defined “earning rules” (also called metrics) to quantify the accomplishment of work, called Earned Value (EV) • Current expenditure on project, called Actual Cost (AC). Demystifying EVM | 2 EVM and ITM Platform • You hire a bricklayer to build a 4 side fence in your backyard. Each side is built in sequence, one after the other. He charges S2 by the hour, 200€ a day. Each side takes him one day of work. He starts working on 12/09/2011. You budgeted 800€. • At the end of the 3rd day (14/09/2011): S1 S3 o He has completed side 1 (cost 200€) o and side 2 (cost 275€) S4 o Side 3 is 50% complete (cost 200€) • How much are you going to pay in the end? Demystifying EVM | 3 EVM and ITM Platform • You can see EVM data in view Follow-up Tab, table Earned Value • Before that, you need to: o Assign resources to tasks o Enter standard rates for each resource o Register Actual Work + update pending Work for each task Demystifying EVM
    [Show full text]
  • Project Initiation Documents, the Information Contained in Those Documents Is Often Quite Similar, Despite Variations in the Terms Used
    et the Free Newsletter By the Project Initiation Mind Tools Editorial Team Documents Getting Your Project off to a Great Start 17 ratings Make sure that you're clear where you're heading from the outset. © iStockphoto FrancescoCorticchia Have you ever been part of a project where not everyone has the same view of where the project is heading? This lack of clarity can breed confusion: People start pulling in different directions, building up unrealistic expectations, and harboring unnecessary worries and fears. While it's normal as part of a project to put the detailed plans, controls and reporting mechanisms into place, how do you get everyone on the same page to start with? This is accomplished by creating a Project Initiation Document (PID) – the top-level project planning document. In it, you bring together all of the information needed to get your project started, and communicate that key information to the project's stakeholders. With a well-put-together Project Initiation Document, you can let everyone understand where the project's heading from the outset. Your Project Initiation Document does the following: • Defines your project and its scope. • Justifies your project. • Secures funding for the project, if necessary. • Defines the roles and responsibilities of project participants. • Gives people the information they need to be productive and effective right from the start. By creating a PID, you'll answer the questions: What? Why? Who? How? When? You can also use a Project Charter instead of a Project Initiation Document for these purposes as they are very similar documents. However, a Project Charter usually has less detail.
    [Show full text]
  • Unit 5 – Project Planning
    Unit 5 – Project Planning UNIT OVERVIEW Description of the Unit In this unit, you will explore the necessity of proper project planning and how ‘front end’ planning can ensure project success. You will look at several scenarios that put a structure around project scope, deliverables, scheduling, staffing, resources, and risks to help anchor the planning process. Unit Objectives At the conclusion of this unit, you will be able to: • Understand the necessity of a project plan • Assess resource and budgeting issues • Analyze project risks • Effectively determine project scope • Identify project deliverables Unit Topics • Project schedules based on work breakdown structures • Project resources and schedules based on staff availability • Project budgets • Managing project risks • Triple constraint to achieve project goals Activities and Exercises • Group Exercise 5A: Project Management Scenarios • Group Exercise 5B: Review Project Plans for Unit 3 Scenarios Approximate Time for Unit 1 hour 45 minutes Managing Technology Projects and Technology Resources Participant Guide 5 - 1 Institute for Court Management Unit 5 – Project Planning Managing Technology Projects and Technology Resources Participant Guide 5 - 2 Institute for Court Management Unit 5 – Project Planning ___________________________________ ___________________________________ ___________________________________ ___________________________________ UNIT 5 ___________________________________ Project Planning ___________________________________ ___________________________________ ©2010
    [Show full text]
  • PRINCE2 Agile Slides
    How to use PRINCE2® with agile ways of working “© Copyright AXELOS Limited 2015. “PRINCE2 Agile™ is a trade mark of AXELOS Limited. All rights reserved.” Course Objectives 1.Understand the basic concepts of common agile ways of working 2.Understand the purpose and context for combining PRINCE2 and the agile way of working 3.Be able to apply and evaluate the focus areas to a project in an agile context 4.Be able to fix and flex the six aspects of a project in an agile context 5.Be able to apply or tailor the PRINCE2 principles, themes, processes and management products to a project in an agile context 6.To learn through the use of theory and practical exercises 7.To prepare delegates for the PRINCE2 Agile Practitioner exam About yourself 1. Name (and company) 2. Role 3. Experience of PRINCE2 4. Experience of agile 5. Your objective for this course About the manual • Aligned to the PRINCE2 manual • Early chapters – Basic understandings and drivers for PRINCE2 Agile. • Middle chapters – Discussion and description of the Principles, Themes, Processes and Products – What you may find – What to do. • Final chapters – Focus areas – where PRINCE2 needs more detailed guidance when in an agile context – The appendices. Exam structure • 2.5 hour exam • Open book • Objective Testing Exam • Taken on the afternoon of the third day • 5 questions totalling 50 marks • Pass mark is TBC. Agenda for Day 1 • Projects and BAU • An overview of agile • Blending PRINCE2 and agile together • Assumptions • The Hexagon (incl. MoSCoW prioritisation) • Starting Up a Project, Initiating a Project (including the Business Case, value assessment and Cynefin approach) • Requirements and User Stories • Organization.
    [Show full text]
  • The Use of Project Management Methodologies in Reducing Project Delays: Evidence from the Adentan Municipal Assembly in Ghana
    “Navigating Cyberspace for Socio-economic Transformation and Redefining Management in Light of Digital Economy.” Proceedings of the 8th International Conference on Management and Economics – 2019 The Use of Project Management Methodologies in Reducing Project Delays: Evidence from the Adentan Municipal Assembly in Ghana Nubuor S.A. a, Dartey-Baah K. b, and Kasanga N.A.B. c a,b,cDepartment of Organization and Human Resource Management, University of Ghana Business School, Legon, University of Ghana, Ghana. [email protected] Abstract The purpose of this study is to investigate the use of project management methodologies in the Metropolitan, Municipal and District Assemblies in Ghana to reduce project delays. To achieve this objective, a case study was conducted in the Adentan Municipal Assembly to determine whether the Assembly is applying the best practices of project management in its projects, to identify the factors causing delay in projects and recommend possible project management solutions to these issues. Projects in Controlled Environment 2 (PRINCE2) and Critical Path Methodologies were employed as the conceptual frameworks for the study. Adopting an exploratory approach, interviews were used to sample the experiences of staff in managing their projects. The results of the investigation provided evidence of the use of project management practices by the Adentan Municipal Assembly in managing projects within their jurisdiction; however, the identified practices did not fall within the context of best practice as described in PRINCE2, and the Critical Path Methodologies. Furthermore, cost, time and scope management were identified as the main project management knowledge areas that were used by the Assembly to ensure the completion of projects as scheduled.
    [Show full text]
  • Reflections on PRINCE2 from an Agile Perspective 4-May-08
    Reflections on PRINCE2 from an Agile perspective 4-May-08 Reflections on PRINCE2 from an Agile perspective (c) Allan Kelly – www.allankelly.net Reflections on PRINCE2 from an Agile perspective...................................................1 Prologue.................................................................................................................2 Introduction............................................................................................................2 History and usage...................................................................................................2 Overview of PRINCE2...........................................................................................4 Eight components...............................................................................................4 Three Techniques ...............................................................................................8 Eight Processes...................................................................................................9 Other elements..................................................................................................12 Critique ................................................................................................................14 Projects – or Products and Programmes? ..........................................................14 Controlled Environments? ................................................................................15 More is less ......................................................................................................16
    [Show full text]
  • Planning in Software Project Management
    PLANNING IN SOFTWARE PROJECT MANAGEMENT AN EMPIRICAL RESEARCH OF SOFTWARE COMPANIES IN VIETNAM Thesis presented to the Faculty of Economics and Social Sciences at the University of Fribourg (Switzerland) in fulfillment of the requirements for the degree of Doctor of Economics and Social Sciences by Quynh Mai NGUYEN from Vietnam Accepted by the Faculty of Economics and Social Sciences on May 30th, 2006 at the proposal of Professor Dr. Andreas Meier (first advisor) Professor Dr. Jacques Pasquier (second advisor) Professor Dr. Laurent Donzé (third advisor) Fribourg, Switzerland 2006 The Faculty of Economics and Soci al Sciences at the University of Fribourg neither approves nor disapproves the opinions expressed in a doctoral dissertati on. They are to be considered those of the author (decision of the Faculty Council of January 23rd, 1990). To my parents, and To Phuong and Trung, my children ACKNOWLEDGEMENT I would like to express my extreme gratitude to Prof. Dr. Andreas Meier for his guidance, encouragement and helpful supervision during the process of this thesis. I would like to thank Prof. Jacques Pasquier and Prof. Laurent Donzé for their review and comments. My special thanks also go to Dr. Fredric William Swierczek for his invaluable help, advices and suggestions for improvement. Without their help and advice this dissertation could not be completed. I would like to thank my friends, Dr. Bui Nguyen Hung, and Dr. Nguyen Dac Hoa, Mrs. Nguyen Thuy Quynh Loan for their assistance and helpful suggestions and contributions. I would like to thank the government of Switzerland and the Swiss – AIT – Vietnam Management Development Program (SAV) for giving me the scholarship for this PhD program.
    [Show full text]