When the last time you asked yourself: “what is the benefit of feature X or module X that I’m currently developing?” or “what the end user will gain from this?”
From time to time, you may find yourself been asked those questions by friends, colleagues or even family. But why is this situation taking place at all? What we missed during our process? – meaning that, if I’m not the only person that is currently working on this project. So, how it can be that all project members missed it out?
Let’s dive into the Why, there’re several failure points that make it happens:
· Product manager – In some cases, product manager may insert a requirement that is forecasting business trends or specific into user while most of the users just won’t use this.
· Long process – On this case, the process is too long that all team missed the feature during weekly or review meetings – something like “blind spot” or even “group thinking”.
· No tracking – on the 3rd case, the sprint are not mature & no “real” process has been made, such as: planning.
In any case, R&D is developing a non-relevant feature –”Waste”.
So, how we could prevent such waste? -Well, since scrum is part of agile we should be more agile in all senses. Meaning, every one of us can be raising the red flag: Product owner, scrum master, team leader & members. It can be during internal or external planning meeting, during dailies/retro. As long as we, thinking out of the box to prevent such waste.
If such waste occurred, at least we will try to minimize the ROI.
In the next blog, I’d like to speak on “initiate”.