Some GYAN from the first time users of SCRUM

  • Better team work
  • Pressure with pleasure
  • Better creativity
  • Better productivity
  • Peer pressure
  • Higher degree of commitment to work

The above points are from the practitioners. As a coach of scrum methodology, I have this case to share. There was one participant, who was very tired at the beginning of the SCRUM workshop. This participant looked tired and from the looks it was clear that this person did not have proper sleep the previous day. At the end of the workshop this person was full of enthusiasm and energy. SCRUM a great energy booster!

There was another person, who was using the word ‘BUT’ very frequently and was always on the problem side. After SCRUMMing he got transformed into a possibility thinker. He was talking only of the positives and the benefits.

Another manager had this challenge of poor knowledge sharing within the team. The experts did not share their knowledge with the new comers. At the end of the SCRUM workshop he had the solution to this problem.

As a SCRUM coach, after every workshop, I am wondering why people are adopting PDCA approach for software development project, when a wonderful framework like SCRUM is available.

Any organization which is serious about creating a better workplace, should adopt SCRUM as a way of doing work and in turn SCRUM can transform the organization.

4 thoughts on “Some GYAN from the first time users of SCRUM

  1. I became involved in the Scrum community mostly through my interest in helping create healthy work environments for employees. It sounds like Scrum really has helped the teams you’ve coached and I’m glad to hear that your teammates are healthier, happier, and growing professionally.

    I’m always looking for folks to chat with about Scrum and Agile so please feel free to call or write anytime!




  2. Hi Katie,

    I started with SCRUM due to my academic interest. Got opportunities to work with some brilliant teams very closely. As I experience it more and more, I am seeing vast potential of SCRUM to create healthy work environments and in turn organizations.

    Since India is an outsourcing hub, many of the customers of the small and medium sized software organizations in India, want to allocate work, before they sleep and want to see the results when they wake up (exploiting the time lag). In these organizations, I never saw any opportunities to implement any kind of project management. Now I am just thinking ‘Why not a daily SPRINT’ – Please share your views on this




  3. Hi,

    Recently our company has decided to follow SCRUM methodology. I am working a Quality assurance analyst and I am new to SCRUM. I am unclear on the role a tester as in SCRUM. All i know is there will be no documentation , but if there is no test plan and cases, what is the level of expectation or expertise expected from a tester? Any inputs be very helpful.



    • As you rightly guessed, there are no roles in SCRUM, except Product owner (PO), Scrum Master and the team member. It is more like the present Indian cricket team. Dhoni is into the team for his wicket keeping ability and he is a batsman and captain as well. Tendulkar and Sehwag are into the team for their batting skills, and they are great fielders and bowlers as well. Yuvraj is into the team for his batting skills, and he has taken many crucial wickets. Harbajan is into the team for his bowling skills, and he has taken many vital runs as well. Like wise, in a scrum team, you qualify as a team member for your coding or testing or architecting or graphics skills, and that does not mean that you will be doing only that. A coder can do testing, if she chooses to do so. A tester can do coding, if she chooses to do so. When we say, there are no hard coded roles in scrum, what we mean is ‘you are not bound by the roles’. It is more like the brazilian foot ball. The team goes all out to score…and very often you may see the goal keeper advancing with the ball, beyond the center line…….

      The second point – Documentation

      If somebody is propagating the wrong information that in SCRUM teams, documentation is not required – it is absolute ignorance. SCRUM is for required amount of documentation, and is against unwanted documentation by the development teams. If there is a 500 page SRS, which nobody is using while coding, then SCRUM is for making it more ‘coder friendly’ by changing the format to user-stories or use-cases. SCRUM is always for enough value adding documentation, and is against any form of non-value adding software.

      If you want more info on this, catch me on skype ‘abrachan’


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s