Can SCRUM save Shark projects
I just watched a movie
called Shark Exorcist (It is a real movie, someone wrote a story and spent
money on making it - http://www.imdb.com/title/tt3120314/).
I was thinking about what could have made the movie better since a team of people worked on it, they must have had hopes for it. I mean when we make
dinner, we want it to be really tasty! When we put on makeup, we want to look
pretty! So, what could have been done to make this movie better?
Answer: Obviously, Not make the movie at all.
I got to thinking - if the makers used the waterfall methodology to make this movie they may not have had a chance to look at the whole product till the very end, so they may not have known about the lameness of the movie. If
they had used SCRUM methodology in the movie making, they might have realized they
were just wasting money and might have scraped the project in its initial
stages and my 5 minutes would have been used on another terrible shark movie. (watched in Fast Forward)
I have personally never worked on a SCRUM team where a project was scraped off
because the vision was so terrible (although SCRUM implies that you can catch issues early on). Because let’s face it, if the team actively
acknowledged the vision was poor suggested
to scrape the project, their jobs would be at stake. We will have less job
security.
So, we silently groom, point, develop, code review, test, release and do tasks
without challenging the vision.
I have worked on SCRUM projects where all my team mates and I trusted each other (that takes time and bad ass
people to self align themselves), and pushed back features and changed features drastically to make the
product better or less defective. But that did not happen just by calling a methodology SCRUM. We were really a team and we were focused on the product not just what the business wanted.
For a project to be noteworthy
or successful the vision is the most important thing. So, do not get hung up on methodology or its certification (I too spent money on the certification). Because the methodology does not make a project successful on its own. It is the people and their insight into the project that makes a great product and successful project.
Comments
Post a Comment