Showing posts with label Project Management. Show all posts
Showing posts with label Project Management. Show all posts

Saturday, 7 February 2015

Business Case

Business case key Philosophies:
The business case represents the optimum mix of information used to judge whether the project is (and remains) desirable,viable and achievable, and therefore worthwhile investing in. A business case must drive the project,it should justify the reason for embarking on the project and why it is worth investing in. If the business case is not satisfactory then you should not embark on the project, and should justification disappear during the project,then stop the project.

The business case is owned by the executive,and it should be developed at he beginning and maintained throughout the project. The focus of the business case should be on totality of business change.

Types of Business cases or projects
  • Compulsory project: A compulsory project is a project that must be done and is essential for the survival of the company.

  • Not for profit project: This might be a project to fulfill a corporate social responsibility or for goodwill whereby the company is not looking to earn profits from it.

  • Customer/Supplier project: This is a project that is initiated by a customer and fashioned to the customer's specifications. The organization seeks to earn profits from such projects.

  • Multi-organization project: As the name implies,it is a project between two or mor organizations for a specific purpose. For example a joint venture.


Business case Contents

1) Expected benefits: This would be a list of each business case benefits the company stands to gain by the project's outcome. Benefits may be measured by financial or non financial metrics. Each benefit should be aligned to strategy and objectives mapped from outputs and outcomes quantified with tolerances measurable assigned.

The PRINCE2 senior user is responsible for identifying the business case benefits in the first place and will be held to account by corporate or programme management that these benefits are eventually realised.

2) Expected dis-benefits: A dis benefit is a negative outcome of carrying out a project. It can be called a side effect or consequence. For example a project that involves the manufacturing a product might come with a dis benefit of air pollution and also noise pollution.


3) Timescale: This is the timeframe on which cost benefit analysis would be based upon.,the time when benefits will be accrued and the earliest time or latest feasible start and completion dates.

4)  Costs: The cost should be linked to the corporate strategies and objectives, it should include details of on-going operational and maintenance costs. This section of the business case should also include the funding arrangements.

5)  Investment Appraisal: A business case should contain a comparison of the development, operations and maintenance costs against the value of the benefits over a period of time. Some of the techniques that can be used for an investment appraisal include:
1) Return on investment
2) Discounted cash flow
3) Payback period
4) Net present value
5) Internal rate of return.



Major risks: in order for the business case to make a balanced business justification,it must consider and include the risks, and these should be balanced against those benefits and costs.




PRINCE 2 principles

PRINCE 2 principles
PRINCE 2 which means projects in controlled environments ii is principles-based. If a project does not adhere to these principles,that means it is not being managed using PRINCE 2.

The seven PRINCE 2 principles can be summarizes as:
  • Continued business justification
  • Learn from experience
  • Defined roles and responsibilities
  • Manage by stages
  • Manage by exception
  • Focus on product
  • Tailor to suit project environment.



1) Continued business justification: A PRINCE 2 project should have continued business justification. A project's justification is documented in a business case. The business case represents the optimum mix of information used to judge whether the project is (and remains) desirable, viable and achievable and therefore worthwhile investing in. Although the justification should remain valid, it may change. If the project can no longer be justified, the project should be stopped.


2) Learn from experience: in PRINCE 2, project teams learn from experience. They reflect back on previous projects or stages carried out, so lessons are sought,recorded and acted upon throughout the life of a project. In PRINCE 2, learning from experience should be used in three stages which are
a) When starting the project
b) As the project progresses
c) As the project closes.



3) Defined Roles and Responsibilities
A PRINCE 2 project has defined roles and responsibilities within an organization structure that engages all stakeholder interests. These stakeholders being the Business, Users and Suppliers.


4) Manage by Stages
A PRINCE 2 project is planned,monitored and controlled on a stage by stage basis. Management stages provide senior management with control points. It is required that there should be a minimum of two stages which are the initiation stage and one or more further management stages.

