Why should we estimate?
Why should we estimate? What are we considering when we do it? Yes, estimation accuracy is a matter of practice maintaining the same team constant. What and how can we … Continue reading Why should we estimate?
Category: SM
The importance of the regular alignment between different Organization levels
When Agile Transformation enters in a scale process, the challenge starts. It is mandatory regular alignment across the different portfolio levels to make sure that the Transformation occurs.
Interviewing Agile Professionals: Mark Ansonia
I’m very happy to announce today our first Interview with Agile professionals! I invited Mark Ansonia for our first interview with experts in Agile roles. Mark is a very experienced Scrum … Continue reading Interviewing Agile Professionals: Mark Ansonia
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 … Continue reading Why is so hard to educate a waterfall project manager to take a role in a Scrum Team?
Bugs, change requirements and the PO dilemma
Type of bugs and CRs we can face, contexts we will face them, who normally will report them into the backlog and the product owner dilemma between occupy capacity with new feature or fixing bugs or improving/ adapting product details.
Egocentrism, Narcissism and the middle management blocker to Agile Transformation
An Organization is described by the processes and structures that define the way people interact. But people has individual values that sometimes can to sabotage the organization evolution.
Retrospective meeting – Simple techniques helping you to moderate the dialogue with the Team
Retrospective meetings are recurring meetings that usually take place after the sprint review. 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.
Moscow – a reference technique helping you to define Product Roadmap or MVP priorities
Sometimes when we are requested to present a Product Roadmap it is hard to start… Start from where? Which features? Which inter-dependencies? How to define priorities? Priorities in the order of the tasks or in the features to enhance product value? MOSCOW can help you 🙂