CI Agile

💡 The quickest way to destroy a Sprint? Silent assumptions.

Most teams fall into this trap:
PO reads the requirements…
“Any question?”
😶 Silence.
And then everyone walks away assuming they understood the same thing.
Spoiler: they didn’t.

When you don’t ask → you assume.
When you assume → your estimates become guesses.
And when your estimates are guesses → the Sprint becomes chaos. 💥

Scrum solves this exactly.
Asking questions early prevents big problems later.
And here’s the fun part:
If you ask and the PO can’t answer?
🎉 That’s the BEST outcome.
Because now you can say:
👉 “Please refine this and bring it next Sprint.”

But why does this even happen?
Because some organizations still expect:
1 PO → 5 teams
Or worse…
1 PO → 8 teams 😵‍💫

No human can produce high-quality requirements for that many teams.
Poor requirements = garbage in, garbage out. 🗑️⚠️

This is why Scrum emphasizes clarity, refinement, and human interaction.
Asking isn’t optional — it’s how we solve problems before they happen. 🚀

💡 Why old-school requirement sessions fail — and how Scrum fixes it.

Traditional waterfall-style requirement study looks like this:
📺 Everyone sits in a room
📄 Requirements projected line by line
👤 The requirement owner reads…
“Any questions?”
🫠 Silence.

This silence isn’t alignment — it’s danger.
Because when teams don’t ask…
❗ They assume
❗ They estimate wrong
❗ They build on guesswork
❗ Bugs explode later

Scrum fixes this issue through its first official activity — creating space for real interaction, real questions, and real clarity. 🗣️🤝

As a team member, you must ask.
Because one good question can prevent ten bad assumptions.

And here’s the best part:
If you ask and the requirement giver can’t answer…
🎉 You’re actually the happiest person in the room.

Because now you can say confidently:
👉 “Please refine this and bring it back next Sprint.”

Early questions save future chaos.

Scrum reduces risk by reducing assumptions — one conversation at a time. 🚀

💡 Why Scrum starts with its first official activity — and why it matters so much.

Most teams still do requirements the old way:
📺 Sit in a room
📄 Stare at a projector
📊 Go through Excel line by line
👤 “Any questions?” … silence

And then we wonder why bugs explode later. 😅

Scrum fixes this exact problem.
The first official activity forces real interaction — people talking, clarifying, challenging, asking.
🗣️🤝

Because when you ask early, you eliminate assumptions.
When you eliminate assumptions, you eliminate bugs.
🔥 Bugs drop dramatically simply because the team finally understands the work the same way.

But here's the catch:
❗ If you don’t ask, you assume.
❗ If you assume, your estimates are wrong.
❗ And if your estimates are wrong, your delivery collapses.

Scrum makes the invisible visible through conversation — not documents.
Clarity beats assumptions every single time. 🚀

🔍 Ever wondered where so many software bugs actually come from?
Here’s the truth most teams overlook:

❗ 30% of all software defects come from requirement bugs.
Not coding errors.
Not bad testing.
But misunderstandings at the very beginning. 💥

And that’s why Scrum starts with its first official activity — a powerful moment of individuals and interactions.
Because when people talk early, clarify early, and align early…

⬇️ Bug counts drop
⬇️ Misunderstandings disappear
⬇️ Rework shrinks

Scrum reduces bugs not by adding process,
but by improving human conversation. 🗣️🤝

Sometimes you’re wrong simply because the requirement was wrong.
Fix the misunderstanding early → fix the product faster. 🚀

You Don’t Need to Call It Agile to Be Agile 💭”

When I started, the first thing I changed wasn’t the process — it was the mindset.
I didn’t call it Agile. I didn’t call it Scrum.

Because if you walk into Malaysia Airports and ask, “How’s your Scrum?” — they won’t know what you mean.

Just like in Japan — they don’t call it Lean; they just live it.

Same thing here.

We didn’t brand it, we did it.

That’s how “Kasi Jalan Dulu” became our mindset — action before labels.

“The ‘Jalan Dulu’ Mindset That Changes Everything 💡”

Most infrastructure projects follow waterfall — slow, heavy, complicated.

