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 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.
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 🙂
I already did many Refinement meetings (or grooming meetings, as you prefere it). I think those are my favorite AGILE ceremonies, that moment where after a delicious, creative and smart discussion everybody selects THE CARD!!! There you observe so many things: who leads, who knows, who loves risk, who is more cautious, who influences, who will implement it 🙂
This topic was initially approached in the post How do you define a PoC? , now the focus will turn to the results evaluation: what have we learned with it? Was it worthy the time invested with a critical feature? Have we enough information to start immediately an MVP?
Point your budget to the right investment and best solution design: to buy new or optimize installed applications?
Often, we observe a discussion in our projects about how to start it, it’s what I call a solution design dilemma: it is quicker to start a new project acquiring new software than to consider design a solution from installed applications, or even considering to upgrade them to new versions. Interestingly, in most cases, these