Agile in 31 days

Hola amigos! Sunday! Tip:I prefer to think that this is the first day of the week rather than the last one! However while you are on leave, you will feel that there are no Mondays :-) Awesome! Anyway. Today I was thinking about the " Sprint Reviews ". By the way, not sure if I have already linked you to  Mountain Goat Software  website before in here. This is Mike Cohn 's company - one of the co-writers/co-signers of the Agile Manifesto . Absolutely recommendable for quick checks on Scrum/Agile topics. Surely  Sprint Review. This is the "demo" where we demonstrate how good we did within the sprint. Right?  I assume everybody knows about it so I'll stick to the main point.   Why do we do sprint reviews? This is the first question we need to ask ourselves. So, doing a bit of brainstorming: - To encourage the team to feel part of the sprint delivery via presenting their product. So to speak, increasing the team spirit. - To demonstrate the pr...

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 ...