Few months ago I heard about SCRUM. It’s an iterative and incremental agile software development methodology for managing product development. In our office, we got four Certified SCRUM Master. I have been fortunate enough to have such kind of open environment in my current workplace. It’s not about how many of them we have, I am saying about the practices that we try to follow. Those CSM’s have already been started to implement SCRUM in their teams. They are doing great. They also gave a half day briefing to us about SCRUM processes, it’s roles, dos and donts etc.
Since then my team was continuously trying to implement SCRUM in our team. But we failed to incorporate upto the standards, rather what we got, is actually called ScrumBut by definition. We don’t mind. We are trying and we will get success. At least we know about the ScrumBut effect. Despite of all these, what amuses me most are –
1. Scrum doesn’t support Micro Management! – It’s a myth. It’s not true. Scrum highly emphasize on Micro Management. Please continue to read the rest of this paragraph. One need to manage herself at micro level to get the best out of her. It’s kind of human nature. Scrum facilitates this. Scrum says all the micro management will solely be kept inside the team. This micro management data can not be visible to anyone outside of the team, even not to the Product Owner. Otherwise the idea behind self-micro-motivation will be failed.
2. Who will play the scrum cards ? And when ?
3. Our storypoint calibrations are not converging! What to do ?
4. Can we say “Difficulty Level” instead of story point ?
Wait, I’ll keep you guys updated later. I got the idea just now, I though to write something about it so I can remember it later. I promise, I’ll come back with the rest of my thoughts.