I started using Scrum from 2008 onwards. It has been an exciting and long journey. Have done my share of mistakes, learned and survived. I have been working with large enterprises as Project manager, ScrumMaster, Agil Coach roles.
I strongly believe there is no fixed rule on how to implement Scrum / Agile, rather each situation, each company is unique. We need to figure out what works and what doesn't. Again Scrum or Agile is not a silver bullett. Just because the team does standup every day, it doesn't become super performing team. Scrum helps to surface the problems. The result depends on how we approach those problems, how we react to it, how we make sure same kind of issues arent repeated.
I have extensively worked in Scrum, SAFe (Scaled Agile Framework for Enterprises), Xtreme programming techniques.
Articles I've written
What Do You Do on Your First Day as a ScrumMaster?
Doesn't matter how many times you have done it -- you are always anxious on your first day with the team as a Coach/ScrumMaster. . . .
The Daily Scrum: Common Pitfalls and Negative Patterns
Enough is written on good stand-ups (stick to the three questions, focus on accomplishments, the team owns the meeting, etc.). Here I thought I would discuss some common pitfalls and negative patterns, based on my experience. . . .
Who Is Your Product Owner?
There have been a lot of mixed views about the PO role from those who have been through a bad Agile implementation or haven't gone through a formal Agile/Scrum training. . . .
Scrum Without a ScrumMaster
Can a team function on its own, without a ScrumMaster?