[2/2] The Mythical Man-Month (The mythical man-month)

Continuing the story of Brooks' classic book (1 and 2)I will tell you about where his ideas can be developed now.

1) To prevent delays in the project delivery schedule Do not save tech debt, which will shoot closer to the delivery of the project Do not use mythical man-months, but take metrics of real performance: cycle time, throughput and others. 2) Architectural principles It is worth maintaining conceptual integrity from the very beginning of the project - I would suggest using RFC. (request for comments) to discuss architectural issues, fix solutions in ADR (architecture decision records). I mean that somehow. told A report on the scaling up of architectural processes over the years 5 backwards It is also worth investing in documentation, putting it closer to the code and automating as much as possible. 3) Communications It is desirable to reduce the meeting to the maximum, and those that disappeared to transfer to asynchronous mode, which means writing more documents and commenting on them asynchronously. Allocate focused time to work - this will not break the flow of work (flow state) 4) Scaling up teams

• Here I just recommend a look at the approach from Team Topologies, which is good to describe the type of commands and formats of their interaction. I’ve talked a lot about this book and handler In the first episode of the Code of Leadership podcast with Stas Halup, my former colleague.
• In fact, it works. 2 Main types of commands: stream-aligned and platform. The first creates business value, and the second makes platform tools that use stream-aligned teams. Well, it is important to take into account the numbers of the Donbar to understand the boundaries of scaling due to the overhead of communications.

To sum up, Brooks’s book is still not outdated and can be applied to contemporary problems. While Agile and DevOps are tackling problems of random complexity, its warnings about resource overload and design fragmentation remain relevant. Teams achieve sustainable productivity through a balance of automation and people-centered processes – confirming Brooks’ view of software development as a human-centered process. With the growing scale of distributed systems, a return to the Mythical Man-Month offers both caution and inspiration: Tools change, but team dynamics determine project success.

#Management #Leadership #Software #Engineering #Process #Project #Architecture #DevOps