5) Manage by exception
A PRINCE 2 project has defined tolerances for each project objective to establish limits of delegated authority. If tolerances are forecast to be exceeded or are exceeded,they are immediately escalated to the next management layer. Tolerances can be set against six objectives for the respective level of plan. These six objectives are time, cost,quality,scope,risk and benefit


6) Focus on products:
A PRINCE2 project focuses on the definition and delivery of products, in particular their quality requirements. A PRINCE2 project uses product descriptions to define each product's purpose,composition,derivation ,format,quality criteria and quality method.


7) Tailored to shit the project environment:
PRINCE 2 is tailored to suit the project's environment size,complexity,importance,capability and risk.

PRINCE 2 Themes

PRINCE 2 Themes
There are seven PRINCE2 Themes and they are
1) Business case
2) Organization
3) Quality
4) Plans
5) Risk
6) Change
7) Progress

Now let's briefly look at each of the themes.
  • Business case: To begin a project, an idea must be born that would be considered to have potential value for the organization. A business case is therefore a justification for a proposed project or undertaking on the basis of its expected commercial benefits.

  • Organization: Describes the roles and responsibilities in the temporary PRINCE2 project organization required to manage the project effectively.

  • Quality :This explains how to understand and deliver the quality attributes of the products.

  • Plans: Plans are the focus for the communication and control throughout the project, it describes the steps required to develop plans and the PRINCE 2 techniques that should be applied.

  • Risk: In a project, there are uncertainties because it is susceptible to change. So the theme of risk addresses how project management manages the uncertainties in its plans and in the wider project environment.

  • Change: This describes how project management assesses and acts upon issues. Issues may be unanticipated general problems, requests for change or instancee of quality failure.

  • Progress: Addresses the ongoing viability of the plans and it explains the decision manking process for approving plans, the monitoring of actual performance and the escalation process if events do not go according to plan.

Project Organization

Project Organization
The organization theme serves a main purpose of defining and establishing the project's structure of accountability and responsibility. PRINCE 2 is based on a customer/supplier environment. A successful project organization should have three characteristics which are:

a) Have business,user and supplier stakeholder representation

b) Ensure appropriate governance by defining responsibilities for directing,managing and delivering the project and clearly defining accountability at each level.

c) Have an effective strategy to manage communication flows to and from key external stakeholders.


The three Project interests:
There are three project interests in organization,and they are:

  • Business: The products of the project should meet a business need which will justify the investment in the project. The project should satisfy the value for money criteria to make it worthwhile.The executive role is defined to look after the business interests.

  • User: The senior user will represent this stakeholder interest on the project board. The senior user specifies the needs of the project, ensures user liaison with project management team,commits user resources, monitors products against requirements and specifies benefits and are held accountable for forcasted benefits realization. The user view point should represent those individuals or groups who will operate,maintain or support the project's outputs.

  • Supplier: The supplier viewpoint should represent those who will provide the necessary skills and produce project product. The project may require both in-house and external supplier teams to construct the project product. The senior supplier will represent this stakeholder interest on the project board.

Organization Levels.
In the organization theme of project management under PRINCE 2, there is a distinction between the direction and management of the project and the delivery of the project's output.

The project Management structure has four levels, three of these represent the project management team while the fourth sitting outside of the project.

  • Corporate or program management: This is the topmost level of the project management structure,it sits outside the project management team but will be responsible for commissioning the project, including identifying the executive and defining the project-level tolerances within which the Project Board will work.

  • Directing: The responsibility of directing is entrusted with the project board, it is responsible for the overall direction and management of the project within the constraints set out by corporate or program management. The project board escalates problems outside the tolerance level to the corporate or program management and it is accountable for the success of the project.

  • Managing: The project manager is responsible for the day to day management of the project within the constraints set out by the project board. The project manager is expected to ensure that the project is completed and produces the required output in accordance to the time,cost,quality, scope, risk and benefit performance goals.

  • Delivering: This is vested with the team members. They are responsible for the day for delivering the project's products to an appropriate quality, and within a specified timescale and cost.




