Abstract: Come and see what were the
biggest mistakes I made as a Scrum Master while applying Agile principles, their consequences and how I've overcome them! Short iterations by default, not breaking things small enough or lacking of project management are some of the topics covered. Come and learn how you can avoid them!
Lessons Learned from Your Experience: - I've understood clearly that is not true that ALL iterations must be short. It all depends on the experience, of the team, client, complexity and size of the project. And whatever you do, don't pipeline your work! It will be so much worse;
- Just because you may not need project managers, it doesn't mean you don't need project management! Make sure you keep performing those tasks, especially the ones related with radiating information to the stakeholders;
- Learned how important is to break things small enough, both at story and task level. If you don't, you may be led to think that your iterations are too short, which will make you increase the size of the iteration and consequently, to aggravate your problem;
- Learned that I need a solid Product Owner: Empowered, available and committed, aligned with the stakeholders. Anything less than that will put you into trouble. And never, but never try to replace your Product Owner by yourself, as you may end up making the wrong calls. this will led to lack of trust from the PO and the stakeholders;
- Learned how really important is to keep consistent with the type of unit that you use in your estimates. If the team is estimating in ideal days, make sure you have their availability reflected in Ideal days. The same applies for calendar days. Mix them and you'll get into trouble very quickly (delays).
Attachments:
