Don't complicate it! Project management by P3.express method (management)

Don't complicate it! Project management by method P3.express (heading #Management)

Read it. book Dmitry and Valeria Ilyenkov about project management and I liked it. The book itself was given to me by Dima, with whom we have known since the days of Teamlead Conf. 2020where both performed. In my sense, "Don't complicate" is "Write, shorten" for project management, but in a good sense of the word. (||"Write, shorten"|| contradictory ||for me||). "Don't Complicate" has many examples, simple words, clear structure and presentation without feeling like you're going to be swamped with terminology for the sake of terminology. At the same time, the book is not "about talking", but about a completely applied framework: the P3.express method is divided into 33 step 7 To make the project more transparent and predictable without heavy process transformation. I liked this simplicity - as I'm too tainted by IPMA theory, PMI, layered PMBoK and all the beautiful bureaucratic splendor that often comes with project management:)

When it comes to books, they are like this.

1. She's very down to earth. Tips are almost always backed up by stories and cases - from Boeing and SpaceX to the Sydney Opera, Denver Airport and the authors' own facaps. Because of this, recommendations do not hang in the air.
2. It can be safely given to beginners who need to easily and easily understand how to start working with projects. And it can be given to experienced people who are tired of bureaucracy and want to simplify processes without ruining management altogether. The authors directly write that the book is useful not only for projects, but also for teams, owners of IT companies, analysts and other people who regularly make projects.
3. For technical managers and engineers, the book is worth reading. Not because everyone urgently needs to become PM, but because it explains the basic pillars well: who is the sponsor of the project, why you need a brief summary of the project, how to decompose the results, why regular Go/No-Go is useful, and how not to drag dead initiatives just because they have already been pumped into forces and money.

I also liked a piece about sunk cost fallacy through Concorde. The authors remind that the Concorde effect is when the project obviously does not fly, but it continues to be dragged simply because too much invested. In P3.express, there is a recurring Go/No-Go test for this: not “how to press,” but honestly ask if the project is still needed or we are suffering from inertia. A very sensible thought for corporations and big domestic initiatives.

The six principles of p3.express are as follows: Choose results and facts over habits and attachments Save team energy and save resources

• Act proactively.
• Find the weak link in the system. Do nothing without a clear purpose. Rely on reused elements: templates, checklists, repeatable steps

The life cycle of the project in P3.express is also minimalistic and clear.

• Start of the project
• Cycle planning
• Weekly control circuit
• Daily control circuit
• Closure of the cycle
• Completion of the project The post-project phase, where benefits and new ideas are evaluated

In general, if you want not another “great body of knowledge” ala PMBoK, but a sane book that can be recommended to people nearby – products, teams, engineers, young managers and tired executives – “Don’t complicate” looks like a very successful candidate. Not as a replacement for PMBoK, but as a good antidote to it. (I read PMBoK in three different publications.)

P.S. Dima and I agreed to record an episode of the podcast and discuss project management in general, as well as this book in particular. Anyway, stay tuned...

#Management #Leadership #ProjectManagement #Processes #Engineering