PM² Tools & Techniques

Abstract

The publication presents a set of tools and techniques from different areas of traditional and agile project management, programme management, portfolio management, aiming to support the delivery of high quality results. Each tool or technique provides a high-level overview, and guidelines on how to use it.

Introduction

The publication presents a set of tools and techniques from different areas of traditional and agile project management, programme management, portfolio management, aiming to support the delivery of high quality results. Each tool or technique provides a high-level overview, and guidelines on how to use it.

This publication should be useful and complementary to the training and professional experience of the users and support the increase of productivity by using them.

Please note the presented set of tools is not the complete set, and should be considered as a good start to support the work.

Should you need more information on the presented tools and techniques, or any other, please feel free to consider open source information available on the market.

Portfolio Repository

#PortfolioManagement #Reporting #InvestmentMonitoring

The purpose of a project portfolio repository is to provide a central database for managing and maintaining programmes, projects, resources, and other business information to support decision-making on investments.

This tool allows the evaluation, selection and prioritisation of programmes and projects, as well as the optimisation of the usage of resources and the mitigation of risks, to realise the expected business benefits from organisation's investments.

The project portfolio repository should be populated frequently with key information of programmes and projects proposals and updated with the status of existent investments. This tool should divide investments into different portfolio management stages such as proposals, active, retired and excluded programmes and projects, to give a clear view of the portfolio status and support necessary actions and the traceability of the decisions already taken.

A diagram of a company AI-generated content may be incorrect.

Figure 1: Relationship between portfolios, programmes and projects

This tool will support project portfolio management processes and make available a repository of investments categorised by a common set of characteristics, as described below.

Step 1: Identify key information for decision-making

Identify which information from programmes and projects is necessary to support decision-making, such as project type, scope, deliverables, governance structure, need & urgency, outcomes, impact, dependencies, synergies, risks, duration, and effort (budget and resource needs).

Define key attributes with standard variables, so information can be easily compared. For example, programmes and projects should be grouped in a way that key attributes are comparable. Identify the characteristics of each group and the criteria to evaluate each investment within a group.

Step 2: Group organisational investments

Investments may be grouped into one portfolio or divided by multiple portfolios, representing e.g. business units, geographical locations, or business domains. The choice of one portfolio versus many depends on the size of the organisation, its structure and the nature and relationships among the projects. One single portfolio may allow greater optimisation but also provides more complexity for the analysis.

Projects and programmes should be classified and grouped into categories to facilitate decision-making and to better allocate resources. Multiple schemes can be used so that each project is classified in several different ways. The key idea is to provide a classification scheme that will be most useful for decision-making within the organisational context. Relations between projects should be identified to assist the grouping of projects into the same programmes/initiatives and to better manage risks and resources.

Additionally, investments should be listed into different inventories considering their stage within the portfolio management cycle, e.g. proposals, active, retired and excluded investments.

Step 3: Define the portfolio rules within the project portfolio repository

Define procedures related to portfolio roles and responsibilities. Define standard workflows and identify the templates supporting the portfolio management processes. Develop stage-gates reviews of investments throughout their lifecycle.

Define guidelines and techniques for the selection, evaluation, authorisation and prioritisation of organisational investments and the management of portfolio risks and resources. Use the project portfolio repository to support and document the result of these activities.

Value vs Complexity Matrix

#PortfolioManagement #ProjectEvaluation #ProjectPrioritisation #InvestmentMonitoring

A Value versus Complexity Matrix is a technique aimed to support projects evaluation and prioritisation within a portfolio,

The portfolio manager may identify a set of projects or tasks that need to be evaluated and prioritised. Ratings are assigned to the different projects or tasks based on factors, such as “Value to Customer” and “Value to Organisation”. Weights are applied to each of these factors to calculate their “Business Value”. Similarly, the “Implementation Complexity” can be calculated based on the effort required in man-hours, schedule and resource availability. These two scores are then plotted for all the projects or tasks on a “Value versus Complexity” matrix as shown in the figure below.

For projects evaluation and prioritisation, the different projects or tasks fall into four quadrants of the Value versus Complexity matrix:

A white grid with black text AI-generated content may be incorrect.

Figure 2: An Example of the Value versus Complexity Matrix

Below are the steps to create and use a Value versus Complexity Matrix.

Step 1: Identify the set of projects or tasks

Step 2: Define Business Value Measures

Step 3: Define Implementation Complexity Measures

Step 4: Analyse the prioritisation matrix

As a result, priorities and value-added investments are identified and prioritised, and the limited resources of the organisation are allocated to these tasks rather than to those that provide little value.

Gap Analysis

#PortfolioManagement #ProgrammeManagement #ProgressMonitoring #Reporting

The gap analysis is a technique that can support portfolio managers in portfolio progress monitoring or programme managers in programme progress monitoring by comparing the current and the desired performance state of a portfolio or programme components. This technique also helps to understand the portfolio/programme performance and identify the actions to implement to achieve the desired performance state.

The comparison of current and future states can be done in either qualitative or quantitative terms. Taking the example of the portfolio level, the portfolio manager identifies the factors which need to be analysed to perform a gap analysis between the current and the desired performance state of the portfolio components. These factors could be analysed through qualitative reports, performance metrics, performance ratings, etc. Additional benchmarking to compare the current performance with best practices process performance could also enhance the quality of the gap analysis.

The result of a gap analysis could be depicted on charts to visualise the differences between the states, as in the figure below. In the chart below, there is a difference identified in performance measurement for each factor. The portfolio manager should focus on the different factors that are identified as having the biggest gap between the current and desired performance of the portfolio components. Other charts like line graphs or histograms can also be used.

A graph of a hexagon with numbers and a number of objects AI-generated content may be incorrect.

Figure 3: An Example of the Gap Analysis Model

The steps below should be followed to conduct a successful gap analysis.

Step 1: Identify the future state

Define the portfolio objectives that need to be achieved. Identify the factors, which could be qualitative or quantitative, that one needs to measure to achieve the portfolio objectives. The factors could be benefits delivery, resource utilisation, costs, projects completion, risk level, etc. The portfolio manager sets the target for each of these factors to monitor the portfolio performance.

Step 2: Analyse the current state

Identify stakeholders to capture the current performance of the portfolio components. The portfolio manager should identify the best method for data collection. This could include one-to-one interviews, brainstorming workshops, meetings, reviewing documents or report generation, etc.

Identify the current performance in the same qualitative or quantitative format as in the case of the desired performance factors.

Step 3: Perform the gap analysis

The current performance is compared to the desired performance of the portfolio. Based on the different qualitative and/or quantitative factors, gaps are identified.

Step 4: Identify actions to reach future state

The importance of each factor and the magnitude of difference between future and current state would drive the prioritisation of actions to be taken. The portfolio manager, along with the portfolio steering committee, can brainstorm on the actions to be taken for each factor to bridge the gap between the future and current state.

Table 1: An Example of the Gap Analysis Matrix

Current State Future State Gap Actions to be taken
Qualitative Factors
Qualitative Factors

The above template could be used for a gap analysis to capture the factors for both future and current state. The quantitative factors could later be plotted on charts for a better visualisation and understanding of the gaps. The objective is to come up with actions to be taken that bridge the gap between the current and future state and to continue to drive in that direction.

Cost Benefit Analysis

#PortfolioManagement #ProgrammeManagement #BenefitManagement #PortfolioOptimisation

Cost benefit analysis or benefit cost analysis is a technique for estimating the strengths and weaknesses of portfolios/programmes/projects and to determine which ones provide the best balance, meaning more benefits/strengths and fewer costs/weaknesses. In this analysis costs and benefits are expressed in monetary terms over time to allow a common basis for comparison.

This technique may be used to support decisions on investments and to allow comparison between portfolio/programme components.

A white sheet with black text and numbers AI-generated content may be incorrect.

Figure 4: Examples of Ratios for Cost Benefit Analysis

The steps below should be followed to apply the technique on a portfolio components.

Step 1: List the programmes/projects within the scope of the analysis

List projects in the scope of the analysis and collect the relevant information for analysis. The portfolio manager should consider all the significant costs and benefits, tangible and intangible. Costs can include the Total Cost of Ownership (TCO) of the programmes/projects, as well as indirect costs related to the impact of the programme/project on the organisation. The portfolio manager should also take into account the factors external to the portfolio, such as dependencies on some organisational goals or other organisational priorities. Benefits may be related e.g. to the reduction of operational and infrastructure costs, time saving, compliance to legislation, increase of quality or the creation of value to a certain population.

Step 2: Select the measurements that best fit the organisation

Select the measurements depending on the degree of precise information available and the type of programmes/projects in the scope.

Step 3: Measure all costs and benefits over the selected period

Convert costs and benefits into the same monetary terms. Estimate the probability that each cost and benefit is correctly calculated. Assess risks related to estimations. Consider costs and benefits accrue over time, by use of discounting technique, meaning reduce all future costs and benefits to express them as today’s values.

Step 4: Apply the selected ratios

Apply the selected ratios and obtain the evaluation results for each component. Examples of ratios are the Economic Net Present Value (ENPV), Economic Rate of Return (ERR) and the Benefit-Cost (B/C) ratio.

Step 5: Analyse results and select the best programme/project/set of projects

Compare the evaluation results of each component, rank them and select the one(s) with the best score(s).

Life Cycle Cost Analysis

#PortfolioManagement #TotalCostOwnership #ProjectPrioritisation #PortfolioOptimisation

The Life Cycle Cost (LCC) analysis is a method of measuring or estimating the total cost of ownership of the product or service resulting from a project, for example an IT system. Many methods of total cost estimation only take into account the initial costs or development costs of an investment, meaning the cost of a project itself. However, these estimates fail to take into account the cost of maintaining the product or service during its lifecycle, i.e. the maintenance or operations costs.

The LCC analysis can be generally used to calculate the Total Cost of Ownership (TCO), to build a project portfolio, as well as to prioritise the portfolio components based on the financial requirements and benefits of the projects. For example, when developing a service, requirements can be prioritised based on the LCC analysis. If, for example, the run costs of a cheap-to-build requirement are high, taking into account the total cost of ownership may result in a different prioritisation or management decision.

A graph of growth of a company AI-generated content may be incorrect.

Figure 5: Life Cycle Cost Graph

An example of a Life Cycle Cost Graph for a project that creates a product with a lifecycle of 10 years is shown in the Figure above. As the Figure shows, the development costs associated with the project are high early on and disappear quickly after the first years. Even though the annual operations costs may be perceived as relatively small compared to the development costs, their amount is twice as much as the build costs over the entire lifecycle of the product or service. Therefore, it is important to take into account the Total Cost of Ownership of a project.

When building the LCC, several elements should be taken into account. The elements shown in the list below are relevant to most types of projects:

Life Cycle Cost analysis provides an input for decision making with regards to a project and its result. However, there could be other criteria to take into account:

SWOT Analysis

#PortfolioManagement #ProjectEvaluation #ProgrammeManagement #InvestmentMonitoring

The SWOT analysis or Internal-External analysis is very useful when evaluating projects/mix of projects or different approaches/scenarios. It analyses the strengths, weaknesses, opportunities and threats of projects/scenarios, perceived by several stakeholders, in a qualitative way.

When performing the analysis, the portfolio, programme or other manager should consider the impacts in several domains such as organisational change, cost, time, quality, business value, alignment with strategy and impacts on other projects, assets or services.

The strengths and weaknesses (internal factors) of the project/scenario can be found by evaluating its intrinsic characteristics and by comparing it with other projects/scenarios. The opportunities and threats (external factors) are identified by investigating the interactions of the solution/scenario with the organisational and external environments. The SWOT analysis could be documented in a table as the one represented below:

A white rectangular object with a black border Description automatically generated with medium confidence

Table 2: SWOT analysis table

Step 1: Specify the objective of the SWOT analysis

Document the purpose and the scope of the analysis.

Step 2: Assess the strengths of the solution/scenario

Assess the strengths of the project/scenario. Focus on the quality of the outputs, benefits to the organisation, the characteristics that positively distinguish it from others and the existence of adequate competences and resources.

Step 3: Assess the weaknesses of the solution/scenario

Assess the weaknesses of the project/scenario by focusing on what is missing to cover all the needs and achieving the expected outcomes. Compare with other solutions/scenarios and identify which characteristics are missing.

Step 4: Identify opportunities within the solution/scenario

Identify opportunities in the internal/external environment that can be exploited to increase the benefits of the solution/scenario. Opportunities may come from new technology, new legislation, changes in the organisational environment, special financial conditions, available knowledge and products/services, etc.

Step 5: Identify threats within the solution/scenario

Threats are events that can negatively impact the solution/scenario if they happen. In this case, the manager should try to minimise all the significant threats related to one solution/scenario.

