Agile – Scrum

I am glad that I have taken up the scrum master course from Udemy. Strongly encourage you to take up this course. You can finish this within half a day watching at 1.75x speed.

I’ll breakdown the key takeaway here first. After that, I’ll write down a more detailed explanation in another post. Again, this is a blog mainly for me to jot down my thoughts and notes that I have learned. And, can use it for my future reference.

Key Takeaway:

To begin as a scrum master, we need to start by understanding the agile principle. It has been written down in Agile Manifesto as simple as these 4 points.

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

In simple terms:

  1. Deliver value Early
  2. Technical Excellence
  3. Communication
  4. Embrace Change
  5. Deliver Frequently
  6. Simplicity
  7. Done = Done
  8. Reflect On Performance
  9. Trust & Support
  10. Sustainable Pace
  11. Self Organized Teams
  12. Biz + Dev Together

One thing to note here is that Scrum is not a methodology, but a framework. What that means, is there is no step by step of how it works. A framework serves as a base, and how we approach it matters.

Scrum is not a methodology, but a framework

I have been working with quite some squads. Never really took the time to sit down and understand the Manifesto. To my amazement, these values and culture can be pass on without the need of attending any course or training. I have been adapting to it, and so does with some of the new joiners that joined after me.

Why is it so effective?

I think one of the main reasons is that we practice it every day. From daily standup and retrospective. Technically, a lot of things will is discussed during the retro, and one of those is reminding each other of the practice, behavior, and mindset of being agile.

Generally, I think Scrum is so powerful that is worth not just to explore in the scope of software development. I should also be applied to work with other industry that has a team. Is a way for the management to trust their deliverable, and at the same time keeping a close loop of the progress and what is happening at least on the strategic levels or weekly basis.