But here’s what I learned after training with CI Agile:
👉 If you can make it Agile, do it.

Because when you overplan what could’ve been simple, you waste time and potential.

That’s where the Jalan Dulu mindset kicks in.

Ask yourself: what’s the real risk?

If it’s small — Jalan Dulu.

Start small, test fast, learn faster.

That’s how innovation actually happens.

“How Real Leaders Take Risks 🚀”

Every time a new project hits my table, I ask one thing:
“Agile can or not?”

That question sparks everything — can we move incrementally instead of waiting for perfection?

Then comes the next principle: “Jalan dulu.”

It means take the calculated risk, go first, learn fast.

Because leadership isn’t about playing safe — it’s about de-risking by iterating.

Fail fast, learn faster, and by the time you go big, you’ve already tested what works.

“How We Actually Run Agile in a Real Organization 💼”

Forget buzzwords — this is how Agile actually works in MAS.

We organized by squads:
👑 Senior managers = Product Owners / Subject Matter Experts
🧭 Managers = Scrum Masters + SMEs
💻 Developers = the ex*****on team

Whenever a new project starts, we already know who can lead, who can facilitate, and who can deliver.
It’s not theory — it’s structured collaboration.

“How You Build a Real Agile Culture 💡”

You don’t build culture by declaring transformation.

You build it by training people who understand your expectations, your language, and your way of working.

That’s what we did — 38 certified Scrum Masters trained, not by accident, but by design.

We didn’t talk transformation.

We showed it.

And when people see it working, they follow. That’s how it becomes contagious.

Real talk — hearing someone with solid Agile experience say “I still learned a lot” is huge.

This testimonial hits exactly why learning Scrum the right way matters:

💡 Understanding where Scrum truly came from
💡 Seeing how Jeff Sutherland’s principles connect to real-world team dynamics
💡 Experiencing hands-on activities that make everything click

Even if you’ve been doing Agile for years, there’s always that one session that cracks open a new perspective.

And the best part?
There’s literally zero downside to learning more.
Every new insight pushes you to lead better, deliver better, and think sharper.

This is the energy we love to see — growth-minded, humble, and hungry.

Well well well.

Isn't it great if everyone could solve problem(s) effectively?

Here are some nuggets you can take-away for day to day battle.

6 ways effective leaders solve problems:

1️⃣ They don't fret on small things.
i.e. They work on problems that are worth solving.

2️⃣ They communicate the problems well, so it's understood and clarified.
i.e. They clearly work on ensuring the problems worth solving are well defined.

3️⃣ They don't entertain rumours.
i.e. They ensure the teams don't just work on pure assumptions. Things taken in should be well validated.

4️⃣ It's tricky but it's a must, they manage UP very well.
i.e. Senior stakeholders or top managements often cloud decisions through authority. A great leader who cares about solving the right problem would consider managing this well.

5️⃣ They are open to ideas.
i.e. If the chosen approach is not driving results. They are open to alternative options without blaming others on the need to do so.

6️⃣ They keep their bias in check.
i.e. Consider new perspectives whenever and wherever possible to ensure the thoughts are not limited to own bias.

𝟲 𝗪𝗮𝘆𝘀 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗦𝗼𝗹𝘃𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺𝘀
(Through the lens of Design Thinking)

In high-performance teams, it's about solving the right ones in the right way.

Not trying to be the heroes and save everything, everyone, all at once.


1/ Define the problem worth solving.
Avoid distractions. Focus where impact is highest.

2/ Clarify the root cause.
Go deeper. Ask “why” until the noise clears.

3/ Validate before acting.
Don’t let assumptions steer the team off course.

4/ Manage HiPPO dynamics.
Let data and clarity guide—not just hierarchy.

5/ Explore alternative paths.
One idea rarely fits all. Think in trees, not lines.

6/ Break bias. Seek perspective.
Better questions come from broader views.

𝗚𝗿𝗲𝗮𝘁 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗶𝘀 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹.

𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗺𝗼𝘃𝗲 𝘄𝗶𝘁𝗵 𝗰𝗮𝗿𝗲.

What’s your go-to method when facing complex problems?