Why is so hard to educate a waterfall project manager to take a role in a Scrum Team?

(Cabanas Beach, Portugal) A lot was written already in this blog about why we have more advantages adopting Agile methods. The truth is, once an organization decides for an Agile Transformation, adopting Agile methods and, particularly Scrum practice, to train and educate resources can be a terrifying challenge. Even with training, the roles will change. The background experience required for a Scrum Master or Product Owner role, for instance, is very different from what normally it comes with an experienced resource acting as project manager in waterfall methods since many years.
Continue reading “Why is so hard to educate a waterfall project manager to take a role in a Scrum Team?”

Annoyances: How to deal with critical issues, not planned, entering in the middle of the sprint or release

It’s always annoying when something comes up out of the plan and the team must fix it or manage it inside the sprint. Unfortunately, we must deal with unpredictability. Nevertheless, is always good to analyze why we had to deal with those annoyances.
What can be considered an annoyance? In my opinion, we can consider as critical bugs or unplanned change requests, we receive during the sprint or release and we must integrate or fix it within the sprint. In this post, we will approach, in a generic way some reasons for this and if it happens, who will report it into the backlog and which other measures should we consider to keep the sprint in a normal speed.
Continue reading “Annoyances: How to deal with critical issues, not planned, entering in the middle of the sprint or release”

What can we learn from bugs?

(Berlin, Memorial to the Murdered Jews of Europe) – Some weeks ago, when I visited the Memorial, the feeling of loneliness and lack of direction invaded me. I think this is the main achievement of theĀ architect (Peter Eisenman)… bring this feeling to the visitors. And from the position in the picture I asked to myself “What have we learned from this horror?”. Inspired by a continuous learning for a continuous improvement, I would like to make the question applied to bugs and change requirements (CR), but particularly in this post: what can we learn from bugs? We should take them all as improvement opportunities.

Continue reading “What can we learn from bugs?”

Requirements hierarchy, what should be written per level and by whom

(Berlin, Germany) Sometimes the most obvious Agile concepts are not so easy to be applied when we need to make a practical usage of them. Specially if we need to bring into a consistent and common understanding a product or portfolio vision for later implementation. My goal with this post is to share a very personal opinion about how and whom should fulfill those Agile requirements levels.
Continue reading “Requirements hierarchy, what should be written per level and by whom”

Egocentrism, Narcissism and the middle management blocker to Agile Transformation

An Organization is described by processes and structures, those define the way people interact. But individual values often tend to sabotage the organization evolution. This is often observed during Agile Transformation processes, specially from a middle management layer, insecure about their skills to guide an Agile team to deliver excellence to the end user.

Continue reading “Egocentrism, Narcissism and the middle management blocker to Agile Transformation”

Retrospective meeting – Simple techniques helping you to moderate the dialogue with the Team

Retrospective meetings are recurring meetings that will normally take place after the sprint review meeting. These are very important moments to make a team think about what can be improved. But sometime there are moments when the team is faced with some difficulties in dealing with problems.
Continue reading “Retrospective meeting – Simple techniques helping you to moderate the dialogue with the Team”