<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=2740041&amp;fmt=gif">

User Perspectives

User Benefits

    Stay Up to Date

    Newsletter

      Blockchain technology will fundamentally change project management: that’s what the first academic articles and publications on this topic claim. But is that really the case? After all, at first glance, the two topics seem to have little to nothing in common. Thomas Schlereth, founder and CEO of Can Do, takes a closer look—and discovers some interesting potential applications.

      Can Do Blogpost Blockchain und Projektmanagement 1 von 2But let’s start with a brief introduction to project management and blockchain technology:

      Project management is a method of work and organization designed to achieve a defined result within a planned project, within a specific timeframe and within a financial budget.

      Blockchain is a digital process for storing transactions in computer systems in a decentralized manner so that subsequent alteration of the transactions (forgery, manipulation) is not possible.

      So how are PM and blockchain related?

      Project plans form the basis of contracts. In written contracts between companies, elements from a project plan are agreed upon in a legally binding manner. These often include deadlines and delivery quantities, assurances regarding personnel with specific skills, quality assurance measures, and documentation requirements. The connection can best be illustrated using deadlines in contracts. In work or project contracts, deadlines for specific deliveries of interim and final results are contractually stipulated. These deadlines obligate one contracting party to meet them and, under normal circumstances, not to postpone them. This transfers a project risk from the client to the contractor. Failure to meet these deadlines sometimes results in contractual penalties that the contractor must bear if the deadlines are not met.

      These contractual deadlines are not arbitrarily included in the contracts by lawyers or managers. Rather, a jointproject plan is developed through collaboration between the two partiesBlockchain in der Projekt-Praxis. The result of this planning is milestone dates and project completion dates. Only after this planning process are these deadlines incorporated into the contract. Furthermore, it is contractually agreed that the client may not alter certain framework conditions of the project in such a way that the contractor is unable to meet the milestones as a result. This is regulated throughchange processes—known as “Change Requests”—which both parties must approve. Describing all of this in legal and methodological terms so that any deviation does not lead to a conflict is difficult and, above all, a complex undertaking. In the event of a significant deviation from such agreements, blame is often shifted back and forth between the parties during the course of the project.

      The contractor, in particular, is sometimes very anxious in this situation, as the pressure initially falls on them. Before the project begins, they must prepare a plan —sometimes highly detailed —that is thorough enough to ensure they can comply with all contractual agreements.

      This leads to two outcomes:

      First, before the project begins, every risk and requirement is analyzed in as much detail as possible to avoid any unpleasant surprises during the project.

      Second, buffers are built in that are not visible to the contractor but are used by the contractor if something unforeseeable happens that jeopardizes the deadlines or the scope of work. The result is therefore a very high level of effort in detailed planning and assumptions before the project has even started—plus a “manipulated” schedule with buffers.

      However, the client’s need for security also creates a substantive problem during the course of the project: The contractor resists allowing changes to the project as much as possible, even if they would make technical sense. In this case, the contractor must once again carry out a detailed adjustment to the schedule (with the risks mentioned above) and agree to a change in the contractual deadlines and scope of work.

      Thus, when in doubt, the contractor accepts a poorer project outcome rather than risk paying contractual penalties. As a result, the project outcome may be worse than it could be.

      Clients tend to impose more and more conditions to ensure they are never held responsible for a delay—which they may have caused themselves.
      However, project plans contain a wealth of additional details that are then laboriously incorporated into the contracts. These include, for example, specific project staff members from the contractor who are assigned to the project. Furthermore, the client has obligations to cooperate. The client must test and accept deliverables and must also provide the appropriate personnel for this purpose. The list goes on and on, and it all leads to a crucial question:


      Why isn’t the project plan established as the basis for the contract?

      There are several reasons for this; describing them all in detail would go beyond the scope of this essay, so I will outline only a few.

      Theplanning must meet a certainstandard of quality. To achieve this, it is essential to use professional project management software that, above all, realistically highlights the risks—such as resource overload—for the client. A fancy PowerPoint presentation or an Excel file is absolutely unsuitable for this purpose.

      Furthermore, the contractor has a certain incentive to “hide” buffers within the project. This is also possible with project management software. However, this would have the negative effect within the contractor’s company that such planning might tie up too many resources for too long.

      A much bigger problem, however, is the evidential value of such a plan, no matter how detailed it is. Printouts or PDF files are often attached to contracts. But a project plan is much more than just a “graphic” representation of a sequence or epic plan. Behind it lie resource allocations, imprecise planning, budget line items, risks at the time of printing, and so on. It is therefore more of a digital set of data at that specific point in time—not only for this project but also for all other activities within the client’s company at a given moment.

      The quality of the planning must be sound in order to have a solid contractual foundation

      Detailed, preciseplanning with hundreds of work packages is not practical for this purpose. Projects are generally too difficult to predict and too volatile for that. A more rough, phase-oriented plan that works withunEine gute Planung gehört zum Projektmanagement data is simply more realistic in this context and can be accepted by all parties.
      An imprecise plan—in which a milestone is not set for June 1, but rather for June 2022—allows for a margin of flexibility that is acceptable to all parties. Instead of specifying key resources by name, required skills could be defined, which can be fulfilled by different people throughout the project.

      The client’s required capacities can be specified even if availability details are not known. Rather, a (rough) minimum set of skills that the client must provide is simply included in the plan.

      Data Manipulation—What Is a Base Plan?

      Of course, it makes sense to create a so-called baseline plan at the moment the project agreement is reached. A baseline plan is a copy of a project plan that can no longer be changed as of the moment the baseline plan is created. It’s like a copy of an Excel file that can no longer be modified—only not as a flat file, but as many data records or objects, depending on the project management system. However, most project management systems do not store all the data the system has about the project in the baseline plans, but only a select few. Often, only deadlines are included in the baseline plan.

      Furthermore, such a copy is not immune to manipulation. The baseline plan is also just a collection of records in a database that can certainly be modified retroactively. There are even project management systems that allow this as a standard feature.
      Ultimately, all data in a multiproject management system should actually be “frozen” and backed up at this point to allow for proper validation later on. This subsequent review must then be performed by programs; a manual review would be far too time-consuming.

      The Passing Down of Responsibility

      In today’s interconnected world, project work is often subcontracted by the contractor to subcontractors. Either the client is aware of this and tolerates it, or the client is completely unaware. This “downward” chain can extend as deep as necessary. In large-scale projects, traceability is established through project documentation that can sometimes be enormous. This is actually unnecessary. An example will illustrate this:

      The PRINCE2 project methodology includes instructions—for example, for the project manager—on how to regularly review and optimize certain plans. The project manager must document that he has done this, preferably in a form where he checks a box. Whether he actually did so—regardless of any benefit it may have had—cannot be verified: he simply checks the box. In project management software that supports such PRINCE2 documentation, this is also recorded. What isn’t recorded, however, is whether risks were present in the digital plan and whether the project manager even viewed or adjusted the plan in the system. As mentioned: He simply checks a box with the mouse.


      Blockchain to Secure Basic Planning as a Contractual Basis

      The first obvious approach would be to record each planning element as an entry in the blockchain. Any subsequent manipulative modification of one of these data elements would effectively destroy the blockchain for that element.

      However, the volume of data in the blockchain would be very large if this were done for every single planning element. Therefore, it makes more sense to create a single blockchain entry for the entire planning set. Later, it would then be possible to determine whether the baseline plan had been changed—but not exactly which parts. This is entirely sufficient, because the baseline plan, by definition, must not be altered.

      Outlook

      The second part of Thomas’s reflections on blockchain in project management addresses, among other things, the safeguarding of project documentation, potential analysis in the event of a dispute, and the general advantages of blockchain for project work. He also offers a look ahead at application scenarios in project management and assesses the impact of blockchain technology on digital transformation in the 21st century.

      Want to learn everything there is to know about hybrid project management, the “Can Do” mindset, and new technologies in PM right now? Let us give you a no-obligation consultation—just get in touch!

      An overview of our two-part blog post series:

      Masterclass Hybrides Projektmanagement

      As a member of the management board, Thomas is responsible for the operative management of the development including conception, design and further development of the software. He also advises customers on best practices and supports the roll-out.

      Blockchain and Project Management – Part 1

      Audit-proofing and protection against falsified data: Here’s what blockchain technology can do for your PM. What else? ...

      Read More

      Recommendations for Action in Practice

      "The Human Factor": An empirical study analyzes the use of control measures in projects and their impact on project ...

      Read More

      IR Management Consulting: Can Do Is Not Just Another "Me-Too" Project Management Tool

      Watch the IR Management Consulting video to find out why IR Management Consulting considers Can Do's project management ...

      Read More