Project Board
Duties of the project board includes:
  • Being accountable for the success or failure of the project in terms of the business,user and supplier interests.

  • Providing unified direction to the project.

  • Providing the resources and authorizing the funds necessary for the successful completion of the project.

  • Facilitating integration of the project management team with the functional units corporate or external organizations

  • Ensuring effective decision making

  • Providing visible and sustained support for the project manager.

  • Ensuring effective communication to project team and external stakeholders.


Four characteristics of a good project board:
  •  Authority: A project board should be able to make strategic decisions about the project. It should have the power and right to make decisions and to provide resources to the project. The managerial level required to fill the roles will depend on factors such as the budget, scope and importance of the project.

  • Credibility: Within organization will affect the ability to direct the project.
  • Ability to delegate: Project board should not be involved in the detail of how the project is managed, nor in the specialist content of the project, but they should delegate this to the project manager and give enough space to manage the project by keeping the project board activity at the right level.

  • Availability: To make decisions and provide direction to the project manager.


Project board roles:
  • Executive: The executive is tye key decision maker of a project, he is accountable for the project's success. The executive is the owner of the business case and is focused throughout its life on achieving its objectives and delivering a product that will achieve the forecasted benefits. The executive is appointed by the corporate or program management during the pre-project process of starting up a project.

  • Senior user:The responsibilities of the senior user include:a) Specifying the needs of those who will use the project's products. b) User liason with the project management team. c) Monitoring that the solution will meet those needs within the constraints of the Business case in terms of quality, functionality and ease of use. d) Committing user resources.


  • Senior supplier:The senior supplier represents the interests of those designing,facilitating,procuring and implementing the project's products. The role is accountable for quality products and technical integrity. They provide supplier resources,ensure proposals for design are feasible and realistic and also mostly represents the maintenance interest post implementation.


Change authority:
The change authority has the following responsibilities
a) Changes approved by project board unless many changes are envisaged.
b) May include the project manager, project assurance, technical experts and users.
c) Approves request for changes and off specification
d) severity and authority of changes defined in Configuration Management Strategy
e) Appointed during initiating a project.


Project Assurance:
Project assurance is appointed where project board has insufficient time or requires expertise. Some of the responsibilities include:
a) Provide advise to the project manager but independent of the project manager
b) ideally should have 3 different role representing the business, user and supplier
c) Ensures correct people are involved with quality review and approval
d) Assist with the appointment of the quality review chairperson.



Project Manager:
The project manager manages the prpject from a day to day basis, it normally comes from tge customer environment but may also be from supplier.

The project manager is responsible for all PRINCE2 processes except directing a project. The project manager is appointed by the executive at starting up a project . The project manager delegates responsibility to the team managers and project support, and they are responsible for liaison with the project board and project assurance.


Team manager
Tge team manager is responsible for the production of the assigned products and reports to the project manger. The appointment of the team manager is influenced by the project size, specialist skills required and the geographical location.

The team manager agrees with the project manager on work packages delivery, reporting, cost, time.

Project support. The project support is delegated by the project manager unless performed by corporate or programme management. Project support may include specialist functions such as planning or risk management. Project support is responsible for configuration management procedure and tools defined in configuration management strategy. The project support must be kept independent from project assurance.

Thursday, 11 December 2014

What is Project Management?

PROJECT MANAGEMENT
Before delving into project management, lets first take a look at what a project is. Many people and organizations have defined what a project is, or should be, but probably the most authoritative definition is that given in BS 6079-2:2000 Project Management Vocabulary, which states that a project is: ‘A unique process, consisting of a set of co-ordinated and controlled activities with start and finish dates, undertaken to achieve an objectives conforming to specific requirements, including
constraints of time, cost and resources.’. Then you begin to ask yourself what then is project management? and what is the need for this peculiar type of management?, what is the difference between project management and management of any other business or enterprise?. The answer is that since projects are the vehicles by which change is introduced to organizations, then project management is the management of this so called change, while running a functional or ongoing business is managing a continuum or ‘business-as-usual’.Now lets go more indepth into what a project is, characteristics of a project, why projects fail, and also discuss in detail project management.


