Okay, let’s talk numbers. Real ones. Actual data shows how Asia, and especially Singapore, is diving headfirst into Agile and Scrum at a remarkable pace. Adoption is rising, investment is soaring and the region is transforming faster than ever. But the real story is what these numbers reveal about the future of work in Singapore and why deep, real Agile understanding matters now more than ever.

Where in Singapore can you learn Agile and Scrum the way they were truly intended? Where can you find training that goes beyond personal opinion and is grounded in global standards, local relevance, and the authority of the organisation that created Scrum? That is exactly what Kiwii Pte. Ltd. brings to Singapore. This blog is the first in a broader series in which Scrum.org trainer Chee-Hong Hsia shares his perspective on Agile in Singapore, exploring the realities, misconceptions, and opportunities within our local landscape.

Forget all these Agile Maturity Scans which are often treated as management reports and too focussed on the mechanical side of "do these things and the maturity goes up". Change itself should be considered an empirical journey with no end state. It’s always on the move, so start with making your transformation brutally transparent.

How to Fail as an Agile Coach in Scrum by Scrum.org trainer Chee-Hong Hsia.  ​​​​​​​Helping organisations in their Agile journey sustainably while respecting the three Scrum accountabilities. A must-read if you're a dedicated Agile Coach or working with Agile Coaches in your organisation where Scrum is being adopted.

Scrum.org PST Chee-Hong Hsia is here to set the record straight. It’s actually a huge compliment when people say "You’re a Scrum purist".

So there is Scrum and there is 'an implementation of Scrum'. Why is it important to understand the difference? I hope that after reading this blog, you will realise that many Scrum conversations are actually not about Scrum, but "an implementation of Scrum" and you didn't even realise it.

Liberating Structures has increased in popularity. In this blog, Professional Scrum Trainer Chee-Hong would like to share 13 out of the 33 (more will follow) microstructures of Liberating Structures that he often use in his Scrum class to trigger bottom-up discussions. Digitalised, completely free, redesigned, and in high-definition so that you can print it in any format you desire! Have fun and happy sharing.

The Scrum Accountability Game is an interactive and fun game that you can play with others to reimagine the accountabilities in Scrum. Compatible with the new Scrum Guide 2020. Have fun! #scrumon

If Scrum were to be reduced to one purpose and one only, it would be the creation of a "Done" increment. Although the DoD serves as a crucial part of Scrum, it is also often neglected by many Scrum teams. Try out the DoD EvoCycle, a simple technique to effectively manage your Definition of Done.

If Scrum were to be reduced to one purpose and one only, it would be the creation of a "Done" increment. Although the DoD serves as a crucial part of Scrum, it is also often neglected by many Scrum teams. Try out the DoD EvoCycle, a simple technique to effectively manage your Definition of Done.

Scrum is simple to understand. The Scrum Guide is just 19 pages. Over the years, I've met many Scrum practitioners who have never read the Scrum Guide or they have read it once and once only. I believe there's something special about the Scrum Guide and because of this, it's important that we consider reading the Scrum Guide as an empirical process itself.

This is the truth. If we turn things upside down organizations can't truly embrace Agility. I would be lying if I said that we can improve our product delivery process even more. A small poem about Agility & Scrum

Ahhh... the never-ending debate. What's the value of (Scrum) certifications? Is there any value? Why should you get certified? Is it even necessary? In this blog, Chee Hong gives his opinion about the value of certifications and the reasoning behind getting certified.

Over the years, I've seen countless Scrum adaptions, and I thought perhaps it would be interesting to sum up some of the common misinterpretations. I would love to hear about the misinterpretations that you have faced, so feel free to participate in the comment section.

Just a thought on architecture in a complex environment. What is the value of a perfect architecture? Is there something as a perfect architecture? Perhaps more importantly, when is the architecture perfect?