What Happens When Waterfall on Agile (Scrum)?

Article written by Sreenivas Mothukuru
1)      Ignore tools and look for reasons:
Instead of using / appreciating the features which specialized tools provide teams start overlooking the tools and complain about the features.
2)      Result in “over commitment” or “under commitment” or “as per the commitment”:
Due to point 1, team members pull user stories based on their gut feeling. This might result in a) over commitment b) under commitment c) as per the commitment at the end of the sprint.
3)      User stories will be de-scoped from the Sprint:
Due to point 1 & 2, teams commit for 'N' user stories and complete N - n (n = 0 to N). In every sprint pulling user stories out will gradually impact the confidence level of scrum teams and decrease team's velocity.
4)      Lose focus on Quality:
Sometimes team run after doing more ... more ... more and finally lose focus on the quality.
5)      Sudden surprise during sprint period:
User stories will creep into Sprint backlog and create sudden surprise to the team members. Any new additions during sprint work without teams concern and not managing the existing user stories will create unnecessary confusion to the team and effects team morale.
6)      Due to point 3, 4 & 5 thin line between Scrum Master, Dev and QA become a huge barrier.
7)      Agile formalities will be shelved:
Grooming will end up with actual scrum team members not involving in understanding user stories, not sizing stories. Planning will end up with a fewer user stories in sprint backlog and NO team commitment, ignore Definition of Done & Definition of Ready, Daily stand up meetings will prolong for long time (30-45 minutes), No Retrospective meeting means no scope of improvement.
8)     Due to point 4 bugs will crawl into the system and eventually create busy work for maintenance team.
9)     Instead of building quality into the system ... teams’ move towards addressing / fixing issues during warranty period.
10) Team members start Blame Game.
11) Burn down chart shows sceneries of mountains and valleys.
12) Unknowingly Scrum Master move towards micro management.
13) Eventually teams become incapable at giving proper estimates.
14) Conflict of Interest arises. People will put their own interests ahead of the interests of group / organization.
15) Team members lack authority and decision-making ability.
16) A culture that doesn't support learning evolves.
17)  Denial is embraced instead of the brutal truth.
18) In the words of W. Edwards Deming, team end up "robbing people of their pride in workmanship”.
- Feel free to add a few points (if I miss any). Also correct me if I'm wrong or compliment me if I'm right in any case :)
- Above points are written based on my assumptions (not experience).

- Mothukuru Sreenivas


Popular posts from this blog

How QA Matrix Meet Dev Metric?

Is it an ATTITUDE or qualification that matters?