What is a project?
According to Prince2 (Projects in controlled environments version two), ''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.'' and PMP definition of a project is '' Any temporary activity/ task/ endeavour to achieve a defined objective or to produce a unique/ new result, product document or deliverable.

Characteristics of a project
Temporary: Temporary means that every project as a definite beginning and a definite end. The end of a project is determined when the objectives aimed to be achieved are met or when it is quite clear that the objectives can be met or when there is no continued business justification. Being temporary does not mean that projects must be short in duration, because there may be some complex projects that require a lot of time but are still temporary to the nature of the business.

Also being temporary does not mean the results emanating from the projects would be temporary. This can be justified in the sense that when projects become a success for the organization, the result of the project becomes infused in the Business-as-usual part of the organization and it becomes a core part of the daily operations of the business. So it has phased out from being a project to a business-as-usual. For example a project to make a new phone remains a project when designing,making prototypes, implementing changes in design and so on. But as it becomes a success and appeals to the general public, it phases out from being a project into the normal operation of the business because the organization would continously produce more of the successful product to satisfy the demands of the public. So it goes from being a project to Business-as-usual.

Most projects are undertaking to create a lasting outcome. For example a project to build a new factory would create a result expected to last the years to come. Projects also may often have intended and unintended social, economic and environmental impacts that far outlasts the projects themselves.



Unique: Project should be unique and also the result of the project. For example as a wedding planner they cant be two weddings that would be exactly alike, so even if it is basically ''weddings'' being planned each wedding is still unique. So also in the case of a project, prescence of repetitive elements does not change the fundamental uniqueness of a project.




Change: A project is undertaken mainly for the purpose of change, either to produce a unique product, document or deliverables or to improve on existing ones.

Cross-functional: Projects cannot be undertaken on its own, it needs a team building exercise where people would come together and have specific tasks or jobs to perform for the overall success of the project. So in other words, a project involves a team of people.


Uncertainty: Risk introduces threats and opportunities. The outcome of a project can result into success or failure.




Why do projects fail?
Some of the reasons why projects fail include:

  1. Insufficient attention to checking if valid business case exists
  2. Insufficient attention to quality
  3. insufficient definition of the required outcome
  4. inadequate definition and lack of acceptance of project management roles and responsibilities
  5. inadequate and wild estimates of durations and costs
  6. Poor planning and coordination of duration and costs
  7. lack of communication with the different stakeholders
  8. lack of quality control.


PROJECT MANAGEMENT

Project management is the planning, monitoring and control of all aspects of a project and the motivation of the people involved to achieve the objectives within the performance target. It can also be defined as the application of knowledge, skills and techniques to meet project requirements. The person responsible for achieving a project's objective is the project manager. Steps in managing a project includes.

  1. Identifying what would be the basic requirements for the project
  2. Establishing objectives to be achieved which are within reach when the people involved are motivated.
  3. Balancing the six variables within projects which are: Time, Cost, Quality, Scope, Risk and Benefits.
  4. Adapting the specifications, plans and control to different concerns and expectations of the various stakeholders involved in a project.

Project managers often talk about three of the variables which are time, scope and cost being the most important of a project, because often times, a project as a deadline to meet, they have to deliver the desired quality of product or service within the scope while still keeping it within budget. So any change in these three variables affects product quality. So it is essential for a project manager to successfully balance these three variables.

Also another variable the project manager should consider is the risk. Risk being an uncertain event or condition that if it occurs, has a positive or negative impact on at least one of the project objectives.