"No process is best. You need to find the lesser devil."
Actually there are many. (Title fits that well to pass on ...)
1. Stand up meetings
Actually there are many. (Title fits that well to pass on ...)
1. Stand up meetings
- Doesn't work out. Those who don't want to do, will never do it. Those who will, will always.
- More wasted time. One person each day for 15 min (however I didn't see anyone of them end in 15 min) for 7 people is more than one man day. Take average case of 30 min = 2 productive days lost.
- Breaks work flow. We already have so many obstacles which breaks work flow. Why another ?
Doesn't help. I can bluff them all along. Take me down to hell, but you would never be able to prove me wrong ....... that I'm bluffing.
"Yesterday I was investigating, today I will continue, if that works, will use it tomorrow"
3. More time in meeting & documents
Stand up meeting, scrum of scrum, follow up, impediments, version one, burn down chart .... keep adding.
At first they may sound useful, but we need to solve things than endless debatable topic. Many of above said ends up in that. Mean you catch any in India for a debate on Indian cricket future over a coffee. I can guarantee that you can drink all in the world but will never be able to end the debate. Apart from that, they makes us irresponsible. Take the example of impediments, you may solve many of them, but people just don't, they just report it.
Remember each meeting take more time than meeting time. Every meeting takes at least 10 more minutes than meeting.
Those who are working on scrum can answer this better: How time you actually spend on your task out of total time you spent scrumming !?!
4. Working at one thing at a time. (Independent sprint)
There are lot full of engineer who can do multiple at same time. Most of time you will find task which can better be executed in parallel. Take this one:
You have a task to write API for logging messages; & log messages for another module. You can do better in parallel. Anything can logically be divided as independent and vise versa.
5. Hierarchy
If you haven't use it wisely, you can end up screwing things more than it offer!
Scrum Master, Business analyst, Product manager, Project manager, manager, second line manager, tech leads -- & the engineer! So much to say.
6. No coach
Adopting any process without a coach is more harmful than a soccer team without a coach. At least team knowns how to play.
7. Last but not the least ..
Takes away your freedom to choose whom to answer!
'I don't mind if you don't agree with me, One day you will"
"Yesterday I was investigating, today I will continue, if that works, will use it tomorrow"
3. More time in meeting & documents
Stand up meeting, scrum of scrum, follow up, impediments, version one, burn down chart .... keep adding.
At first they may sound useful, but we need to solve things than endless debatable topic. Many of above said ends up in that. Mean you catch any in India for a debate on Indian cricket future over a coffee. I can guarantee that you can drink all in the world but will never be able to end the debate. Apart from that, they makes us irresponsible. Take the example of impediments, you may solve many of them, but people just don't, they just report it.
Remember each meeting take more time than meeting time. Every meeting takes at least 10 more minutes than meeting.
Those who are working on scrum can answer this better: How time you actually spend on your task out of total time you spent scrumming !?!
4. Working at one thing at a time. (Independent sprint)
There are lot full of engineer who can do multiple at same time. Most of time you will find task which can better be executed in parallel. Take this one:
You have a task to write API for logging messages; & log messages for another module. You can do better in parallel. Anything can logically be divided as independent and vise versa.
5. Hierarchy
If you haven't use it wisely, you can end up screwing things more than it offer!
Scrum Master, Business analyst, Product manager, Project manager, manager, second line manager, tech leads -- & the engineer! So much to say.
6. No coach
Adopting any process without a coach is more harmful than a soccer team without a coach. At least team knowns how to play.
7. Last but not the least ..
Takes away your freedom to choose whom to answer!
'I don't mind if you don't agree with me, One day you will"
Posts
4 comments:
Its more than three. Interesting view...
Yeah ... I just didn't want to start with the worst part. Specially for those who live with it ;-)
You might enjoy my diatribe at
http://www.ProjectPro.com/letters/MethodologyMadness.htm
Very nice and interesting blog. I like it and so much thanks for sharing this nice post with us and keep posting.
Scrum Process
Post a Comment