Project Complexity Assessment

1. Mai 2020
Kategorien
Newsletter abonnieren

One of the main reasons technology projects fail so often is their (underestimated) complexity.
 
Managing this complexity should be an urgent concern for any organisation doing large technology projects.
 
And before you can manage the complexity of your project, you need to understand what drives the complexity of your project.
 
That is why I created the Project Complexity Assessment.
 
This assessment will guide you through the 3 dimensions (structural, sociopolitical, and emergent) of project complexity by asking you 41 questions.
 
At the end of the assessment you will get a score between 0 and 38. The higher your score, the better you have a grip on the complexity of your project. 
 
Most questions have detailed feedback with links to more insights on how to handle this part of project complexity.
 
In use, the benefits of this assessment arise not directly from the questionnaire but from the subsequent conversations between people involved in the project.
 
Your Project Sponsor, Project Manager, Steering Committee, and main Stakeholders need to sit together and go through the answers. 
 
You need to discuss how to reduce the complexity as much as possible and how to manage the remaining complexity actively.   
 
The Project Complexity Assessment is, in other words, a tool for transparency and sense making.
 
The assessment is based on research from Stephen Carver, Senior Lecturer at Cranfield School of Management.
 
Tags

Das könnte Sie auch interessieren

8 Signs of troubled projects for project sponsors

19. April 2017

When you’re dealing with a troubled project, there are usually a number of red flags surrounding you. This article is written from the perspective of senior management (for instance the project sponsor, members of the Steering Committee, or the executive management). All of us have endured troubled projects that didn’t accomplish their intended business goals. Such watermelon projects,

Weiterlesen

Building Is the Easy Part…

6. März 2017

Agile Frameworks and books tell us how to build a product–that’s the easy part… What we are not told are equally important things like maintaining, operating, fixing and extending the built product. When your agile philosophies fail to cover these areas, it greatly reduces agile’s benefits. This is where DevOps comes into play. DevOps is the combination

Weiterlesen

Paying Technical Debt

15. Januar 2017

The metaphor of technical debt in code and design can be defined as follows: You start at an optimal level of code. In the next release, you are adding a new feature. This would take an effort E. This, of course, assuming that estimations are somewhere near reality. If the level of code was less

Weiterlesen

Outsourcing Technical Competence Is a Very Bad Idea

2. Dezember 2016

Organizations do not lose control of large technology programs because they outsource work. They lose control because they outsource understanding. It usually starts with a familiar pattern. A company decides to implement a major system on a technology it does not truly understand. ERP, CRM, HCM, core banking, it does not matter. The internal capability

Weiterlesen

Estimating with Wideband Delphi and Monte Carlo Simulation

18. Oktober 2015

During the LeSS training in Berlin last week with Craig Larman he mentioned the best estimating method he knows for any big software project. Wideband Delphi with Monte Carlo Simulation. I agree with him on this one hundred percent. This article will explain what Wideband Delphi and Monte Carlo Simulation is (Part 1 & 2),

Weiterlesen
Previous