Chess -

Archivos de Autor: Antonio Martel

Illusion of Control

You have been working in chronograms, Gantt diagrams, risks and resource management, more graphics specifying who reports to whom, dreamed plans, and the name of the people who should be blamed in case of not meeting a deadline. You are probably thinking everything is under control, but nobody reads those documents, skimming them at best. 

When you see paperwork like that one, you might be thinking “What a great project manager I am. Every single detail has been captured”, but it might be only an Illusion of Control. What are you doing to help the team to be more productive? How do you plan to overcome Parkinson or Hofstadter’s laws? Other than getting everyone nervous when a deadline is getting closer, have you helped them to remove obstacles? Are you sure the team is delivering value? Ticking a checkbox for every completed task is not getting you any closer to the objectives if the outcome is faulty or doesn’t provide any utility.

Theory of Constraints (TOC)

It’s based on the search of bottlenecks and critical paths in your operations, so you can improve the process as a whole as any improvement in that point will enhance the total outcome. The idea comes from factory lines where a machine or an activity is delaying the whole line and preventing you from manufacturing more tomato soap cans. 

Your team probably (I hope) follows a sequence of actions: First user story is refined, then developed, tested, reviewed by colleagues, after that a pull request is triggered, software is merged, then tested in an integration environment, and finally reviewed and approved by Product Owner. What is constraining you from delivering more value at the end each iteration? Maybe your refinement session is not long or frequent enough to get all the stories refined, or perhaps Tech Lead is too busy for the huge amount of pull requests she is receiving, and they start to pile up in the repository tool. Do you need another pull request approver? 

Analyze the series of steps your team follows. Try to tweak your proceedings a little bit every time. You’ll make significant progress in your cycle time.

The error of choosing the cheapest supplier

A common mistake in projects is choosing the cheapest supplier to save on costs. There is a risk that it will be because it cannot compete on quality with other suppliers and will have to compete on price. The other solution providers are probably better at managing uncertainties, and choosing this one adds uncertainties and delays to the project.

A 20% discount in the choice of the supplier can represent only 2% in the total cost of the project. Is it worth putting at risk the delivery of the entire project, the costs due to delays, or the extra costs due to quality or errors for a supposed 2% savings?

Read in the book “Critical Chain” by Eliyahu M. Goldratt.

When everything is a priority, nothing is a priority

I remember when I read the book “Prioritizing the Product Backlog” by Roman Pichler. He wrote: “I’ll never forget the day when I suggested to the product manager of a new health-care product to prioritize the use case pile in front of her. She looked at me, her eyes widening, and replied, ‘I can’t. They are all high-priority’”.

Quoting to Karen Martin: “When everything is a priority, nothing is a priority”. I have faced this issue too. I tried to solve it by telling the manager that the team couldn’t be working on five tasks at the same time and asked her what she wanted to obtain first. She didn’t hesitate a second and pointed to one of the user stories. “No doubt,” she said, “this one, definitively”.

How does Agile help you to deliver?

Have you ever wondered why Agile is so widely adopted? How does it help companies to deliver sooner and better? Here are some tips:

  • Releasing frequently improves customer satisfaction and allows the client to decide how the product is evolving.
  • Sprints are small milestones. They help you to overcome the Parkinson laws and avoid feared deadlines at the end of the project, when little can be done if something went wrong.
  • The Kanban board, the backlog and the sprint backlog make visible the pending work and how we progress (have a look at the Checklist Effect by Atul Gawande).

Esta web utiliza cookies propias y de terceros para su correcto funcionamiento y para fines analíticos. Contiene enlaces a sitios web de terceros con políticas de privacidad ajenas que podrás aceptar o no cuando accedas a ellos. Al hacer clic en el botón Aceptar, acepta el uso de estas tecnologías y el procesamiento de tus datos para estos propósitos. Más información