Agile Micromanagement, the good and the bad

Jim Highsmith wrote an interesting post about micromanagement. He mentioned Steve Jobs and Bill Gates are good examples of successful product manager micromanagement. I totally agree with that.

He also talks about the Agile process micromanagement. Experiencing both worlds, waterfall and agile as a developer and a manager. I have a strong opinion about it. Agile is all about micromanaging!

Consider these:

  • You are coding and someone is talking about your code as you type it (Pair programming).
  • Every day you stand up and tell the whole group what you did yesterday and what you will be doing today (Daily Scrum meeting).
  • You retrospect about what you did well and what you can improve on (Retrospective)
  • You show everybody exactly which task you are working on and how it is progressing (Visible card wall)
  • You respect work in progress limits (Kanban WIP limit)
  • You make a code commit and let everyone know about it. (Continuous Integration)

The more I think about it, the clear it is to me: Agile is all about micromanagement. The good or bad depend on how people adopt its principles and practices. I have experienced many benefits that come from such micromanagement. In fact, when I look back at all projects I participated on, the projects I consider more successful (people enjoying working, delivered great products and improving the work process) are the ones with lots of micromanagement.

 

Paulo Caroli

Paulo Caroli is an author, speaker, and consultant specializing in agile transformations, Lean Inception, and OKRs. With over 30 years of experience—including nearly a decade in Silicon Valley and 18 years at ThoughtWorks—he has helped organizations transition from project to product and from strategy to execution. Creator of the Lean Inception methodology and author of bestselling books like Lean Inception and Team OKR, Paulo is dedicated to empowering teams to align, validate, and deliver real business value.
Triple Track Development: Business Innovation Through Continuous Discovery and Continuous Delivery

Triple Track Development: Business Innovation Through Continuous Discovery and Continuous Delivery

Continuous Triple Track Development, comprising Business Strategy, Discovery, and Delivery, revolutionizes product development. Quarterly goals replace yearly plans, ensuring adaptability. Continuous Discovery delves deep into user needs, while Continuous Delivery swiftly transforms validated ideas into products. This synchronized approach fosters unprecedented collaboration, propelling teams towards collective success. It’s not just a methodology; it’s a strategic advantage, enabling businesses to innovate rapidly in today’s dynamic market.

read more
New Book Alert: How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas

New Book Alert: How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas

Introducing our enhanced book, “How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas.” Evolving from its predecessor, this edition responds to valuable reader feedback, refining both content and title. Delve into the world of effective product development and user story management, discovering the integrated power of the PBB Canvas. Embrace an enriched reading experience and explore insights from thought leader Jeff Gothelf in the preface. Don’t miss a reader’s insightful review, preserved for wider readership. Join us on this journey of empowering user story craftsmanship, and witness the transformation of your product development goals.

read more
Product thinking strategy questionnaire

Product thinking strategy questionnaire

The questionnaire below elaborates on a few important aspects of product thinking, problem understanding, solutioning and strategic delivery planning.   I have used this questionnaire as part of a workshop on Product Leadership and Strategic Alignment. Basically,...

read more

Pin It on Pinterest