Archivi tag: books

The Goal: A process of ongoing improvement – Quick review


⏰⏰⏰⏰⏰ / 5


Visualizza immagine di origine

Quick review

I read this book because it is listed inside the bibliography of The Phoenix Project and this was a good reason to go for it.

The book is written as a novel and explains the Theory of Constraints inside the process of growth of the main character, Alex Rogo. He’s in charge of a manufacturing plant in serious trouble and he has 90 days to increase performance to save the plant from failure.

The title of this book represents the main question that Alex ask himself to understand what actions he must undertake to solve the task assigned to him. This is the first of many questions that the author uses to drive the improvement and the change of Alex.

The author opens the reader’s mind by revealing us a new way to think about performance and what are the really important things to do to achieve The Goal. He does that with a socratic approach and a progressive discolsure of concepts guided by events that happens in the plant.

If you’re searching for a book that teaches how to think in an effective way and how to organize complex activites inside a plant this is the book for you. Don’t wait to buy it, do it now!



Reading – The Manager’s Path

I’m currently reading Camille Fournier’s “The Manager’s Path”.

It’s a practical guide to be a better manager in tech. The are some general management principles but it is very specific for the tech/software world.

I find it very inspiring and it makes me think about how I interact every day with my team: what am I doing wrong, what am I not doing at all?

What do you do to be a better manager today than yesterday?


The best tip on software estimation I’ve ever found

Count if at all possible. Compute when you can’t count. Use judgment alone only as  last resort. (Steve McConnell)


Count-first is the approach that Steve McConnell suggests in his Software Estimation book.

If you can count the answer directly you should that. […]
If you can’t count the answer directly, you should count something else and then compute the answer by using some sort of calibration data.

Reading about this approach makes me think about how I estimated things in the past. My job is changing and the tasks of estimating and scheduling are more frequent. I know that software estimation is hard and crucial for every project to succeed.

If you, like me, are having troubles on software estimation I strongly recommend Steve McConnell’s books “Software Project Survival Guide” and “Software Estimation”. They are like strong related cousins; you’ll be a better software project manager if you know how to estimate and you’ll estimate better if you know how a software project has to be done.