Fiction Managing Successful Projects With Prince2 2009 Pdf


Thursday, August 29, 2019

Projects With Prince2 Edition [PDF] [EPUB] PRINCE2 is firmly uk Managing Successful Projects with PRINCE2 Edition. Managing Successful Projects with PRINCE2® Edition (Polish This publication is also available as a PDF from the TSO Shop. Managing Successful Projects with PRINCE2® Edition - PDF · Managing Successful Projects with PRINCE2® Edition - Online.

Language:English, Spanish, Portuguese
Genre:Fiction & Literature
Published (Last):10.09.2016
ePub File Size:21.53 MB
PDF File Size:16.52 MB
Distribution:Free* [*Regsitration Required]
Uploaded by: ADELE

Managing Successful Projects with PRINCE2TM This is where the PRINCE2 . Projects with PRINCE2 to effectively deliver what is required by (TSO, ). You should be studying the official Prince2 book Managing successful projects with PRINCE2 Download free PDF of this book on this page, using the link below. [PDF] Managing Successful Projects with PRINCE2 Edition Manual EBOOK FOR DOWNLOAD PDF FREE.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy. See our Privacy Policy and User Agreement for details. Published on Aug 20, SlideShare Explore Search You.

Metropolitan Police. David Lillicrap. Wietse Heidema. Jorn Wigh. Highways Agency. Mark Sutton. Remarc Group. United Nations Development Programme. Quorum ICT. Steve Livingstone. Helen Nicoll. Noel Scott.

Martin Lewis. Gerald Williams. Stephen Wierzbicki. Tim Sneller. Xwave solutions inc. Charnwood Borough Council. Eileen Roden. Home Office. Hans Kemper. Ian Santry. Ministry of Economic Development New Zealand. Department of Labour New Zealand. APMG Denmark. Adrian Newton. Land Registry. Lucid IT. Capital Coast District Health Board.

Tim Lulham. Tony Levene. Graham Robertson. Geoff Ward. Quality Projects. Terry Hewins. APMG Netherlands. Joy Shewring. Tanner James Management Consultants Australia. Oger Systems Ltd. Geoff Rankins. Bruce Nicholls. Andrew Schuster. Department of Health. ILX Group plc. Maria Maltby. Nigel Jones. Jay M. David Whelbourn. Southend-on-Sea Borough Council.

Rod Sowden. Sheryl Ward. PM Professional Learning. Luis Herrera. Trevor Mirams. Phil Stephensen-Payne. Staffordshire Metropolitan Borough Council. Aspire Europe Ltd. Ravi Joshi. Bram de Vuyst. Lizz Robb. Liberty Network Consultancy. Satyam Computer Services Ltd. Suffolk County Council. Network Rail. Action For Children.

Raed M. Bristol Management Centre. Peter Weaver. Chris Price. Goal Professional Services Pty Ltd. Philip Wilson. Ministry of Education New Zealand. Ian Thomas. For example. Key points are illustrated like this: Example techniques are illustrated like this: Should have. Conventions used in this manual Throughout this manual. Projects often cross the normal functional divisions within an organization and sometimes span entirely different organizations. Project Managers. Projects are the means by which we introduce change — and.

As the pace of change technology. The manual covers the questions frequently asked by people involved in project management and support roles. There are a number of characteristics of project work that distinguish it from business as usual: This frequently causes stresses and strains both within organizations and between. This manual is designed: A project is a temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case.

Once the desired change has been implemented.

Managing Successful Projects with PRINCE2 2009.pdf - It is...

Each has a different perspective and motivation for getting involved in the change. These questions include: For 1. The ability to delegate is important in any form of management but particularly so because of the crossfunctionality and risks in project management.

There are six variables involved in any project. None of this is project management — so why do we need project management at all? PRINCE2 achieves this by isolating the management aspects of project work from the specialist contributions. It is the Project Manager who plans the sequence of activities to build the house.

Of course. A new house is completed by creating drawings. Projects are more risky.

An organization may undertake many similar projects. Even if the work is going well. In order to achieve control over anything. With the delegated work under way. It may be possible to build the house yourself — but being a manager implies that you will delegate some or all of the work to others.

Whether it is by taking corrective action or implementing measures to improve performance. Project management is the planning. Should we build the house near the site of a disused mine. The seven themes explain the specific treatment required by PRINCE2 for various project management disciplines and why they are necessary. The Project Manager should take care not to deliver beyond the scope as this is a common source of delays.

The customer may assume that. If we decide to go ahead. The Project Manager has to have a clear understanding of the purpose of the project as an investment and make sure that what the project delivers is consistent with achieving the desired return. There are seven principles and unless all of them are applied. Each process provides checklists of recommended activities. Maybe insure against it or have thorough surveys carried out?

Benefits Perhaps most often overlooked is the question. Without knowing it. Introduction or live in it happily.

There is a companion guide. On large-scale projects. Where appropriate. Details of these best-practice guides and other relevant guides can be found in Further Information. Figure 1. OGC methods and guidance are augmented by qualification schemes. Engineering models. There are many leadership models and interpersonalskills training programmes that fulfil this requirement. For this reason. Such techniques are well documented elsewhere. Examples are critical path analysis in planning and earned value analysis in progress control.

Project Board or project management levels PRINCE2 ensures that participants focus on the viability of the project in relation to its Business Case objectives — rather than simply seeing the completion of the project as an end in itself It defines a thorough but economical structure of reports It ensures that stakeholders including sponsors and resource providers are properly represented in planning and decision making Adopting PRINCE2 promotes learning and continual improvement in organizations PRINCE2 promotes consistency of project work and the ability to reuse project assets.

The fact that it is easy to think of successful leaders who have adopted very different styles — from autocratic to consensus-based — bears this out. There is a defined structure for accountability. Leadership styles vary considerably and a style that works in one situation may be entirely inappropriate in another. If a project does not adhere to these principles. It is therefore important that the project and evolving justification remain consistent.

Although the justification should remain valid. Stopping a project in these circumstances is a positive contribution to an organization as its funds and resources can be reinvested in other more worthwhile projects. Even projects that are compulsory for example.

They provide a framework of good practice for those people involved in a project. Poor alignment with corporate strategies can also result in organizations having a portfolio of projects that have mutually inconsistent or duplicated objectives.

Organizations that lack rigour in developing Business Cases may find that some projects proceed even where there are few real benefits or where a project has only tentative associations with corporate strategy. The principles facilitate good use of PRINCE2 by ensuring that the method is not applied in an overly prescriptive way or in name only. Principles are characterized as: As a project is inextricably linked to its business justification.

To be successful. It is this element of uniqueness that makes projects challenging as the temporary team may not have experience of a project like the one being undertaken. The management structures of the parties involved in the project are likely to be different — with different priorities.

The day-to-day line management structures may not be designed for. Lessons should be included in all reports and reviews. Projects involve a temporary organization for a finite timescale for a specific business purpose. For all those people involved. Unless lessons provoke change. The defined project management team structure unites the various parties in the common aims of the project.

If the project costs outweigh the benefits. All projects have the following primary stakeholders: A project is typically cross-functional. It is the responsibility of everyone involved with the project to seek lessons learned rather than waiting for someone else to provide them. A common characteristic is that the project includes an element of uniqueness such that it cannot be managed by existing line management or functional units.

No amount of good planning or control will help if the wrong people are involved. Principles 13 2. Accountability is established by: Shorter stages offer more control. At the end of each stage. A great deal of effort can be wasted on attempts to plan beyond a sensible planning horizon. A detailed Team Plan for the short term and an outline plan for the long term is a more effective approach. Management stages provide senior management with control points at major intervals throughout the project.

Breaking the project into a number of stages enables the extent of senior management control over projects to be varied according to the business priority. Planning can only be done to a level of detail that is manageable and foreseeable.

It can be used by any project because the method is designed to be tailored to its specific needs. A successful project is output-oriented not activityoriented.

The purpose of a project can be interpreted in many different ways unless there is an explicit understanding of the products to be produced and the criteria against which they will be individually approved. They provide the means to determine effort estimates. Without a product focus. The set of agreed products defines the scope of a project and provides the basis for planning and control. Tailoring requires the Project Manager and the Project Board to make an active decision on how the method will be applied.

The value of PRINCE2 is that it is a universal project management method that can be applied regardless of project type. The purpose of a project is to fulfil stakeholder expectations in accordance with the business justification.

The purpose of tailoring is to: Where are we now? Where are we going? Should we carry on? Organization The organization sponsoring the project needs to allocate the work to Who? Table 3. Chapter 4 The project starts with an idea which is considered to have potential value for the organization concerned.

This theme describes the roles and responsibilities in the temporary PRINCE2 project management team required to manage the project effectively. Any Project Manager who gives thorough attention to these themes will fulfil the role in a professional manner. Projects are cross-functional so the normal line function structures are not suitable. The theme explains the decision-making process for approving plans.

This theme addresses the ongoing viability of the plans. This theme complements the Quality theme by describing the steps required to develop plans and the PRINCE2 techniques that should be applied.

The PRINCE2 processes address the chronological flow of the project — with actions relating to different themes mixed together.

This theme What if? They are the focus for communication and control throughout the project. Issues may be unanticipated general problems. This theme explains What? How much? The reasons for undertaking the project must drive decision making. The Project Board and stakeholders must have confidence at all times that the project remains viable.

When projects face changes or risks. The business justification is the reason for the project. The ongoing and ever-present decision regarding the Business Case is whether the project can still be justified. Such analysis enables one project to be compared with another so that the organization can choose to invest in the best set of projects.

The purpose of the Business Case theme is to establish mechanisms to judge whether the project is and remains desirable. In some cases the project may be initiated with 4.

It should not be used only to gain initial funding for a project. The Business Case presents the optimum mix of information used to judge whether the project is and remains desirable.

The Senior User s is responsible for specifying the benefits and subsequently realizing the benefits through the use of the products provided by the project. When making investment decisions. The Executive is responsible for ensuring that those benefits specified by the Senior User s represent value for money. If business justification is valid at the start of a project.

It provides the answer to the question: Since this viability question is ongoing. Without it no project should start. Projects should be evaluated on how well they will contribute to corporate objectives. New sales system Outcome: Sales orders are processed more quickly and accurately Benefits: In this context: Desired outcomes measured in Business changes also cause The Business Case is at the centre of any impact assessment of risks.

Confirming benefits will mostly take place postproject. Side-e ects and consequences result in realize further Benefits helps achieve one or more 4. For more details on how the project environment affects the Business Case. Regardless of the type of measure being used. Development of the Business Case may be delegated.

It does not necessarily mean that the Executive writes the Business Case. Such objectives will be measured differently depending on the type of project.

The outline Business Case is derived from the project mandate and developed pre-project in the Starting up a Project process in order to gain approval by the Project Board in the Directing a Project process to initiate the project.

To drive the decision making. There needs to be an initial justification to proceed with the project. Once the costs and timescales are better understood. The detailed Business Case is derived from the outline Business Case.

The Executive should not rely on end stage assessments alone to make this judgement and should use Project Assurance to assist. Whoever is given the task of developing the Business Case. In some cases. If not. Due to the inputs required to develop a Business Case. By default. If corporate or programme management are to manage or participate in the benefits reviews. The projected 12 million visitors was an untested assumption and significantly higher than the actual 4.

As the Benefits Review Plan may be managed by the project. The Senior User s specifies the benefits and is held to account by demonstrating to corporate or programme management that the forecast benefits that formed the basis of project approval are in fact realized. The Benefits Review Plan is first created by the Project Manager in the initiation stage and is submitted to the Project Board for approval when seeking project authorization.

The Benefits Review Plan is updated towards the end of each stage with actual benefits achieved. Example of an unverified Business Case A project to build a tourist attraction in London was justified on the basis of attracting 12 million visitors in its first year.

The benefits that can be measured during the life of a project should be reported by the Project Manager in the End Stage Report. Any residual 4. The projected number of visitors determined the revenue for the exhibition and. In project terms it was a success — the exhibition opened on time. This poses a dilemma because. It was a commercial and public relations disaster.

This may involve a commitment beyond the life of the project as it is likely that many benefits will not be realized until after it has closed. It is important to define the current status of each benefit in quantifiable terms so that measurable improvements can be assessed after the project has been completed. Regardless of whether they are financial or non-financial. The reasons are likely to be defined in the project mandate. It typically contains: The post-project benefits review s will involve corporate or programme management holding the Senior User s to account by asking them to provide evidence of how the individual benefits allocated to them have been gained in comparison to those benefits promised to justify the cost and risk of the project when it was authorized.

Business Case benefits should be re-examined and their forecast updated as part of the Managing a Stage Boundary process. Benefits can be financial and non-financial sometimes referred to as cashable and noncashable. The Business Case should define how and when the measurement of the improvement can be made.

The Business Case for the chosen option should be continually assessed for desirability. The following sections provide further guidance for some of the Business Case content. Once the benefits are defined.

Managing Successful Projects With PRINCE2TM

This analysis usually reveals whether benefit expectations are reasonable or overoptimistic. Identifying the timescale requirement for a project can help identify tolerances and timings for benefits reviews.

The quantification of benefits enables benefits tolerance to be set e. The project should not include any products that do not directly or indirectly enable the soughtafter benefits to be achieved.

Both of these can be converted into a likely monetary saving. If it is. The last might be affected by building into the costs an allowance for estimating inaccuracies.

Such mapping enables decisions to be made based on the impact of the realization of the expected benefits. Wherever possible. These would all need to be considered and valued as part of the investment appraisal. The Senior User s is responsible for the set of benefits within their respective areas. The result of this analysis can lead to revision of the decision to go ahead with the project.

Another example is to define three views of the achievement of the benefits. The list of expected benefits will influence the set of products that the project will provide.

The costs should also include details of the ongoing operations and maintenance costs and their funding arrangements. There are many ways to verify the expected benefits. Dis-benefits are actual consequences of an activity whereas. In this example. If the project includes benefits that cannot be proven. Mapping products to outcomes and subsequently to benefits aids decision making in the planning and control of the project.

It is worth making the effort to think carefully about intangible benefits to see whether they can be expressed in measurable ways. The Senior User or Executive may define many benefits as intangible for example. The investment appraisal period may be a fixed number of years or the useful life of the products. Sensitivity analysis involves tweaking the input factors to model the point at which the output factors no longer justify the investment.

Refer to Appendix C for further details of project management team roles and their associated responsibilities. The Business Case should include a summary of the aggregated risks and it is suggested that this is in the form of a summary risk profile and highlight the major risks that will have an effect on the business objectives and benefits therefore covering both the project delivery and the ongoing operations and maintenance.

In order to identify how robust the Business Case is. Sometimes discounted cash flows include risk adjustments as the business may not be confident that all the benefits will materialize Net present value The total value of discounted future cash inflows less the initial investment.

The commissioning authority may have prescribed accounting rules defining how the investment will be appraised. The investment appraisal should cover both the project costs to produce the required products and the project management costs and the ongoing operations and maintenance costs.

Project Assurance business assurance responsibilities Assist in the development of the Business Case. Ensure the value-for-money solution is constantly reassessed. Executive Senior User s Responsible for specifying the benefits upon which the Business Case is approved. Confirm that the products required can be delivered within the expected costs and are viable. Responsible for the Business Case for the duration of the project. Project Support should advise the Project Manager of any proposed or actual changes to products that affect the Business Case.

Responsible for the Benefits Review Plan post-project. Review the impact assessment of potential changes on the Business Case and Project Plan.

Monitor project finance on behalf of the customer. Verify and monitor the Benefits Review Plan for alignment to corporate or programme management. Monitor changes to the Project Plan to identify any impact on the needs of the business or the Business Case.

Assess and report on project performance at project closure. Verify and monitor the Business Case against external events and project progress. Project Support The Business Case should have a baseline and therefore be under configuration management. Responsible for the Benefits Review Plan for the duration of the project unless being managed by corporate or programme management. Provide actual versus forecast benefits statement at the benefits reviews. Oversee the development of a viable Business Case.

Ensure the project fits with overall programme or corporate strategy. Ensure the desired outcome of the project is specified. Ensure that the project produces products which deliver the desired outcomes. Prepare the Business Case on behalf of the Executive. Assess and update the Business Case at the end of each management stage. It needs to be flexible 5. One of the principles of PRINCE2 is that all projects must have a defined organizational structure to unite the various parties in the common aims of the project and to enable effective project governance and decision making.

When combining roles.. It will. It assumes that there will be a customer who will specify the desired result and probably pay for the project. It is likely to have a longer life than a single project. It defines roles. Establishing an effective project management team structure and strategy for communication at the beginning of a project. A programme is a temporary flexible organizational structure created to coordinate. Every project needs effective direction.

A project which forms part of a programme may be impacted by the programme structure and reporting requirements. A successful project management team should: The supplier viewpoint should represent those who will provide the necessary skills and produce the project product.

The user viewpoint should represent those individuals or groups for whom some or all of the following will apply: Business The project User Supplier Figure 5. As well as the primary categories of business.

The project may need to. The project should also provide value for money. Where the user interest is external to the organization sponsoring the development. The Senior Supplier s will represent this stakeholder interest on the Project Board.

These stakeholders may be internal or external to the corporate organization and may support. In this case. The business viewpoint therefore should be represented to ensure that these two prerequisites exist before a project commences and remain in existence throughout the project.

The project management structure has four levels. The level of overlap between the interests of the business. Figure 5.

But projects need day-to-day management if they are to be successful. This for the day-to-day management of the project within the constraints set out by the Project Board. The Project Board is accountable for the success of the project. The four levels of management are: Organization information should.

As part of directing the project. In such cases. For example: As the Project Board is accountable for the project. A good Project Board should display four key characteristics: Depending on the size and complexity of the project.

The Executive representing the business viewpoint and Senior User representing the user viewpoint roles can often be combined. The managerial level required to fill the roles will depend on factors such as the budget. The Project Board has authority and responsibility for the project within the instructions initially contained in the project mandate set by corporate or programme management. The structure allows for channels of communication to decisionmaking forums and should be backed up by role descriptions that specify the responsibilities.

As one of the key responsibilities of the Project Board is to provide direction to the Project Manager. This role will include providing supplier resources to the project and ensuring that proposals for designing and developing the products are feasible and realistic.

Project Board members are often from senior management positions. The Executive will then be responsible for designing and appointing the rest of the project management team. The frequency and detail of communication required by the Project Board during a project should be documented in the Communication Management Strategy.

If the project is part of a programme. The concept of management by exception allows the Project Manager to keep them regularly informed of project progress but only requires decision making at key points in the project.

The Senior User s specifies the benefits and is held to account by demonstrating to corporate or programme management that the forecasted benefits that were the basis of project approval are in fact realized. This role is accountable for the quality of products delivered by the supplier s and is responsible for the technical integrity of the project. It is important to review the level and frequency of reporting for each stage during the Managing a Stage Boundary process.

The role of the Executive is vested in one individual. Project Board members may require more detailed or frequent information at the start of the project. Project Board members should not be involved in the detail of how the project is managed.

For the sake of effectiveness the role should not be split between too many people. The Executive has to ensure that the project gives value for money. Senior Supplier The Senior Supplier s represents the interests of those designing. As the project progresses. Executive Although the Project Board is responsible for the project. The Executive is appointed by corporate or programme management during the pre-project process of Starting up a Project.

This role may require more than one person to cover all the user interests. The Senior User role commits user resources and monitors products against requirements. The Project Board is not a democracy controlled by votes. Throughout the project. Where Project Assurance tasks are shared between Project Board members and other individuals.

If they have sufficient time available. Project Board members are responsible for the aspects of Project Assurance aligned to their respective areas of concern — business. If necessary. The Project Board may also make use of other members of the corporate organization taking specific Project Assurance roles.

But projects may be in a dynamic environment. In fact. Technical knowledge may also be needed to evaluate potential changes. Anyone appointed to a Project Assurance role reports to the Project Board member overseeing These delegated authorities must be written into the appropriate role descriptions.

In a project where few changes are envisaged. For projects that exist within a programme. Exceptions to this do occur. Depending on the severity. Project Assurance is not just an independent check. The Project Board needs to decide before the project moves out of the initiation stage if it wishes to delegate some authority for approving or rejecting requests for change or off-specifications.

Project Board members are accountable for the Project Assurance actions aligned to their area of interest. To facilitate this. Personnel involved in Project Assurance are also responsible for supporting the Project Manager.

Refer to Chapter 9 for more information on changes. The Project Board needs to represent all of the interested parties in the corporate organization. To avoid enlarging the Project Board. These groups discuss user or supplier issues and risks. Any changes that fall outside of these limits would have to be escalated to the Project Board.

It may also be appropriate to appoint members of these groups to user or supplier Project Assurance. If a user or supplier group is involved. Organization 37 Example of a Change Authority A Project Manager is given authority to approve changes to individual products only if the changes would: User groups User groups User representative area 1 User representative User area 1 representative area 2 User representative area 2 On a large project. There are many reasons why the Project Manager may decide to appoint other people to be Team Managers rather than undertake the role themselves.

The Team Manager reports to. In projects with no separate individual allocated to a Team Manager role. The Project Manager will normally come from the customer corporate organization. In projects with no separate Project Support role. This person has the authority to run the project on behalf of the Project Board within the constraints laid down by the Project Board.

Among these are the size of the project. They can be used formally or informally depending on the needs of the project. In addition to the information included in Appendix A. Defining the deliverables at the appropriate level will also assist new Team Managers in becoming more effective as it is clear what has to be produced.

As the single focus for the day-to-day management of a project. Leaving them out of the Directing a Project process could cause delays due to the lack of supplier resources to deal with change and to address specialist issues.

The Team Manager role may be assigned to the Project Manager or a separate person. The decision on whether to include external suppliers on the Project Board may be a cultural one based on fear of divulging commercial or financial information. Organization If the Team Manager comes from the supplier corporate organization.

Knowledge of different types of personalities and how these work together can help the Project Manager to structure balanced teams that can work together effectively during a project.

In practice. A clearly defined team structure. Although ideally the Project Executive and Project Manager should stay with the project throughout its lifecycle. It is important to stress that the role of Project Support is not optional. Project Support and Project Assurance roles should be kept separate in order to maintain the independence of Project Assurance. Some corporate organizations may have a project office a temporary office set up to support the delivery of a specific project or similar structure.

After the supplier has been selected and the project moves to the development stage. Example of changes to the project management team A project may include a procurement stage. In a given environment. It could also provide specialist functions to a project such as planning or risk management.

If required. Project roles should be reviewed for the next stage during the Managing a Stage Boundary process.

Managing Successful Projects with PRINCE2 | AXELOS Store

Project Support defaults to the Project Manager if it is not otherwise allocated. Unless performed by a corporate or programme management function. Different people have different characteristics. The use of management stages also allows a smooth transition for changes to the project management team. It is not enough to have the required processes and systems in place: The use of End Stage Reports and Stage Plans can help to ensure that any handover procedure is thorough and well documented. A Team Manager.

In the context of the project. Project Support is typically responsible for administering any configuration management procedure and tools as defined in the Configuration Management Strategy. The structure of the project management team does not necessarily reflect line function or seniority but represents roles on the project. Before the supplier has been selected. If individuals are tasked with working on too many projects. During a project. It is important to achieve the correct balance: Solutions include undertaking fewer projects in parallel or.

Parttime team members suffer more absences and diversions. This could include training on any processes and standards to be used on the project such as configuration management procedures. Others are more analytical.

Project Managers can find difficulties when managing cross-functional projects due to the inability to agree overall leadership from within the various groups.

The Project Manager should allow for this when designing a plan — either by negotiating guaranteed availability or greater tolerance. As a result. Project Board members may also need training on their roles. The Project Manager should ensure that training needs are built into the appropriate plans. Whatever the environment. Project Managers who know the natural roles of the team members can use that knowledge to build effective teams during the Starting up a Project process for the management team and the Initiating a Project process when identifying team members.

The manager of a small project is therefore likely to find that team members are. Understanding and working within the wider corporate organization can be challenging for the Project Manager. Setting up clear project controls at the start of the project. Parties external to the project management team can exert a powerful influence on a project. Example of stakeholder analysis Stakeholder analysis identified the following stakeholders for a project to relocate a chemical factory: It is important to analyse who these stakeholders are and to engage with them appropriately.

All projects need to have some level of some stakeholder engagement. A centre of excellence can be useful where: Effective communication with key stakeholders. Such people may: Example of a centre of excellence An organization has established a centre of excellence that provides: Note that some of these were external to the project management team but internal to the corporate or programme management organization.

It is usually carried out at the programme level. Where the project is part of a programme. Their position in the corporate organization and expertise in the subject matter will. If a formal stakeholder engagement procedure has been completed. For each interested party. For instance. Project Assurance could be involved in checking all the key stakeholders. The Project Manager should be responsible for documenting the Communication Management Strategy during the Initiating a Project process.

They have the potential to affect the success of the project. Many projects have a formal commencement meeting to introduce the project and its aims to the corporate organization.

Managing Successful Projects with PRINCE2® 2009 Edition

When planning the final stage of the project it is also important to review the Communication Management Strategy Defining the methods and timings of the communications. These are best planned after defining how the project will engage with the different stakeholders. Perceptions may be mistaken. If this type of meeting is used.

When selecting the senders of information. Defining how the project can effectively engage with the stakeholders. Gaining an understanding of the influences. It is also important to review and possibly update the Communication Management Strategy at each stage boundary in order to ensure that it still includes all the key stakeholders. Refer to Appendix A for more details of the suggested content for the Communication Management Strategy.

It facilitates engagement with stakeholders through the establishment of a controlled and bi-directional flow of information. Identifying the individual stakeholders involved in.

Ensure that the Communication Management Strategy is appropriate and that planned communication activities actually take place. Advise on project team members and stakeholder engagement.

Advise on selection of project team members. Executive Appoint the Project Manager if not done by corporate or programme management. Prepare role descriptions. Refer to Chapter 19 for more detailed information on programme roles and how they may interact with project roles. Approve the Communication Management Strategy.

Confirm the appointments to the project management team and the structure of the project management team. Define and verify user requirements and expectations. Prepare the Communication Management Strategy. It is a structured project management method based on experience drawn from thousands of project practitioners sponsors, trainers, and academics worldwide.

It will be particularly useful for new project managers wishing to learn about project management generally and about PRINCE2 in particular. Experienced project professionals, and anyone considering introducing PRINCE2, will benefit from the detailed best-practice and governance guidance held within this invaluable resource.

Write a Review. Number of pages: Publication Date: In stock - days. Delivery options and charges. You May Also Like The feedback from the clients was always very positive and key project milestones have been achieved , realising projected business benefits.

MARYBELLE from Virginia
Also read my other articles. I have always been a very creative person and find it relaxing to indulge in rugby fives. I love reading comics questionably.