Step 6: Select the best solution/scenario

Select the best solution/scenario based on the analysis performed. Justify why the selected alternative/solution is the best one comparing to others.

Key Performance Indicators (KPI's)

#PortfolioManagement #ProgrammeManagement #Reporting #InvestmentMonitoring

Key Performance Indicators (KPIs) are quantifiable metrics that provide an indication of key performance measures of a project, programme or a portfolio.

Taking example of a project, it is important to distinguish between two types of project related KPIs. The first type covers project performance KPIs, which measure the performance of an ongoing project and are usually related to Earned Value Management (EVM) metrics. The second are used to measure project progress towards the objectives or goals of the project. The project goals are directly linked to the quality, benefits, and project performance. These goals can only be achieved when all sub-goals are obtained. These sub-goals can be identified as the Critical Success Criteria (CSCs) of the project. The quantifiable metrics used to track the progress of these CSCs are KPIs. Using both types of KPIs is best practice in project communication and reporting and increases the likelihood of buy-in from project sponsors and stakeholders.

KPIs should be selected based on the top priority goals of the project. Various stakeholders should be identified to review the metrics on a continuous basis and provide guidance in case of any identified variations. Benchmarks could be set for the metrics to set the expectation levels. Portfolio Managers should have periodic meetings with Programme or Project Managers and other stakeholders to monitor KPIs and provide feedback.

A diagram of a business model Description automatically generated

Figure 6: KPIs Framework

As mentioned earlier, there are two types of projects related KPIs. Those dealing with project performance are usually based on EVM, and hence are relatively easy to define. KPIs measuring the achievement of overall project goals and objectives are much more difficult to define. The figure above illustrates the KPIs framework, which shows the relationship between goals, CSCs, KPIs and resulting activities.

Some examples of KPIs that apply to portfolio are listed in the table below:

Table 3: An Example of Portfolio KPIs

Category Considerations Measurements
Portfolio Mix What percentage is the portfolio aligned to strategic objectives?

% of portfolio spend to "run the business"

% of portfolio spend to "grow the business"

% of portfolio spend to "innovate the business"

% of portfolio spend with short / medium or long term projects

% of portfolio spend in large or extra-large projects

Demand and Capacity Do we have the right prioritisation and sequencing of projects given current capacity?

% of growth in project intake

% of growth in initiatives

Resource Utilisation (Budget, People or Assets)

Recruiting pipeline

Value For our portfolio, what extent did we achieve our objectives?

% on time

% on budget

Portfolio Health For programmes / projects in-flight, how is the execution progressing?

Counts and amounts for programmes, projects or activities

# of issues by severity

Financial Management How effectively are we managing programme and project budgets?

% variance to plan

% funding of in-flight

Although not a simple exercise, it is important to define both portfolio/project performance and objective oriented KPIs. The following steps provide a high-level guideline to define such KPIs:

Step 1: Define project goals

Step 2: Determine measures for the goals

Step 3: Define KPI's

Step 4: Determine activities to reach the goals and carry them out

Step 5: Establish reporting

While analysing which activities contribute to the relevant KPIs of the portfolio/project, other activities might not lead to project goals. Portfolio Managers should try to minimise resource utilisation for such activities and keep focusing on activities related to the KPIs.

What If Scenarios Analysis

#PortfolioManagement #ProjectEvaluation #RiskManagement #InvestmentMonitoring

The purpose of the ‘what if scenarios analysis’ is to build several alternative solutions using the combination of current and potential projects and analyse the impact of each solution on the portfolio performance and value. ‘What if scenarios’ are based on a set of assumptions and conditions that need to be carefully evaluated to be as realistic as possible, so, costs, scheduling, dependencies, synergies, benefits and impacts should be precisely estimated.

A diagram of a decision Description automatically generated

Figure 7: Decision Tree Approach

This technique will support the analysis of the optimal mix of investment within the portfolio considering the resources capability. The analysis is performed through the following steps:

Step 1: Define portfolio objectives and expected benefits

Define the objectives of each component within the portfolio and identify the expected benefits during the period under analysis. These benefits should be translated into metrics.

Step 2: Collect the relevant information

Identify the key success factors, external events and risks that may impact the delivery of the expected benefits. Identify dependencies and possible synergies within the portfolio. Determine portfolio human resources and budget capability.

Step 3: Document alternative scenarios

Document different scenarios and assumptions. Deeply analyse assumptions to be as accurate as possible. For the ones that there is an "uncertainty", quantify the likelihood of occurrence and the impact on the final result. List these assumptions per impact on the final result, and for the significant ones estimate an "intermediate" output between an optimistic and a pessimistic scenario. The Portfolio Manager may combine this technique with the Monte Carlo Simulation technique for the analysis of complex combinations of uncertainties. The development of scenarios should consider the variety of the investments (strategic, maintenance, performance enhancement) and the coverage of organisational objectives (investments in different portfolio categories).

Step 4: Analyse the different scenarios for portfolio optimisation

Analyse the impact of the different scenarios on the portfolio performance and on the creation of value to the organisation. Verify which scenario uses fewer resources and creates more value to the business considering the organisation's risk appetite.

Activity Based Costing

#TotalCostOwnership #ProjectManagement #CostMonitoring

Activity Based Costing (ABC) is a method for estimating costs that first identifies activities within an organisation and, subsequently, assigns the cost, taking into account all products and services that were consumed for each activity. The model differs from traditional cost calculations, which assign costs based on the resources linked to that service. The ABC model also assigns more indirect costs compared to only direct costs in the traditional way.

In a project context, ABC can be used to estimate the cost of a project based on a set of activities as the drivers (ex. by project activity actually performed), rather than by simply summing direct costs (ex. summing the total headcount cost).

The aim of the ABC method is to identify and eliminate activities or services that seem to have a low (or the lowest) return of investment. The costs are assigned according to the cause-and-effect relationship between activities and cost objects, which is captured using drivers. These drivers are related to the actual process and can occur at the following four levels:

There are two types of cost drivers that should be considered while using the ABC method:

A diagram of a project Description automatically generated

Figure 8: Activity Based Costing Framework

Activity Based Costing assigns the overhead costs of services in a more logical manner than the traditional cost calculation. The Activity Based Costing method is also commonly used for taking strategic decisions such as pricing, outsourcing, identification and measurement of process improvement initiatives.

These are the steps when using the Activity Based Costing method:

Step 1: Identify needs

Step 2: Define project context

Step 3: Create a cost structure

Step 4: Collect data

Step 5: Report costs

The Activity Based Costing method can be helpful in cost analysis to identify where and why costs may be higher than expected. The method also identifies the factors related to the cost of quality, which provides data and insights to improve the quality of service.

As the Activity Based Costing method is a process-oriented method, it gathers information from the processes about the effort required and the kind of resources needed. It gives the project manager the ability to match as closely as possible the resource needs of the project. Over time, using the Activity Based Costing method leads to an increased cost efficiency and better use of the available resources.

Benefits Tracking

#PortfolioManagement #ProgrammeManagement #ProjectManagement #BenefitManagement

Benefits tracking can be used by organisations to measure the degree of achievement of the intended portfolio or programme benefits. Benefits tracking can start as soon as the programme/ portfolio component (e.g. project) is initiated and implemented throughout the component lifecycle and until long after its completion.

Benefits tracking usually involves the creation of a benefit plan matrix in which lists of intended benefits are documented and Key Success Factors (KSFs) and Key Performance Indicators (KPIs) are defined. This matrix should be tracked throughout the duration of the projects within the programme/portfolio. After completion of each project, the identified benefits should continue to be reviewed and analysed to define development areas and measure project results using metrics.

Among challengers that senior managers face in tracking projects benefits are the following:

Remember that benefits tracking should not stop at project completion, but tracked until their target outcomes are achieved, which is often beyond the life of the project.

Table 4: An Example of Benefits Tracking Matrix

Project Project Name
Desired Benefit
Description
Stakeholders Impacted KSF KPI Baseline measure Responsible Target Date
<Benefit 1>
<Benefit 2>
<Benefit 3>
<Benefit 4>
<Benefit 5>

Below is a summary of the key steps of tracking benefits of a project.

Step 1: Define and develop the benefits:

Step 2: Develop the benefits plan:

Step 3: Monitor the benefits during project implementation:

Step 4: Review the benefits:

Benefit tracking should continue even after the completion of the projects. It should at least start before a project review is executed as to show the direct results from the projects. In benefits tracking, the project manager role should be to drive the benefit initiatives by means of working closely with the programme/portfolio manager and with other stakeholders of the project.

The Balanced Scorecard Approach

#PortfolioManagement #ProgrammeManagement #BenefitManagement #Reporting

The Balanced Scorecard (BSC) is a strategy performance management tool that enables organisations to translate strategy into implementation, and to measure the performance of activities from four perspectives: Financial, Internal Business Processes, Learning and Growth, and Customer. In the context of projects, the Balanced Scorecard Approach can be used to continually assess the progress of a set of projects par of a portfolio or a programme towards the defined strategic goals and objectives. For example, accurate reporting may be a key objective of the organisation, hence, we can assess projects based on their contribution to accurate reporting.

Various examples of metrics that can be tracked under the four perspectives of a Balanced Scorecard are shown below. Note that these are examples originally used by the creators of BSC and that they can be adapted to fit the organisational needs:

For each metric under the four perspectives the portfolio or programme manager sets a target and analyses the metric in order to track the portfolio or programme performance based on the following:

The Balanced Scorecard approach thus retains the traditional way of checking financial data along with other relevant perspectives to provide an overall view of portfolio performance.

A diagram of a business strategy Description automatically generated

Figure 9: Balanced Scorecard Framework

The Balanced Scorecard is a standardised tool to track performance towards specified and defined objectives. Below are the steps of the Balanced Scorecard approach for a portfolio.

Step 1: Define portfolio objectives

Step 2: Define portfolio performance measures

Step 3: Monitor portfolio objectives achievement

Step 4: Adjust where necessary

The strategic objectives under the four perspectives are also known as a Strategy Map, as it outlines the overall strategy to achieve the portfolio objective. The Balance Scorecard enables the portfolio manager to execute strategies using the Strategy Map. It also alerts the project managers and other stakeholders when projects performance deviate from the objectives.

Bubble Diagrams

#PortfolioManagement #RiskManagement #ProjectEvaluation #PortfolioOptimisation

Bubble Diagrams represent a type of diagram that can be used to visualise data points which have three values. It displays a circle (the "bubble") in a certain position versus two orthogonal axes. Two values are used to determine the position on each axis, while the third value determines the size of the bubble. In a more advanced form even more values per data point can be indicated using the bubble's color, fill pattern, etc. Since this makes the interpretation of the diagram more complex, it is advised to limit the values to three per data point.

A graph of value vs risk Description automatically generated

Figure 10: Value-Risk Bubble Chart

For example, bubble charts can be used to compare the value, risk and cost of projects (see figure above). Projects with a high value, low risk and low cost can be easily distinguished this way.

Below are the steps to create a bubble chart for visualising data points with three values.

Step 1: Gather the data

Step 2: Create the chart

Monte Carlo Simulation

#PortfolioManagement #RiskManagement #BenefitManagement #PortfolioOptimisation

This technique aims to analyse the impact of risk and uncertainty on forecasting models, using computational algorithms that rely on probability distribution sampling to produce hundreds or thousands of possible outputs. From the results, the portfolio manager will get the probabilities of occurrence of each event.

When analysing the best mix of investments within the portfolio, it cannot be ensured what is the actual value of these investments because of the uncertainty of events that may happen in the organisational internal and external environment. Considering this, the portfolio manager needs to estimate the expected value based on several techniques such as benchmarking, historical data, and expertise in the field, although these estimations will still contain some uncertainty.

The Monte Carlo simulation uses a range of possible values to create a more realistic projection of the future. Equally, the output of the simulation will be a range of possible values, showing how likely the events are. A random value is selected for each of the events, based on the range of estimates. The model is calculated based on this random value. The result of the model is recorded, and the process is repeated. A usual Monte Carlo simulation calculates the model hundreds or thousands of times, each time using different randomly selected values. The large number of results from the model will be used to describe the likelihood of reaching various results in the model.

This technique is based on probability distributions that may be from different types such as Normal, Lognormal, Uniform, Triangular, PERT or Discrete.

The example below shows a model for estimating the total duration of a project using a PERT distribution (defines the minimum, most likely and maximum values). The simulation ran 500 times, and the results show that the probability of the duration of the project being less than 14 months is below 35% and there is a change of nearly 80% that the project will take 15 months.

A graph of a number of people AI-generated content may be incorrect.

Figure 11: Example of a Monte Carlo Simulation – Probability of completing a project within a specified time (months)

This technique will estimate the probability of events to happen in the future, as described in the following steps: Step 1: Define what needs to be estimated

The Portfolio Manager should first define the purpose and the scope of the estimation.

Step 2: Establish the model to be used

Step 3: Run the model and produce several samples of simulated data

Step 4: Examine the results of those samples

Analyse the results and determine which events are more likely to happen.

Capability Maturity Models (CMM)

#MaturityAssessment #ProcessOptimisation #InvestmentSelection

Capability maturity models enable organisations to benchmark processes with good practices, identify areas that can be improved and communicate them to management. There are several tools that provide a systematic way to assess organisational level of maturity to support establishing the "to be" / expected level and developing the required roadmap for increasing the maturity level.

Senior management is usually asked about how well processes and services are being managed, how they will be managed in the future and which investments should be performed. This tool can be used for selecting the right investments for the organisation, considering the main deficiencies identified through the Capability Maturity Models.

A line of arrows and stars AI-generated content may be incorrect.

Figure 12: Graphical Representation of Capability Maturity Models

The objective of using a maturity model is to help an organisation to assess its level of processes optimisation and support developing a roadmap to achieve the expected/agreed-on maturity level, as detailed in the following steps:

Step 1: Assess the current level of processes maturity

For the selected process, use the process-specific maturity model to obtain the high-level assessment. Maturity models are normally based on five generic levels, as following:

Document the analysis and detail the actual capability for each activity/task of the process. Determine the maturity rating based on the level obtained for different activities/tasks.

Step 2: Establish the target maturity/capability level

Senior managers need to identify the desired capability target level, considering legal requirements, resources constraints, organisational culture, and business objectives. A top-down approach should be used, starting from the identification of the strategic objectives down to the level of processes optimisation required to achieve these goals.

Based on the selected CMM, verify for each process what the expected maturity level corresponds to. Define Key Performance Indicators to measure whether the goals are met.

Step 3: Develop a roadmap to achieve the target capability

Elaborate a gap analysis to determine what needs to be done to achieve the chosen level. Identify the required actions and prioritise them in time. Look for "quick wins" and implement these actions first.

Step 4: Assign roles and responsibilities

Assign an owner to each action and detail the roles and responsibilities of everyone involved.

Step 5: Detail the action plan for each identified deficiency

Detail the objectives, deliverables, major milestones, scheduling and resources required to implement each action. Make sure that resources will be available.

Step 6: Monitor and control the implementation of actions

Regularly monitor the status of each action and evaluate if any change is needed to obtain the expected benefits. Update the action plan with the progress of each action and define new actions if necessary.

Step 7: Re-assess processes maturity level

Re-assess the processes' maturity level at a predefined time. The implementation of the actions will not increase immediately the processes' maturity level, as new processes/controls need to be operating in a consistent way and widespread.

Effective Communication

#StakeholdersManagement #StakeholderCommunication #TeamCollaboration #Reporting

Communication is the process of exchanging information and ideas. It is an active process as it involves encoding, transmitting and decoding of messages.

The sender of the information will, first of all, transform the message in a way the receiver can understand it. Secondly, he needs to find a mean to transmit it to the receiver. And the third step is when the receiver has to decode the message to understand it.

This is a process that everybody does on a daily basis and we hardly think about it when performing it.

Communication becomes effective once the message is understood by the receiver as intended by the sender. For example, the sender in verbal communication could consider the following skills, as shown in the figure below:

A blue oval with white text Description automatically generated

Figure 13: Effective communication

For example, the following could be considered:

Also bear in mind that the more persons or groups are at the receiver's side the harder it becomes to have your message transferred in a clear and concise manner. Thus, you could consider to limit the audience for your message and send several messages to smaller groups.

Effective communication helps in problem solving and conflict management. It is not a tool that you can download and run every time you have a message to transmit. It is more a technique where guidelines can be proposed, and it is up to the sender to decide what is the best way to communicate the message to the receiver(s).

For starting and facilitating the effective communication, you can follow the steps below.

Step 1: Encoding the message

Step 2: Transmitting the message

Step 3: Decoding the message

Running Effective Meetings

#StakeholdersManagement #StakeholderCommunication #TeamCollaboration #Reporting

Managing a project, many projects or a programme, managing portfolio, etc., involves organising, coordinating and/or attending many meetings with various purposes, for example:

The ability and habit of running these meetings efficiently and effectively means that they are focused on set goals, achieve expected results, help the efficient management of the project/programme/portfolio and actually positively contribute to the time management of the involved teams and stakeholders.

In several organisations, people can lose a lot of time in project/programme/portfolio related meetings that lack a clear agenda with set expectations or finish without a set of follow-up actions. It is very important to set and understand the objectives of the meeting to design the meeting in the most effective manner. The following list provides a description of the most common types of meetings:

A diagram of a meeting Description automatically generated

Figure 14: Meeting Process

The figure above provides a set of general steps that should be taken to ensure that meetings are run efficiently and effectively. This model focuses on thoroughly preparing the meeting to ensure attainment of the objectives, and to improve communication and follow-up past meeting. The overall concept is to be more focused and concise, and to ensure that meetings result in a set of key actions with action owners.

For running effective and efficient meetings, one can follow the steps below.

Step 1: Prepare for Meeting

Step 2: Conduct Meeting

Step 3: Communicate Actions

Step 4: Review Actions

For larger or longer meetings, and particularly for brainstorming meetings, it is helpful for the meeting organiser, apart from main speakers, to have someone to support all the record keeping and assisting in the facilitation of the meeting. These activities include:

The organiser should take accountability of the meeting and ensure that the discussion runs smoothly. Do not hesitate to table, or put aside, topics that do not contribute to the meeting objectives, or are not part of the agenda. These can be noted and addressed outside the meeting. The focus of the meeting should be to collect constructive inputs from everyone present, and at the end of the meeting everyone should be aware of the key decisions and actions that must be taken care of.

The Eisenhower Matrix

#TimeManagement, #SelfOrganisation #Prioritisation #ProjectManagement #AgileProjectManagement

Projects are not run in a vacuum; they are run in an organisational context. As a result, during the life of the project, the project manager and team will get busy in the day-to-day activities and get involved into spending time on activities that do not directly contribute to the project goals. It is important to manage available time well during projects lifecycle by understanding the priority of activities. It helps to organise a To-Do list by focusing on the activities that need urgent attention and are important for achieving project goals. The Eisenhower Matrix is a simple tool to organise a To-Do list to effectively manage time during the execution of a project.

A grid of white paper with black text Description automatically generated

Figure 15: An Example of the Eisenhower Matrix

A To-Do list can be organised using an Eisenhower Matrix as shown in the figure above. The matrix categorises tasks into different quadrants based on importance and urgency. It is important to understand these two types of categories in order to organise activities during projects:

Based on the urgency and importance of activities, the Eisenhower Matrix categorises activities in the following four quadrants:

Once the activities or tasks of a project are categorised, the project manager can easily prioritise the tasks and activities within the project and communicate them to the project team, as well as organise a To-Do list and optimise the personal time spend on a project.

Below are the steps that one can follow to create and use the Eisenhower Matrix.

Steps:

Different response strategies should be employed for the activities categorised in the four quadrants.

Do Now - Critical Activities - Urgent, Important

Schedule for later - Important Goals - Not Urgent, Important

Delegate - Interruptions - Urgent, Not Important

Do not do - Distractions - Not Urgent, Not Important

It is important to prioritise activities and understand what contributes to the project and what does not. Using a standard prioritising method like the Eisenhower Matrix helps to keep the focus on important activities that lead to the achievement of project goals and objectives.

Tuckman's Model of Team Performance

#TeamManagement, #SelfOrganisation #ProjectManagement #AgileProjectManagement

In the context of a project, teamwork should be effective and well guided by the project manager. However, it usually takes time and effort before a good level of effective teamwork can be achieved, as team members go through different stages of group development regarding understanding the group behaviour and supporting each other in the establishment of project deliverables.

In the FSNPA model, developed by Bruce Tuckman, he stated that any group goes through five different phases of team building before it can start performing effectively. It is important for a project manager to understand these stages in order to guide the project team towards an improved project team performance. The five stages of group development are described below.

It ultimately becomes the responsibility of the project manager to help the team reach the performing stage as early as possible in the project and sustaining it as long as necessary. Project managers should be able to adapt their management approach according to the stage the project team is in order to facilitate the team development.

A diagram of a storming curve Description automatically generated

Figure 16: The Tuckman Model (FSNPA)

Below are the five stages of team development, within the Tuckman’s Model, that project teams undergo with the aim of reaching a high level of team performance.

Stage 1: Forming

Team Members:

Project Manager:

Stage 2: Storming

Team Members:

Project Manager:

Stage 3: Norming

Team Members:

Stage 4: Performing

Team Members:

Project Manager:

Stage 5: Adjourning

Team members:

In order to improve the project team performance, the main focus of the project manager should be to understand the stage of group development the project team is currently in. The model also states that due to changes in the project environment, the project team may tend to return to the previous stage of the Tuckman Model. These changes in the project environment could be a new project Manager, a change in project team members or changes in the project goals or objectives. Whenever this occurs, it is important to go through the different stages of the Tuckman model again.

Stakeholder Importance-Influence Matrix (SIIM)

#StakeholderManagement #StakeholderCommunication #RequirementsManagement

This technique is used to analyse and document the influence of each stakeholder in the project or programme or portfolio. Hereinafter, taking an example of a project, as a project manager, it is of the utmost importance to know the stakeholders and understand how they can impact the project goals.

The importance of a stakeholder indicates the extent to which the needs and interests will be prioritised by planned activities. This means that a stakeholder is considered important when their needs and interests gain a heightened priority when the team is in the process of creating and revising plans. Therefore, the stakeholder will be contacted quickly if their feedback is needed during a revision of the planning.

The influence of a stakeholder for the project is the power over the planning and implementation of activities. A stakeholder that can demand a change in the planning has a big influence on the project. For example, most of the time, the people that can allocate budget and/or resources to the project are considered to have a high influence.

A white grid with black letters and numbers Description automatically generated

Figure 17: An Example of Stakeholder Importance/Influence Matrix

Step 1: List the stakeholders for the project

Step 2: For each stakeholder, access the importance of the project

Step 3: For each stakeholder, access the influence he/she has on the project

Step 4: Plot the position in the matrix

Step 5: Read the specification for every stakeholder

Here, we lay out the four major parts in the table, and the way to handle them:

Part A: PROTECT: Stakeholders that have a great importance in the project but, unfortunately, have low influence. Special attention is needed to protect their interests as they don't possess the required influence to protect their own needs.

Part B: GOOD RELATION: Stakeholders that have a huge interest in and influence on the project. We need to create a close working relationship with them and agree on methods of communication besides the standard communication agreements. This can be, for example, a face-to-face update on a daily/weekly basis.

Part C: LOW PRIORITY: This group has a low priority for the project, and practically no influence, so your investment in them should be minimal. However, be aware that they keep a positive attitude for the project, so do not neglect them.

Part D: MONITOR: This group may be a source of risk since their influence is high, but the importance of the project is low for them. Thus, they need to be carefully monitored and managed to make sure that they don't lose their interest in the project or, even worse, become a blocking factor.

Work Breakdown Structure

#Planning #ProjectManagement #ProgrammeManagement

A Work Breakdown Structure (WBS) involves logical decomposing of a project into smaller work components. With support of WBS, the project manager can have a thorough picture of all the project needs, and, thus, see clearly how to manage its activities in an efficient manner. This technique can also be used on a programme level when planning programme components and milestones.

A project manager may use a WBS to decompose a project in stages, deliverables, activities, tasks, business units, etc. The project team members can support the project manager in identifying these lower-level tasks of the project.

While a WBS is a good way to decompose the work required for a project, it can serve as a good basis for the project work plan. It can provide the basis for the time, sequence and dependencies among work components, resource, and budget allocation.

Different WBS techniques can be used to decompose a large project into smaller and identifiable work components. Below are some of the commonly used techniques used by project managers to create a comprehensive and thorough WBS.

A diagram of a project Description automatically generated

Figure 18: An Example of the Work Breakdown Structure

The figure above shows an example to breakdown the work into deliverables, activities and tasks.

Below are the steps to create and use a Work Breakdown Structure in a project.

Step 1: Identify project goals, objectives, scope

Step 2: Determine the breakdown model

Step 3: Divide the work components

Step 4: Review the WBS

Optional Step 5: Extend the WBS into a project work plan

The project manager can use created WBS and with support of other techniques, can assign resources to the tasks, identify tasks sequences and dependencies, allocate budget per task, etc.

Efforts and Costs Estimates

#Planning #Estimation #ProjectManagement #ProgrammeManagement

The outcomes of the Work Breakdown Structure can be used as input for what is called the Cost and Efforts Estimate technique. It can be used in project management to extend the WBS into a project work plan, in programme management to estimate benefits realisation, etc.

Let’s estimate the required effort and associated cost with all of the work items. Then, we can match that estimate to an availability of resources. The project manager coordinates this estimation for each task in close collaboration with the task owners (or other experts) for each impact area (who are usually project stakeholders).

The following are different approaches to base the estimate upon for the finest detail level of tasks of a Work Breakdown:

The accuracy of the WBS is of the highest importance to get adequate estimates. When creating the WBS with the stakeholders, remember to mention to them that the better the WBS, the better the estimates.

The figure below is diagram that shows the relationship between the level of accuracy and the size of projects.

A diagram of a graph Description automatically generated with medium confidence

Figure 19: Size of projects versus Accuracy

Based on the above chosen approach (or a combination of approaches) the following steps can be followed.

Step 1: Look at the lowest level of the Work Breakdown.

Step 2: Estimate the amount of effort

Step 3: Include contingency

Step 4: The task owners must validate the effort estimates.

Step 5: Estimate the likely cost to be incurred on the activity (if it must be traced).

Step 6: Add non-people cost

Step 7: Finalise the estimate

Three-Point Estimates using PERT

#Planning #Estimation #ProjectManagement

Estimating project cost or duration is most often done based on estimates, and there can be various amounts of uncertainty on the accuracy of these estimates.

The Three-Point Estimate is a technique that forms part of the PERT (Project Evaluation and Review Technique) toolset. It is used to provide a weighted average of the various estimates of project time or cost. To perform a Three-Point Estimate, a project team is asked to provide 3 estimates for the duration of each activity defined in the Work Breakdown Structure (WBS). These estimates are then weighed to provide a weighted average of their effort, cost, or duration. In addition, these estimates can be used to calculate a standard deviation, which can then be used to estimate confidence levels of the weighted average per activity, as well as to build simple statistical models of task time and cost.

In very advanced project management practices, these statistical methods are applied to project management in order to forecast and mitigate risks, and to assign buffers to tasks.

The figure below shows a three-point estimate calculation for a project with five activities (from A to E). The numbers in the table represent the expected cost of each activity in man-days.

Table 5: Three-Point Estimate Table

Activity Predecessor a (best-case) m (most-likely) b (worst-case) E (expected) SD (standard deviation)
A - 10 13 17 13.17 1.17
B A 8 9 13 9.50 0.83
C A 6 7 12 7.67 1.00
D D 14 15 17 15.17 0.50
E B,C,D 4 8 13 8.17 1.50

These activities can be represented in a simple network diagram. Using the expected duration calculated, it is then possible to provide a simple view the Critical Path (CP) of the project.

The figure below shows an Activity on Node (AON) network diagram for this example of the project of five activities. The red arrows show the Critical Path (CP) of the project based on the expected duration calculated above.

A diagram of a flowchart

Figure 20: An example of AON Network Diagram

The three-point estimate is basically a weighted average of several estimates of activity duration or cost. The expected duration of a project and the standard deviation of its cost are found using the three-point estimate, calculated by the formulas below:

E = (a + 4m + b)/6

SD = (b – a)/6

Where E is the expected duration, a is the optimistic estimate of cost or duration, m is the most likely estimate, b is the pessimistic estimate, and SD is the standard deviation.

The three estimates forming the three-point estimate are defined as follows:

Optimistic value (a):

Most likely value (m):

Pessimistic value (b):

It is important to note that a basic assumption in the estimating process is that the three estimates are based on the same level of effort, for example the same number of persons working or the same number of shifts and days per week (i.e. 1 person day = 7,5 hours).

In addition, the three-point estimate is designed to capture and mitigate the uncertainty of providing a single estimate, and it is not designed to provide forecasts of buffers to mitigate changes to the fundamental conditions of the project. For example, the technique can be used because the project team is unsure of the difficulty of implementing some aspect of the project, and it is not used to capture the effects of a change in the scope of the implementation.

Lastly, it is also important to note that the three-point estimate technique does not mean that expert advice is no longer necessary to build project cost and duration estimates. While the technique provides a weighted average of three estimates, a large standard deviation will mean that the likelihood of achieving this expected cost or duration is very low. Involving experts to provide the three-estimates will increase the accuracy of the three-point estimate and reduce the risk or uncertainty of the project.

Project Scheduling

#Planning #AgileProjectManagement #ProjectManagement #ProgrammeManagement

The objective behind project scheduling is to identify dependencies between tasks, assign resources for each task, identify task start and end dates, and work out the overall project duration.

Scheduling can be done for the entire project upfront, or for portions of it (i.e. individual stages or iterations). Most of the time, a high-level schedule is established for the entire project and a detailed schedule is created for the upcoming months.

Different scheduling methods and representations can be used. For instance, a list of dates/deadlines, milestone plans, bar charts, network diagrams and linked bar charts can be used, which are often seen as complementary to each other. The effectiveness of each scheduling method (or combination of methods) depends on the type, size, complexity, dynamics, and other requirements of each project.

Below is a list of steps that a project manager can follow to create a project schedule. The sequence of these steps can vary depending on each project, and some steps can be considered as optional.

Step 1: Review for completeness

Step 2: Identify the dependencies and sequence between tasks:

Step 3: Identify the critical path

Step 4: Identify the resources for each task

Step 5: Availability of resources

Step 6: Official approval of the schedule

Critical Path Method

#Planning #AgileProjectManagement #ProjectManagement #ProgrammeManagement

The Critical Path Method (CPM) is a modelling technique that uses a mathematically based algorithm to calculate the total duration of a project. CPM calculates the longest necessary path (longest unavoidable duration) of planned activities from the beginning to the end of the project, otherwise known as the critical path of the project.

CPM is used widely in projects where enough detail can be derived, and estimates can be relatively accurate. CPM is particularly useful in projects with many concurrent activities, or in organisations running numerous concurrent projects. In these cases, resources are often shared across multiple activities or projects, and understanding where they are critical for timeliness is crucial to preparing the resource management plan.

Since the critical path represents the longest necessary path of activities, it also represents the shortest possible duration of the project to completion. If this duration exceeds the project deadline, activities can be prioritised in order to shorten the duration of the critical path. This is done by pruning the critical path activities, performing more activities in parallel (Fast Tracking) or shortening the duration of the critical path activities by adding more resources (Crashing the Critical Path).

A diagram of a diagram Description automatically generated

Figure 21: Critical Path Diagram

The figure above shows an example of the network diagram with a set of activities from A to H, along with the respective duration and interdependencies and the basic CPM analysis performed to find the critical path. The activities A, B, C, D and H form the longest path or the Critical Path (CP), whereas the other activities (E, F and G) are off the critical path and can be delayed or extended until a certain point without delaying the overall completion of the project.

The Critical Path Method is used to define the longest necessary path of activities for a project, and to understand which activities have a critical influence on the overall duration of the project. Below are the steps to identify the Critical Path:

Step 1:

Step 2:

Step 3:

Table 6: CPM Key Parameters

CPM Parameters Description of the Parameters
Early Start (ES) Earliest Time that an activity can start, given its preceding activities are completed.
Early Finish (EF) Earliest Start Time + Duration of the activity (EF = ES + DUR)
Late Start (LS) Latest Finish Time - Duration of the activity (LS = LFT – DUR)
Late Finish (LF) Latest time at which an activity can be completed without affecting the overall duration of the project.
Slack (SL) Time between the Early and Late Start or between the Early and Late Finish of an activity, and denotes the amount of delay the task can incur without affecting the overall completion of the project.
Critical Path (CP) The longest necessary path of activities to complete the project, or the shortest possible time to complete the project. The path of activities with the least amount of slack, generally zero - often indicated with red arrows.
Duration Time that an activity takes to complete

To perform a “forward pass,” start from the first activity (A, in figure above) and note the ES and EF, then move on to the next activity (B). The ES of the following activity will be the same as the EF of the previous one. Continue until all activities have an ES and EF.

Now perform the “backward pass.” Start with the last activity (E) and find the LF, which is the same as the EF for the last activity only, and then calculate the LS for the last activity. Moving backward, continue to the previous activity - -in this example Activity D - and note its LS and LF. Following the pattern, the LF for previous activity will be the same as the LS of the following activity.

The CPM method requires some accuracy or certainty of estimates regarding activity duration. In simpler projects, or in instances where there is high uncertainty regarding the estimates, it is advisable to use the three-point estimate and a simple network diagram to define the critical path. As estimates increase in accuracy, begin use the CPM to ensure the scheduling of project activities and to confirm the duration of the project based on a more accurate critical path calculation.

Gantt Charts

#Planning #AgileProjectManagement #ProjectManagement #ProgrammeManagement

A Gantt chart is a graphical representation, generally a type of horizontal bar chart, which illustrates a project plan and the duration of tasks against the progression in time. This project management tool, originally developed by Henry Gantt at the beginning of the twentieth century, focuses on the sequence of tasks necessary for completion of the project at hand.

The Gantt chart can be a very powerful visual tool to represent duration, sequence, dependency and status of the terminal or/and summary elements of an entire project. A Gantt chart visually represents the entire work breakdown of a project and allows the terminal elements (the lowest level of detail in the Work Breakdown Structure, for example, task) and the summary elements (the aggregate levels in the WBS, for example, Activity) to be easily identified.

Gantt Chart

Figure 22: An example of the Gantt chart

In a Gantt chart, such as the example in the figure above, each activity is represented as a single horizontal bar on an X-Y chart. The horizontal axis (X-axis) represents the time scale and the beginning and ending dates of the project, as well as that of the individual tasks. The length of each activity bar is related to the duration of that particular activity, or the time that is necessary for completion. Different colors or percentage numbers in the bars can represent the status or level of completion of an activity. Arrows connecting the bars are used to indicate a dependency between tasks.

The Gantt chart is a common project management technique used to represent the schedule, phases and activities of a project in a single visual. Gantt charts visually represent project sequence, duration, dependency and status in a manner that is easy to understand.

The Gantt Chart represents the order in which activities need to be carried out and provides an overview of what should have been achieved at any point in time. Furthermore, Gantt charts can be used to show current schedule status by adding percent-complete shadings and a vertical "Today" line. Another clear strength of the Gantt project management technique is the ability to display the status of each activity at a glance.

Overall, a Gantt Chart is a useful technique that can also be used for planning and communication purposes.

However, Gantt Charts for a larger project consisting of many tasks can become crowded and lose the positive aspect of simplicity. In large Gantt Charts, choosing the right level of granularity is crucial to ensure that the visual remains useful and easy to communicate.

Note, however, that projects are often much more complex than what can be represented even in a detailed Gantt Chart. In such cases, a Gantt Chart cannot be used on its own as it cannot include all the critical information and project dynamics required for managing a project, particularly for larger or more complex projects.

The following steps are typically used to create a Gantt Chart:

Step 1

Define the project's Work Breakdown Structure (WBS).

Step 2

Identify the duration of each task.

Step 3

Identify the dependencies between tasks and activities in the WBS.

Step 4

Define the sequence of tasks in the project.

Step 5

Map the summary and terminal elements of the WBS on the Y-axis of a graph, and the duration on the x-axis of the graph.

Step 6

Create horizontal bars to depict the length of each WBS element, and connect the dependencies identified in Step 3.

Resource Levelling

#Planning #TimeManagement, #ProjectManagement #AgileProjectManagement

Resource Levelling is a technique used to analyse the unbalanced use of project resources and to resolve conflicts related to resource allocation. The resources could consist of FTE (full-time equivalent) as human resources, material or equipment to be used during an activity of a project.

During the project planning, the project manager might schedule several activities in parallel to reduce the duration of the project. This may result in an uneven allocation of resources, with resource needs per activity, which might require more resources than available. In complex scenarios, resources could also be allocated to multiple projects, which could result in a shortage of FTE, material or equipment. In such scenarios, resource levelling is used to optimise allocation and resolve related conflicts.

Figures below show the resource requirement for a project with breakdown of activities A-F over time. The total required resources--over a period of 6 days--is 28 units. Thus, ideally, Project 1 would have 5 resources per day (28 divided by 6 is 4.67, which we will round to 5) to complete the project.

However, activities are interdependent in most cases. In addition, FTE resources often require various skillsets to complete an activity, which makes the “ideal” situation a poor representation of reality. Consequently, resource levelling could delay the project end date if it impacts the critical path activity. This can be seen in the second figure below, where resource levelling added two additional days to complete all activities with the available FTE resources.

A graph of different colored bars AI-generated content may be incorrect.

Figure 23: Resource Histogram (1)

A graph of different colored bars AI-generated content may be incorrect.

Figure 24: Resource Histogram (2)

Resource levelling focuses on an efficient and optimal resource allocation, so that the project can be completed in the defined timeline.

To be able to optimise resource allocation, project managers (analyse dependencies between projects or activities to ensure that activities can be executed within the foreseen timespan. During this process, the project manager could face some constraints related to the sort of activities of a project, which can be mandatory, discretionary or external.

Mandatory:

Constraints could arise due to the obligatory nature of the work being done, which often involves a physical limitation. For example, a test case needs to be defined before testing.

Discretionary:

Constraints could arise due to the preferences or decisions of the project manager or team. For example, a decision is taken to document a process before executing it.

External:

Constraints could arise due to the needs of a third party involved. For example, equipment has to be purchased from a third party before the configuration of the equipment can begin.

Once the identified constraints are taken into account, resource levelling can be performed. It may require the delay of tasks until the necessary resources are made available. Within a larger organisation, resources could also be allocated across multiple, simultaneous projects. Therefore, the project completion date could be delayed if the tasks affected by resource levelling are within the critical path.

The Critical Path Method is commonly used as a basis for levelling. Project managers) could choose from the following alternatives in order to resolve resource constraints:

Earned Value Management

#CostManagement #ProjectManagement #ProgrammeManagement

Earned Value Management (EVM) is a technique used to monitor and control the performance of projects and programmes. Taking example of a project, it provides an objective view of performance based on the project budget. Therefore, in EVM the concept of cost and time are both measured in terms of cost units (e.g. Man-Days or Euros).

EVM allows project managers to manage project scope, cost and time, as well as impact of any associated risks. The metrics provides relatively objective indicators regarding past and current project performance, in addition to forecasts of future project performance.

EVMs are often used for Key Performance Indicators in project status reporting. They also enable project managers to foresee deviations from the project baseline plan in terms of cost and schedule, and to make decisions early in order to put the project back on track.

A graph of different colored lines Description automatically generated

Figure 25: Earned Value Graph

Traditionally, project management metrics concentrate on a total budget (PV) and actual cost (AC). Considering the figure above, using these metrics, it would appear that the project in question is performing well under-budget. However, with EVM, = it is shown that the project has been efficient in terms of cost (EV>AC), but are lagging on the project schedule (EV<PV).

Based on the results of such an EVM, a project manager can propose a pro-active measure to management to allocate additional resources to the project in order to deliver on time and still be on budget.

As mentioned, EVM provides project managers with a set of relatively objective metrics, or Key Performance Indicators, that allows them to “proactively” manage project performance.

The metrics used in EVM are proposed in the table below:

Table 7: An Example of EVM Metrics

EVM Metric Description of the Metric Source/Calculation
BAC Budgeted at Completion – Total baseline budget Input
EV Earned Value – The perceived value earned at a point in time in the project % completed * BAC
PV Planned Value – The incremental or per period value that is planned in the Project Planning Phase Input
AC Actual Cost – The incremental or per period cost incurred at a given point in time in the project Input
CV Cost Variance – The difference between what has been achieved and how much it has cost at a given point in time in the project EV – AC
SV Schedule Variance – The difference between what has been achieved and what should have been achieved at a given point in time in the project EV – PV
CPI Cost Performance Indicator – A measure of efficiency of cost – the amount of EV units earned per 1 AC unit spent EV/AC
SPI Schedule Performance Indicator – A measure of efficiency of schedule – the amount of EV units earned per 1 PV unit spent EV/PV
EAC Estimate at Completion – A revised estimate of the total cost based on the current efficiency (CPI) AC + ((BAC – EV)/CPI)
ETC Estimate to Completion – The amount of cost yet to be incurred based on the revised budget (EAC) EAC - AC
TCPI – BAC Total-Cost Performance Index (based on the BAC) – Provides an estimate of the CPI necessary to complete the project in the BAC (BAC – EV)/(BAC – AC)
TCPI – EAC Total-Cost Performance Index (based on the EAC) – Provides an estimate of the CPI necessary to complete the project in the EAC (BAC – EV)/(EAC – AC)

Despite its benefits, it is important to understand the drawbacks of Earned Value Management (EVM).

EVM uses cost units as its only measurement, hence even schedule oriented metrics such as SPI and SV are not expressed in time units. Therefore, the SV and SPI will not tell a project manager the delay in calendar days that a project may suffer. Moreover, EVM does not consider qualitative elements like project quality and team dynamics as measurable metrics.

Even though EVM metrics are largely objective, they are still subject to not only interpretation, but also estimation error or bias on behalf of the project manager. Namely, EV is derived based on the percentage of a work package completed, and it is an estimate provided by the project manager and by the project team. In addition, the accuracy of PV is a subject to the experience and information available to the project manager during the planning phase of the project. PV and EV are then most accurate when the Work Breakdown Structure (WBS) is very detailed and work packages are small in cost and duration.

EVM is also demanding in terms of project set-up because it requires a good reliable project plan, and in terms of project monitoring and controlling because it requires measuring, gathering and tracking all necessary indicators.

Overall, EVM is a useful tool to manage project budget and performance. However, it only considers quantitative aspects and ignores qualitative KPIs reflective of domains, such as quality.

Ishikawa/Fishbone Diagram

#RiskManagement #ProjectManagement #ProgrammeManagement

“Ishikawa,” or Fishbone diagrams, are cause-and-effect diagrams that identify potential factors that may cause problems. They are commonly used in process design and quality defect prevention to identify the root causes related to the problems.

Project or programme teams may want to identify a risk, understand what the root causes of it are, and how to tackle these within the project. In order to find root causes of a problem, the cause analysis can be organised, as follows:

These categories and their applicability can differ, for example, project-to-project. Identical analyses of root causes may be repeated within an individual cause category to uncover its primary and secondary cause. This analysis of decomposing and detailing causes and effects is called the Fishbone diagram, as shows in the figure below, as its visual representation is akin to the skeleton of a fish.

After decomposing a problem and identifying its root causes with the Fishbone diagram, the project team can adjust the solution to best minimise the impact of each major issue on the project.

A diagram of a process Description automatically generated

Figure 26: Ishikawa Diagram

The Ishikawa or Fishbone diagram is used to find the root cause of a problem in a project. Project managers may involve a small team to brainstorm on the problem statement to take into account and minimise the impact of each major cause on the project.

The following steps to finding and resolving the root causes of project issues can be taken to elaborate on the Fishbone diagram:

Step 1

Step 2

Step 3

Step 4

While analysing a problem using a Fishbone diagram, the scope should be manageable. The factors should not be too broad, as it makes the analysis of the diagram difficult. The team should also not spend too much time debating on where to place a primary or secondary cause. However, it is important to build the right diagram for a thoughtful discussion. It is also important to find solutions for each of the identified cause and effects of the problem statement.

Delphi Techniques

#RiskManagement #ProjectManagement #ProgrammeManagement

Delphi Technique helps to understand and estimate the positive or negative impact of future events on a project or programme that allows, for example, a project manager to address unforeseen circumstances.

The Delphi technique uses a panel of experts, moderated by a facilitator, to discuss circumstances of the project or a programme for two or more rounds in order to come to a consensus. The opinions in each round are shared anonymously through questionnaires or surveys. In each round, the experts are aware of all the inputs and opinions on the project. Though, the experts do not know the source. This anonymity ensures that influence of some inputs and/or opinions are avoided and enables the panel to discuss openly and revise any errors in previous opinions. The results of each round are fed as inputs into the next round until a consensus is reached. Finally, the facilitator reviews the feedback and builds a consensus of the panel’s views and issues a summary report.

One might consider the Delphi technique as an iterative process to identify areas of agreement and disagreement regarding assumptions of a project. Once there is a consensus in the panel, the facilitator issues a report regarding the analysed potential events or circumstances and how those may impact the project.

Please find an illustration of the Delphi technique in the figure below.

A diagram of a group Description automatically generated

Figure 27: Delphi Technique Process

The steps below could be followed when using the Delphi technique:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Although the Delphi technique cannot predict the exact future events with certainty, it can help the project or programme teams to understand and take into account the impact of potential future events. This helps the team more effectively and efficiently complete the project.

Plan-Do-Check-Act Method

#Planning #QualityManagement #ProjectManagement #AgileProjectManagement

PDCA (Plan, Do, Check, Act) is an iterative method that is usually used for project management process improvement. The method was developed by Deming, who is known for introducing successful process and quality control techniques to the Japanese manufacturing industry.

The fundamental principle of the PDCA method is iteration. Once a problem is identified in a process, a potential solution is tested. The result of the solution is checked and analysed to see whether the solution can be improved further. The solution is then applied to the problem again. Through the iterative nature of this method, the desired control on business processes can be achieved.

The PDCA cycle can be used by the project managers in the following scenarios:

A diagram of a plan Description automatically generated

Figure 28: PDCA Framework

The PDCA cycle enables a project manager to be methodical in the approach of process improvement or control. The following are the key steps in the PDCA cycle:

Plan:

Identify problems related to the achievement of a project objective or execution. This can be found using a number of methods, such as the 5 Whys, Root Cause Analysis, and Fishbone Diagrams. The problem statement outlines the expected output from the solution.

Do:

Several possible solutions are identified. The best alternative is chosen and applied within the project. This small-scale pilot could involve few resources, limited geographic area, new business processes, etc.

Check:

The effectiveness of the solution is measured, applied, and the outcome is analysed. The areas of improvement are identified in the solution, and the process is refined. The “Do-Check” steps are repeated until a feasible solution is reached that is in line with the expected output (defined in the Plan phase).

Act:

The solution, with corrective actions identified, is now implemented to the whole problem. The process may not end at this step. In case of continuous improvement of the process, the complete PDCA cycle is repeated to further improving the project management processes.

The project manager will define process improvement objectives and run through the PDCA cycles until each of the improvement objectives are achieved. This iterative exercise is a structured way to find and evaluate solutions to prevent the implementation of solutions without proper analysis, foresight and control.

Though the PDCA cycle is a well-structured and methodological process, it has limitations. It cannot be applied in emergency situations where a quick fix needs to be applied. In addition, the PDCA cycle is time consuming and thus needs to be applied in projects where there is time available to brainstorm and implement the pilot runs. Lastly, the cycle is not effective in adaptive scenarios where finding a solution is difficult due to high complexity or uncertainty of the system.

Pareto Chart

#RiskManagement #IssueManagement #ProjectManagement #ProgrammeManagement

The Pareto principle states that generally 80% of the effects come from 20% of the causes. The same principle applies in project and programme management. For example, 80% of costs may be attributed to 20% of activities, or 80% of the effects of risks may be attributed to just 20% of the identified risks. This analysis is called a Pareto Analysis, and it is illustrated by a Pareto Chart in the figure below.

The Pareto analysis is a formal technique to identify issues that cause most problems in a project. Focusing on these primary issues will lead to addressing nearly 80% of the problems. Then, the root cause analysis can be performed to address them.

The application of a Pareto Analysis helps to focus on those few risks that cause the most impact on a project or programme.

A graph with different colored lines Description automatically generated

Figure 29: Pareto Chart

A Pareto Chart can be prepared once the problems and associated inputs are identified. The horizontal axis (X-Axis) gives the list of all inputs that are potential causes of the issues at hand. The left vertical axis (left Y-Axis) tells us how frequently an input has caused the problem. Lastly, the right vertical axis (right Y-Axis) depicts the cumulative percentage of how much the project has been affected by all the problem inputs listed on the X-Axis.

Applying the Pareto principle, one can see in the chart above that the 80-20 rule has worked: inputs A and B account for around 80% of the issues in the project that need to be addressed as a priority

The Pareto Analysis provides insights about the top issues impacting the project and prioritises the actions to be taken. The following steps can be used to perform the Pareto Analysis:

The European Commission PM² Methodology V.2 Guide

Step 1:

Define the problem statement and decide on how to classify the causes.

Step 2:

Create a list of cause categories covering all identified causes in Step 1.

Step 3:

Determine the frequency of occurrence for each cause category identified in Step 2.

Step 4:

Arrange the cause categories on a histogram with the highest to the lowest frequency of occurrence. Add a cumulative contribution in percentage terms on the right vertical axis to complete the Pareto Chart.

Step 5:

Identify the top problem categories contributing to 80% of the causes from the Pareto chart. Use root cause analysis methods to drill down on these top causes to find solutions.

Sometimes, the top problem category identified may be too broad to address. In this case, a second-level Pareto analysis needs to be conducted on the larger problem category. This enables to break down the analysis to apply the proper solution to the right problem category.

One of the limitations of the Pareto analysis is that it can overlook smaller project issues, which will grow into larger problems the longer they go unaddressed. These small issues may be the root cause of a large problem in the future, so addressing them may be postponed, but cannot be avoided. The Pareto Analysis can be performed at different phases of the project to uncover these smaller issues, as they may not be found or exist when the analysis is initially performed.

Lessons Learned

#ClosingPhase #ProjectManagement #ProgrammeManagement

Capturing the lessons learned of a project or programme is often overlooked. Project and programme managers should encourage team members to capture lessons from projects and programmes, as identifying these can lead to discovering areas for improvement, which can be useful when executing similar projects or programmes and even lead to the organisational process improvements. Information that can be captured include lessons learned through addressing risks, quality issues, outsourcing or contractor issues, change requests, etc.

For example, the project team with invited project stakeholders can captures ideas through brainstorming sessions, project reports and logs, project questionnaires, etc., during the lifecycle of the project. The Project manager can also organise meetings to stimulate the process of capturing lessons and identifying opportunities for improvement ideas. Project managers should conduct these meetings efficiently to capture constructive inputs from the whole team and project stakeholders.

The project team and project stakeholders should be open to discuss the shortcomings of the project and how they were overcome. The identified areas for improvement can be grouped afterwards and prioritised to understand and act upon the top improvement areas. In addition, action items for follow-up can be assigned to team members to improve upon shortcomings. The captured lessons, as well as any derived action items, can be reviewed in follow up meetings.

Table 9: Project Lessons Template

Project Details Project Name, Project Manager, Team Members
Area/Process Issue that occurred Actions taken What worked well What can be improved Other comments Shared learning Recommended follow-up actions
Area 1
Area 2
Process 1
Process 2

In order to capture lessons learned, the project managers, alongside with the project team, could use and customise a template as illustrated by the example in the table above.

Capturing lessons learned within a project is an effective way of identifying development areas within that project and areas for improvements. Below are key steps to follow when identifying lessons learned:

Step 1: Kick Off

Step 2: Capture Ideas

Step 3: Group into Opportunities

Step 4: Prioritise

Step 5: Identify and Assign Actions

Lessons learned can also be captured on a regular basis and archived. This archive could serve as a starting documentation for project and programme teams to execute similar projects and programmes.

Setting Up Self-Organising Teams

#TeamManagement #ProjectManagement #AgileProjectManagement

Self-organising teams have the ability and authority to take decisions and readily adapt to changing demands. From a social systems perspective, it means that the team can create new approaches and adjust to meet new challenges in their environment. Self-organising is a process and not something that is done once and completed.

Promoting self-organising teams within an organisation is a strategic decision, starting with a shift in management mindset while creating effective self-organising teams is not necessarily an easy task. Managers must create the conditions that enable teams to thrive and continue to self-organise. It takes a combined commitment and effort from many different levels of the organisation (Senior Management, Project Management, and Development/Team Management) to help teams emerge as self-organising and high performing teams, while management commits to guiding the evolution of behaviours that emerge from the interaction of independent agents instead of specifying in advance what effective behaviour is.

Self-organisation does not mean letting people do whatever they want to do neither that they are free from influence. Managers need to work with the team to set appropriate boundaries and constraints. Self-organising teams have (bounded) authority to make their own commitments, organise and assign their own work. They craft appropriate strategies to accomplish their goals and make decisions with (bounded) economic and organisational impact. So they should not be disconnected from the broader organisation. They are accountable to make their progress visible, and work within the agreed boundaries.

Self-organising teams:

Characteristics of self-organising teams:

A diagram of a group of people Description automatically generated

Figure 30: Creating and Sustaining a Self-Organising Team

Misconceptions about Self-Organising Teams:

For starting and sustaining a self-organising team, one can follow the steps below.

Step 1: Train

You need to groom people to get the desired skill set. At the end of this phase, you can assume the team has the capabilities to exhibit self-organising behaviours. Provide any needed classroom and on-the-job training to make each person competent in a particular domain/technology. Behavioural training is also helpful.

Step 2: Coach

Once the team starts working together, adopt a coaching style to see if the members are facing any difficulties. They may require more support and guidance at the beginning. Some indicators of a self-organising team show the meetings are productive, the team enjoys the work, and members help each other, new ideas are forthcoming, and teams are pulling work for themselves. By the end of this step, you know the team is self-organising. However, keep your eyes open to observe the team's behaviour and provide need-based coaching. This is the step that will result in innovative ideas and improved results from the team.

Step 3: Mentor

Once the team is in self-organising mode, the key is to sustain this for the longer run. Assign mentors who can help the team go to the next level. Job rotations can be an important aspect of keeping people involved and of encouraging continuous learning. As mentioned earlier, a self-organising team doesn't need "command and control," but it does need coaching and mentoring.

The Team Manager/ Team Leader/ The Agile Team Lead, i.e. the role responsible to coordinate the team, should act as a coach and ensure that the team gets job-specific training and coaching. This role is primarily responsible for ensuring a cohesive and soothing working environment, which is a must for the blossoming of a self-organising team. Coaching individual team members is important so that they understand the principles of self-organising teams and trust each other. This role should also look at a variety of ways to improve collaboration within the team geographically distributed.

Senior management should ensure that they don't get in the way of the team's work; they need to act as supporters rather than distractors.

Team goals should be set, and individual heroism should be discouraged - it only acts as a block to self-organising teams. It's essential to allow team members to fail before they're expected to deliver.

The organisation as a whole should ensure that it provides the necessary infrastructure, training, and incentive system to keep people motivated at work. These are hygiene factors that constitute the first barrier to cross before you can expect your team members to be self-organised.

Defining User Stories, Epics and Themes

#RequirementsManagement #Planning #AgileProjectManagement

User stories are a way to express the requirements that a given solution should address. Each user story captures a concise, written description of a piece of intended functionality that has value to a user role of the developed solution. A user role represents a population of users that share similar attributes and interaction with the product. Each different user role has different characteristics or attributes that help identify different ways that each interacts with product. The use of roles while writing user stories helps us avoid writing the stories from a single user's perspective. It is typical that we start by identifying individual users of the product, then we need to organise, consolidate, and refine them into more generic user roles.

A typical notation for documenting a User Story is: "As a <User Role> I want to <goal> so I can <reason>".

User stories also capture the stakeholders' conditions of satisfaction about that piece of functionality, the acceptance criteria. User stories are meant to be simple, clear, brief descriptions written using business language in the context in which the need or capability will be used in the product. A user story is in fact a reminder for further conversation between the team and stakeholders. User stories are written down, but they are not meant to be contractual, or even interpreted without further discussions with the stakeholders. The ongoing interaction between stakeholders and the team (to discuss the details of a user story) are more important than the resulting textual description itself.

Conversation

Another important concept is not to worry about getting all the details into the story. It really needs to be a commitment to have a conversation (actually, a lot of them). Stakeholders can make up their minds as the story is in development. Likewise, as developers need more information or need to ask questions, they should ask (and not expect everything to be spelled out up front for estimating purposes). What's important is to foster a healthy communication betweende stakeholders (or their proxies) and product owners with the development team.

Confirmation

It's usual that agile teams do a lot more testing along the lines of development of the product, compared to traditional teams. For example, in IT projects, they often write a test before they write sufficient production code to fulfill that test, and then they proceed develop the next iteration. These teams work very closely together and, ideally, work closely with their stakeholders. Changing requirements are seen as a competitive advantage, not as something that you need to prevent, as long as one can act on them. Agile teams deliver working product at every iteration, thereby providing concrete evidence of actual progress on the project. Daily builds, or even builds multiple times a day, are highly desirable. Shorter iterations are desirable, from as short as one to two weeks.

The following list provides some examples of user stories:

There are several user story representation alternatives. One typical way of recording a user story is an index card. The front of the card is used to capture the user story sentence, which typically follows the notation shown in the figure below.

The back of the card is used to capture relevant details that come up during conversations with stakeholders, such as information or data needed, non-functional requirements (such as performance or scalability) and other conditions of satisfaction for the user story. The back of the card can be organised as the figure below shows.

Figure 31: An Example of Front and Back Sides of a User Story Card

Certain requirements for the product under construction are not about a specific functionality that can be assigned to a team member and implemented in one time box. These requirements typically impose constraints on the product in terms of, for example, how fast, reliable, scalable, useful, portable, or easy to maintain a product should be. Such requirements generally span across multiple user stories of the product and are referred to as non-functional requirements, product-wide requirements, technical requirements, or constraints. There are different approaches to capturing non-functional requirements as part of user story-driven development, as described in the three sections that follow.

Approach 1. Write individual stories

One way to capture non-functional requirements or constraints on the system is to write them as individual stories, which are often referred to as technical stories. For example, consider this technical story:

This technical story captures what a legitimate user role wants from the system: the bank CTO wants the system to comply with a banking standard related to system performance. Even though it is legitimate, this technical story arguably violates the goal of stories being valuable and, at the same time, sized to be finished in one iteration. This technical story affects or constrains many user stories in the system. Considering that many iterations will pass until all user stories are developed, it is clear that this technical story can't be assigned to one team member and finished in one iteration if it is to show value to all stakeholders - not only to the bank CTO, but also ATM users.

Approach 2. Include the details in each user story

Another approach is to capture non-functional requirements as part of the details of each user story. This way, each user story clearly contains the acceptance criteria that define the level of completeness. Let's take the following user story as an example:

In the details part of that user story, one could capture the non-functional requirement this way:

In this version, when the user story is implemented, tests need to be created. This includes having the appropriate test environment to simulate the operational environment so that both the functionality (the ability to withdraw cash from a bank account) and the performance (how fast the back-end operations run) can be tested.

Approach 3. Combine both methods

While conversing with stakeholders to flesh out the details of a user story or prioritising the user stories and developing them, the team might inadvertently miss that a given user story, for example, is constrained by the adherence to XPTO Standard. A combined approach to capturing the non-functional requirements seems the best option: capture the non-functional requirements as technical stories (or another notation or free-format text, if that makes sense), and always make that list of technical stories visible to the team and stakeholders when prioritisation and detailing of user stories is happening.

In this way, the team and stakeholders make sure to capture the non-functional requirement as an acceptance criteria within the details of each and every user story where that constraint applies.

Another advantage of keeping all of the technical stories on a consolidated list is that if there is a requirement change or a new requirement is added, it becomes visible to the stakeholders and team right away. For example, you might get this change to the performance requirement:

That one-second change and the stricter standard should alert the team to revisit all affected user stories. Based on the previous discussion, a non-functional requirement that is captured as an individual technical story may be hard to treat (prioritise, assign to a team member, and implement in one iteration). These technical stories are not prioritised with the user stories, but they typically serve as a reminder that, for example, the system is constrained or needs to adhere to some standard. On the other hand, stakeholders will most likely prefer to give high priority to user stories that have high business value, which is acceptable from the stakeholders' perspective. However, the team needs to make sure that the user stories that are affected by constraints take precedence over other non-constrained user stories. The team and stakeholders need to find this balance when prioritising user stories. This is the same as thinking which user stories impact the architecture of the product being developed. Those user stories should be scheduled for implementation early in the project to help the team build and validate the product architecture early, which helps minimise project risks early.

Epics

As each user story expresses a requirement from the user perspective, different user stories with different granularities may be defined throughout the development of the product. Depending on the project and the project environment (e.g. degree of experience with agile approaches), it may be useful to consider the concept of 'Epic'. Epics are single, large story that usually represent complex requirements not ready to be partitioned at the moment that they are identified, either because they are of low priority and will be partitioned later in the development, or because there hasn't been a conversation between stakeholders and the development team to better understand those stories. It is common that, early in the development aspect, there are many epics, encompassing high-level product features requested by stakeholders. As the conversation evolves, many smaller stories originate from those epics. The following is an example of an epic:

This is epic in scope, because the development required seems to be as big as a complete ATM system. This might represent the first request that the stakeholder ever made to the team.

It is too complex to be estimated and too big to be finished in an iteration or cycle. It corresponds to the work of a whole team through various iterations or cycles to complete an entire product release.

In short, this large story does not possess some of the characteristics of the INVEST model (Independent, Negotiable, Valuable, Estimable, Small, Testable).

The epic in this example could be broken down into stories such as these examples:

However, those two stories still seem to be epics, because they are still complex to estimate and too big to finish in a short time frame. Ideally, they should be further broken down into more granular user stories. Let's take, for example, the epic related to paying bills, and break it down:

Notice that by defining a more specific user role (ATM user rather than bank customer) and providing different usage scenarios (different bill types, specific vendors, or providers), it is possible to write more granular user stories that are in better shape to be discussed with stakeholders, prioritised, estimated, and developed in a short time frame.

Themes

As previously mentioned, throughout the development, user stories are allowed to be big, then broken down and detailed for estimation and development.

Also, user stories can be grouped together for prioritisation in the longer time frame. To facilitate the high-level prioritisation, it may be useful to consider the concept of 'Theme'.

Themes are collections of user stories that are grouped together for prioritization and planning purposes. The process of breaking down larger stories into smaller ones helps the team and stakeholders better discuss their details, prioritise them, and have the team estimate and develop those stories in a short time box, such as an iteration. However, for the purposes of prioritising stories along a longer time span, such as a release time frame (many weeks to a few months), the prioritisation of many fine-grained stories is a difficult process. Therefore, it may make the stories easier for stakeholders to follow if you group shorter ones into collections, perhaps according to those that will have more business value if they are developed simultaneously. It may also help the development team to define what stories go well together, such as stories that have common infrastructure needs or address a common set of features. These collections of user stories are referred to as themes.

A simple analogy is to think of a pack of index cards that represent stories, all bundled together by a rubber band. This provides the flexibility needed for stakeholders and the team to decide to add or remove stories from the pack as appropriate for prioritisation and development purposes. A given theme can also be split in more sub-themes as needed, with the option of sub-themes being of higher priority than others. In the previous ATM application example, these are examples of major themes to use to group stories together:

For the purposes of prioritisation along a release time frame, that grouping should be enough. However, for the purposes of more refined prioritisation, stakeholders and teams may decide to break a theme down into smaller sub-themes. For example, the Bill Payment theme can be broken down into the following sub-themes:

A diagram of a story Description automatically generated

Figure 32: Epic, Theme, and User Story

User Stories Breakdown Techniques

#RequirementsManagement #Estimation #Planning #AgileProjectManagement

User stories may be of different sizes during a project lifecycle, including very large ones that are often called epics. When a user story is close to being implemented, it needs to be right-sized to facilitate being prioritised, estimated, and developed within a reasonable time frame (typically within a time box, such as an iteration). Even if a user story fits within the defined time box, it might still need to be split because it does not fit within the available time to finish.

A diagram of a user Description automatically generated

Figure 33: User Stories Breakdown

There are different approaches to breaking down stories for planning, estimating, and development purposes.

Breaking down user stories across data boundaries

One approach is to break down user stories across data boundaries. Look for the data that needs to be supported by the user story. If the data is complex or a large set of inputs will be required from the user or to present to the user as output, split the stories according to subsets of that data. If there are different types of values, then split stories according to those value types. For example, in the ATM system, an ATM user should be able to make payments for predefined payees that have business relationships with the user's bank. ATM users should also be able to make payments to payees that they add when they authorise payments. In this example, the user story that starts:

Breaking down user stories on operational boundaries

Look for different operations in a user story as a way to split it. From the example on the previous section, adding a new payee and making the payment are two separate user stories. This is a possible way to split this user story:

Another common way to partition user stories along operational boundaries is to look for the typical operations of creating, reading, updating, and deleting data (CRUD).

Breaking down user stories on product-wide or non-functional concerns

There are some requirements that can be considered product-wide requirements, meaning that they apply to many user stories. Examples are security, language support, and logging. There are also non-functional requirements that apply to one or more user stories, such as performance or availability. If a user story is too big to fit into an iteration, split the story into two stories: one that does not include the non-functional concern and the other that does. This helps you implement the story in its simplest case (even though you might not want to release the user story without elements of security or performance until they are implemented on a second round).

Breaking down user stories of mixed priority

Some user stories can be broken down based on priority, according to when the parts need to be implemented. In this way, you can start implementing the most important parts first, then add the lower-priority functionality later. In the ATM example where an ATM user wants to withdraw cash from the bank account, the team might decide to break this story down and develop the common path first, which is to have the ATM dispense 20€ bills. Another story to be developed later might be to provide the option for users to select cash in 5€, 10€, or 20€ bills.

What is not a recommended breakdown

It is not uncommon that a large user story is difficult to split, even after considering those approaches. However, one thing to avoid is breaking down a user story based on horizontal slices of the product layers. A user story, as small as it could be, still needs to be of value to a user role. Therefore, avoid developing a story that has only user interface elements and no logic or data access. Also, avoid fully implementing the data access without having user interface elements and logic to access that data. When developing a user story, make sure that you are slicing the various layers of the product vertically, which means that you develop a little bit of each layer to support that user story (for example, user interface, business logic, and data access)

Definition of Done

#Estimation #Planning #QualityManagement #AgileProjectManagement

In an iterative and incremental product development environment, it is important that the development team agrees on what conditions must be satisfied for a given user story to be considered "done", the user story "definition of done" (DoD). A DoD can be a list containing different items that the development team members check to determine if an implemented user story complies with the team's quality standards. The Scrum Guide describes a Definition of Done as a shared understanding of what it means for work to be complete‘. Some examples of items that can be included in a DoD checklist in IT Project are:

A diagram of a project Description automatically generated

Figure 34: Definition of Done example

The DoD should be the result of a discussion and an agreement at the development team level of what "done" means in the context of that project. In some cases, a common "definition of done" may be available and can be applied by different development teams, moving towards cross-project understanding of what "done" means for the organisation. User stories (or any increment to the product under development) that are considered "done" are ready to be made available via a release. Some of the main benefits of having a "definition of done" are:

It is important to differentiate the "definition of done" and the acceptance criteria for user stories. The "definition of done" should be the same for all user stories as it is concerned with the notion of a quality output (fit-for-use). The acceptance criteria of a given user story implementation is specific to each user story as it is focused on the user's perspective of what the product is expected to do by having implemented that user story (fit-for-purpose).

Even if the DoD in a first maturity step is mostly applied to user stories development, the same concept can and should be applied to the iterations and releases of an agile approach. The purpose remains the same: common agreement of what does it mean a given increment of product to be done. What changes is the type of items to be checked to determine if a given iteration or a given release is "done" (e.g. deployment instructions for operations - corporate data centre, for example, written, automated integration tests run).

Step 1: Agree which DoDs are (or can be) applicable to your project

Depending on the experience and maturity of the development team and the project's organisational and technical environment, decide the scope of DoD that is needed and realistically achievable in your project. Start by defining a DoD for user stories, and from there define a DoD for iterations and releases.

Step 2: For each DoD, agree which items should be part of the checklist

Discuss within the development team what is the desired and achievable quality to built-in the product developed and in the development process itself. In your organisation, check for corporate policies, guidelines and constraints that may impact your project. Areas such IT Governance, Data Protection, Security, Hosting should be considered when defining the DoD. The references in terms of IT Policies and Guidelines could be:

Step 3: Ensure that the defined DoD is respected

Creating a DoD should not be seen as something external imposed to the development team. It should be agreed between the team and all the team members should commit to respect the DoD when developing parts of the software. The DoD is meant to help the team to produce a fit-for-use solution in each increment and contributes to better estimation and planning of what can realistically be achieved by the team, setting the correct expectations to the product owner and other project stakeholders.

Step 4: Inspect and adapt the DoD

The DoD should not be static. As the development team get experienced with the use and value of having a DoD, it is expected that the DoD is fine-tuned to the organisational and technical environment within which the team operates. The retrospectives, at iteration and release level, are good opportunities for the team to openly discuss the DoD identifying and implementing some improvements to the defined DoD.

INVEST model

#RequirementsManagement #Estimation #AgileProjectManagement

Even though user stories are an informal technique for capturing requirements in a lighter way, to promote interaction between teams and stakeholders, it helps to know what makes a "good" user story. The INVEST model defines them as Independent, Negotiable, Valuable, Estimable, Small, Testable. This model was introduced by Bill Wake and has been used by many other authors in the Agile development-related literature.

The next sections explain characteristics of good user stories, based on the INVEST model.

Independent

Identify and capture user stories that are as independent as possible. Independent, in this context, means that one is able to assign that user story to be completed in a defined period of time with as little dependency on other stories as it is feasible to have. You may realise that completely removing dependencies is not only impractical for some types of products, but also undesirable. In some cases, dependencies may make sense. For example, the "Forgot user ID and password" user story depends on the existence of the "Log in to the system" user story. In this case, it makes sense to group stories into themes, which are a better way to plan for and develop together those user stories that have some level of expected dependency. Another aspect of user stories being independent is to make sure that there is no functionality captured by more than one user story, which helps avoid that redundant work is done by two or more team members.

Negotiable

Identified user stories each contain a short description of a user performing something in the system-to-be to achieve a goal. This description is initially at a low level of precision, and by no means should be seen as a contract. It is a reminder that we need to communicate continually with stakeholders to understand the stories better and refine their details, based on the dialog. The trick is to capture just the right amount of detail, which may be constrained by subjective interpretation. A good sign that a user story has too much detail, too early, is when the team assumes that they already know all they need to know to develop the story without further communication with stakeholders. As stakeholders add details to stories, team members can capture high-level design decisions to include in the stories, as well as elements that are candidate for user interfaces. But stories need to remain works-in-progress and negotiable. This means that when a team member is developing a user story, if the team member decides there is a better way to implement it (despite of the details captured in the user story) and still achieve the stakeholders goals, that should be an option, and the stakeholders should be open to negotiate that alternative.

Valuable

This might mean that user stories need to be valuable to stakeholders. But that raises the question of "Which stakeholders? Users or owners of the product?" That depends. Some stories are written with the end user in mind, and some may be written with other types of roles in mind. Therefore, a better statement would be ‘user stories need to be valuable to user roles’, whomever those roles represent. The easiest way to adhere to this is to write the user story from a business perspective, rather than a technology perspective, and to use natural language.

One caveat about capturing non-functional requirements (such as performance or availability) as user stories: these typically affect many functional user stories and should be worded in a way that expresses that dependency. From a development standpoint, the resulting implementation also needs to show value to stakeholders. It is expected that developers will implement a complete pass through all layers of the product. For example, if a developer implements all of the database access interfaces at once, this implementation may show nothing of value to an end user.

On the other hand, there is much more value from a user standpoint if a developer implements a user story that "cuts a vertical slice" across the various layers of the product, meaning that the developer is really implementing user interface, business logic, and database access to support that user story.

Estimable

Valuable, agreed upon, and right-sized stories should be estimable - something that you can use as a basis for an estimate. Failure in estimating user stories relative size often leads to failure to deliver the solution with the value that stakeholders expect. There are different reasons that it might be difficult to estimate user stories size. For example, the user stories might be too broad; they might need to be broken down into smaller stories or development tasks that are more granular and easier to prioritise and estimate. Another example can be that the team may lack information or knowledge about the domain or technology to be used, thus they can't provide an estimate for user stories size until they have access to a domain expert or can investigate the new technology to be used.

Small

As mentioned previously, "small" stories are easier to estimate. They should also be able to be developed within a reasonably short time frame (typically with one person working for a few days to a couple of weeks), to provide value to stakeholders as soon as feasible. The question is, how big is small? There is no right or wrong answer here, but, generally, there are indicators of a user story being too big. If the team has difficulty in estimating size and effort of a user story, that might mean that the story needs to be broken down into smaller stories or development tasks for a more accurate estimate to be provided. If it would take more than a month for one person to develop the user story, that is another indicator the story needs to be broken down. Not all stories are broken down early in a project, even if it seems that they need to be. Many larger stories (also called epics), remain on the work items list as they are until it is time to develop them. At that time, the team discusses the need to break them down for the purposes of planning, estimating, and development.

Testable

Good user stories should be able to be tested and validated, and this needs to be true even before development begins. Understanding how to test a user story means that the user story is understood, the value stakeholders want out of it is clear, and we know when development is successfully finished. Discuss with stakeholders - and capture in each user story - the conditions that will make the user story considered fully developed. In general, larger user stories, such as epics, are harder to test because of their size or complexity. Stories that represent non-functional requirements also may be hard to test, because they need to be a clear, quantitative definition of test conditions. For example, define a test scenario that says ‘the administrative report needs to run in 3 seconds or less,’ rather than saying ‘the administrative report needs to run fast.’

MoSCoW Prioritisation

#RequirementsManagement #Estimation #Planning #AgileProjectManagement

The prioritisation of user stories is driven by the stakeholders and facilitated by the development team. These two groups collaborate to prioritise the stories for a given release according to the stakeholders' business needs and the team's understanding of the highest architectural risks to be addressed. This prioritisation allows the following to happen:

If a situation arises in which it appears likely that deadlines and effort estimates will constrain the development team's ability to deliver all known functionality, the stakeholders' prioritisation of stories facilitates subsequent scope reduction. In such a situation, the stakeholders and the development team can work together to further negotiate and reprioritise remaining stories, to ensure that something of benefit can be produced by the deadline.

Scope prioritisation is a powerful tool for businesses that need to react to, for instance, changing market conditions and new opportunities. As such, scope prioritisation should recur several times during a release. Scope prioritisation and scope reduction must continue to occur until the stakeholders and the development team have agreed on a baseline commitment.

Given that development time boxes (such as releases and iterations) are fixed, the deliverables from a time box may end up being less than was originally planned. If this is the case, it is important that all essential work is done within the time box and that only less-critical work is omitted. The method of ensuring that this is true is to ensure scope prioritisation, which means prioritisation of the stories to help with scope reduction.

Limiting functionality to meet an iteration deadline does not mean limiting quality. As with any software development endeavour, the development team strives to deliver a product fit for the business purpose: defect-free, user-friendly, and so on. The objective at the end of a development increment is to deliver a set of stories that will do useful work when the product is ready for production.

The simple rules known as MoSCoW rules can be used to achieve clear prioritisation of requirements. The development team can use these rules to lead the stakeholders and to formalise the way in which they prioritise the stories for the product under development. The following table explains what the MoSCoW model proposes.

Table 11: Prioritisation Rules

Prioritisation Rules Description
Must have Essential stories that are fundamental for the product development. Without them, the product will be unworkable and useless. The "must haves" define the minimum usable subset.
Should have Important stories for which there is a workaround in the short term. These stories would normally be categorised as mandatory in a less time-constrained project, but the product will be useful and usable without them.
Could have Stories that can more easily be left out of the increment under product development.
Want to have but won't have this time Valuable stories for which there is an appropriate alternative or a manual workaround. These stories can and will wait until later development.
A screenshot of a graph Description automatically generated

Figure 35: MoSCoW prioritisation

User stories may be of different sizes during a project lifecycle, including very large ones that are often called epics. When a user story is close to being implemented, it needs to be right-sized to facilitate its prioritisation, estimation, and development within a reasonable time frame (typically within a time box, such as an iteration). Even if a user story fits within the defined time box, it might still need to be split because it does not fit within the available time to finish.

Prioritising user stories helps to ensure that the stakeholders receive a usable product at the release deadline. Running effective and efficient meetings helps the project to progress at a faster pace with limited usage of resources and time. Below are the high-level steps associated to prioritisation:

Step 1: Prioritise user stories

Step 2: Ensure contingency

Step 3: Review priorities

Since the prioritisation of user stories is driven by the stakeholders and facilitated by the development team, it is desirable that it happens during workshop sessions where both groups get together to have a conversation around user stories and what is the value of each user story for the product owner.

Although the MoSCoW prioritisation is typically associated to user stories (requirements) prioritisation, it can (and should) also be used to prioritise other types of work items, such as enhancement requests, defects, project tasks, and so on.

Setting up Backlogs

#RequirementsManagement #Planning #AgileProjectManagement

A backlog is a list of features or technical tasks (hereinafter, items or work items), which the project team maintains and that, at a given moment, are known to be necessary and sufficient to complete a project. One should take into consideration the following:

There could be two types of backlogs:

These "necessary and sufficient" properties are assessed relative to the team's state of knowledge at a particular moment; the backlog is expected to change throughout the project's duration as the team gains knowledge. The backlog is the primary point of entry for knowledge about requirements, and the single authoritative source defining the work to be done.

The Work Items List (Product Backlog) captures all scheduled work to be done within the project, as well as proposed work that may affect the product. Some of the work items may be implemented in this project, some of them may be implemented in a future project, and some of them may never be implemented. Some of the work items may still be poorly defined; therefore, it could represent a big chunk of work, requiring potentially several months of resource effort. As the priority of these work items increases, they are typically decomposed into smaller work items that represent specific and well-defined tasks that may take hours or days to address. In other cases, specific and well-defined work items are created directly, representing, for example, a defect to be addressed, as the figure below illustrates.

A diagram of a work item list Description automatically generated

Figure 36: Work Items List

Having a Product Backlog provides the information required to plan and manage an iteration. Together with the burn-down charts, the project manager can plan iterations by understanding effort involved, and project manager can manage iterations by tracking how much work is left to do.

Step 1: Manage unscheduled work items

Different work items have different levels of complexity and difficulty. Some work items will require more thinking than others, and the time allocated at the beginning of the iteration for iteration planning may not be enough to fully understand a given work item. One should not wait until the iteration starts to pull the top work items from the stack and start working on them. Instead, it is recommended to look at the work items one or two iterations ahead and do high-level modelling to understand the work items complexity and propose candidate solution to address the high-risk work items, which helps reduce the overall project risk.

Planning Poker

#RequirementsManagement #Estimation #AgileProjectManagement

Planning Poker is a collaborative and consensus-based approach for all team members to participate in sizing estimates for work items. Each person holds a set of planning poker cards with the values 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100,?, and ∞. The numeric values may represent the number of story points, ideal days, or other units in which the team estimates. The '?' represents that the estimator needs more information about the item. The '∞' indicates the item is so big that it is impossible to estimate.

Planning poker assumes that the most competent people in solving the particular task should estimate it.

A screenshot of a game Description automatically generated

Figure 37: Planning Poker

Ideally, the planning poker technique should be used in the context of a workshop environment to refine and estimate higher priority work items.

Step 1: Present and understand the work item

Step 2: Estimate work item

Step 3: Achieve consensus

Effective Iteration (Sprint) Planning

#RequirementsManagement #Planning #AgileProjectManagement

The goal with iteration planning is to establish a few high-level objectives for what to accomplish during the iteration, produce a sufficiently detailed plan outlining who needs to do what to accomplish those objectives, and define how to assess that you accomplished what is set out to accomplish. Iteration planning is ideally done with the entire team (including key stakeholders) in a meeting (typically lasting one to a few hours), at the beginning of an iteration. This ensures that the entire team understands what needs to be done, and they become committed to the success of the project. In some cases, it is preferred to have a smaller subset of people to meet in advance to prepare the meeting with a draft iteration plan.

A diagram of a diagram Description automatically generated

Figure 38: Iteration (Sprint) Planning

Step 1: Define high-level objectives

Step 2: Produce an iteration plan

Step 3: Define Evaluation Criteria

Kanban Board

#RequirementsManagement #Planning #AgileProjectManagement

The Kanban Method is part of the lean management tool set and is used in just-in-time (JIT) manufacturing and in the pull method. Kanban uses a visual (a card and a board) to explain during the build process what and when to produce or add a feature.

In traditional push methods, waste is built-up during the production process as bottleneck steps are hit in the production chain. This causes the inventory to be put in waiting, the overall flow of production is disrupted, and quality of the product decreases.

In the pull method, the last step in the production chain tells the previous step when it is ready to produce. It then receives the work finished in the previous step. This pull is then passed on step-by-step back to the first step. The tools that provide these signals for WIP (work-in-progress) to move downstream via a pull method are Kanban cards and boards.

This lean production method has become popular in project management practices in general, but particularly so in software development, where the development process is much like a production chain in a factory. Kanban and the pull method have also become popular in Agile development, where the WIP moving through the production chain is highly controlled.

A screenshot of a computer AI-generated content may be incorrect.

Figure 39: Kanban board

The figure above shows a standard Kanban board, designed to control a software development process. Each black numbered box represents a feature or a set of requirements of the software that is then moved down the production chain from “To start” to “Transition” and out to operational. As the feature moves from the “Transition” phase’s output inventory to operational, a production Kanban card is sent to the “Transition” WIP asking for another piece to be produced and provided as finished inventory.

As a result, the “Transition” WIP sends an inventory Kanban card to the “Testing” output, asking for another piece of inventory to work on. This pull process moves upstream the development process, until the “Requirements” WIP is asking for “To start” inventory to start working on.

The Kanban method is a pull-based mechanism, which uses visual notifications to indicate when an activity should be performed in a project to limit work-in-progress elements.

The benefits of using the pull method for development and using Kanban to control and visualise the production chain, can be a substantial aid in reducing errors, risk, and time to completion. It also helps to increase visibility and transparency and keeps less inventory in waiting.

However, these methods do require strict set up and diligence of the project manager to follow up.

Below are some steps and guidelines to using the Kanban method:

Step 1:

Step 2:

Step 3:

Step 4:

Step 5:

Step 6:

The following are the best practices to follow when using the Kanban method:

Burndown Charts

#Planning #MonitoringControl #AgileProjectManagement

A burndown chart supports to track the progress of an agile project. It has a y-axis showing measurable points that are planned to eventually go down to zero, and an x-axis that shows the total remaining time to do so.

Typical items displayed on the y-axis include hours, functionality, budget, work items, and defects. The x-axis usually tracks days, iterations/sprints, or releases.

In all cases, the total amounts are plotted that will change over time (up or down) but ultimately reaches zero by the end of the assigned time (on the rightmost side of the graph).

Some examples of specific types of burndown charts are as following:

A graph with a line and a line Description automatically generated

Figure 40: Burndown Chart Example

The above burndown chart is an example of tracking the iteration burndown rate. At the beginning of the iteration, there are 55 work items assigned to this iteration. The blue line illustrates the number of work items to be completed. The red line shows the number of work items that were added to the current iteration. Adding work items in the middle of the iteration can happen when new defects are discovered or additional tasks are necessary to complete the original tasks.

Iteration burndown

Release burndown

Burnup Charts

#Planning #MonitoringControl #AgileProjectManagement

A burnup chart supports tracking the progress of an Agile project by showing how much work has been completed over time. Like a burndown chart, it has a y-axis and an x-axis, but instead of tracking work remaining, it tracks work accumulated toward completion.

Unlike burndown charts, burnup charts do not necessarily end at zero. Instead, they show progress rising toward a fixed target, making it easier to visualize scope changes and how close the team is to completing the work.

Some examples of specific types of burnup charts include:

A graph with a blue line AI-generated content may be incorrect.

Figure 41: Burnup Chart Example

A comparison between the Burndown and Burnup Charts is summarized in the table below:

Feature Burndown Chart Burnup Chart
Tracks Remaining Work Completed Work and Scope
Scope Changes Visible No Yes
Visual Trend Downward Upward
Best For Short Iterations Long Term Tracking

 Use a Burndown Chart When:

Use a Burnup Chart When:

Conducting Retrospectives

LessonsLearnt #RequirementsManagement #AgileProjectManagement

Retrospectives aim at capturing Lessons Learnt conducted at the end of a project. The spirit of retrospectives should be imbued across the project continuum, conducted at key project milestones, such as at the end of project iterations, after the releases, immediately upon occurrences of key project incidents (significant unexpected events). When the practice of Retrospectives is intimately intertwined with the processes of the project, the health of the team is constantly monitored, the "heartbeat" of project progress is readily measured, and the team focuses on an awareness of opportunities for improvement and increased productivity. A symbiotic relationship emerges between an evolutionary development process and a Retrospective that supports the various methods of inspection and adaptation.

A screenshot of a computer Description automatically generated

Figure 42: An example of the Retrospective Template

A key characteristic of this learning approach is that it relies on the commitment from the team members to complete the suggested improvements that have been chosen for application in the next iteration cycle. The visibility and commitment among the members of the team imbue a sense that the Retrospective was worthy of the team's investment of time, and that the results of the work on the Retrospective will be tracked in the next iteration cycle.

The steps below can be followed to incite the Retrospective team to begin their collective investigative work.

Step 1: Define the scope of the reflection, retrospective, review

Step 2: Evaluate how the work was done

Step 3: Define what can be done better in the future

Step 4: Capture the findings

The questions are expected to generate actions that will assist the team in prioritising suggested improvements for the project, to be implemented during the subsequent cycle. In addition to the aforementioned investigative questions, a Retrospective should include steps that provide structure for the team focus and resulting work.

The mere execution of Retrospectives is insufficient without an organisational commitment to a collaborative culture. The success of Retrospectives is directly proportional to, and necessarily contingent on, an environment that promotes highly motivated and performing teams (not the individual), nurtures open and frequent communication, and provides a thriving sense of dedication to the team community. Retrospectives embody the spirit of team collaboration and self-reflection by offering an environment in which teams are encouraged to provide feedback and identify lessons learned. The compositional aspects of the team are crucial in supporting the highly collaborative nature of Retrospectives, enabling the team to produce insight(s) into improving the processes of the project.

An effectively facilitated Retrospective will create an environment that is conducive to various practices of inspection and adaptation. The methods of inspection and adaptation are project control mechanisms that assume, and respond to, the existence of complexity, unpredictability, and constant change. Practiced in the context of a Retrospective, the methods of inspection and adaptation produce a feedback loop enabling flexibility, responsiveness, and reliability.

Appendix A: Contributions and Acknowledgements

This publication has been produced by the European Commission, DIGIT.A2.001, Procurement and Programme Management Solutions. Portfolio Methodologies and Tools

Methodologies Office (MO):