Agile in 31 days

Hola amigos! It's been a long month and finally we are about to complete the last day of these 31 days agile blog experience! Since today is the last day of the year I'll get a Victoria beer ! I was thinking of what is the best way to end the blog. What about inspecting and adapting the blog itself so I can take actions to improve if this experience is repeated in the future? Sounds like a retrospective! Trying first of all to be constructive...  The Prime Directive "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." Should I raise my hand to and say: "I agree". Quite obvious. So do I :-) What went wrong? Most of the entries were not deepened. In order to keep the easy-going style, not very long, I feel that some of the posts could have a longer content.  Difficulti...

Hola Hola! Maybe not the right time for a coffee. No. There's always a good time for it. Agile coaching is tough. Very tough. Essentially we (people) are... tough. You need to have a strategy (your epic) and a full set of tactics (user stories) that align to a common goal. Within my career. When providing Agile coaching, this is structured in few phases: 1. Understanding of the current situation and who the people are and behave. This is a continuos work since people are not predictable and you cannot even draft an immutable plan. However, we need to start from a point, let's say our sprint 0. We will be learning as we go. Last week for instance. Our starting point was the understanding of our evolution as a team and an individual brief profile description .  " We know how we are (Now!) and what brought us here" 2. Additionally, provide with sufficient materials, documentation to read as a guideline to self-"learn" and estimulate the idea of...

Hola! Please take a seat and have a coffee! On Agile environments, I have noticed how member of the teams quite often raise up their voices saying: "We have so many meetings, I cannot do development, this is boring". Let's say a Scrum implementation. We have several ceremonies: Sprint Planning, Poker Sessions, Stand-ups, Retrospective and Sprint Review. At least. Then we can have one-off, ad-hoc meetings such as 1-to-1s, trainings, general discussion meetings. On a 2 week-cycle we can count the number of hours a sprint on meetings. Let's say 2-3 hours grooming/sizing, 4 hours on the sprint planning, 1-2 hours retrospective, 10 minutes x 10 days on Stand-ups. This is perhaps a 10% of the sprint. But where is the problem? I have been a developer back in the time and still. I hate meetings. Sometimes a meeting is just a reminder of a calendar to talk about something "There is a problem, let's have a meeting with the maximum amount of people possible so ...