Leading Engineering Teams with Agile Practices

When I joined Export Japan Inc. as Team Lead, the system team was delivering features but lacked structured agile practices. Here's what changed when we introduced proper Scrum workflows.

The Challenge

Our team was building and maintaining Kyoto.travel — a high-traffic tourism platform serving international visitors. Features were shipping, but:

• Sprint planning was informal

• Retrospectives were skipped under deadline pressure

• Cross-department coordination happened ad hoc

What We Implemented

Daily Scrum with Purpose

We moved from status-update meetings to focused 15-minute standups. Each engineer answered three questions, but we added a fourth: **"What's blocking you?"** This single addition reduced silent blockers by half within two sprints.

Sprint Reviews with Stakeholders

Inviting design and content teams to sprint reviews created shared ownership. Stakeholders saw working software every two weeks instead of quarterly demos.

Monthly Retrospectives

We dedicated time to process improvement — not just project post-mortems. Small changes compounded: better task estimation, clearer acceptance criteria, fewer last-minute scope changes.

Results

Within six months:

• **Delivery predictability** improved — we hit sprint commitments 85% of the time vs. ~60% before

• **Code review turnaround** dropped from 2 days to same-day

• **Team morale** increased — engineers felt heard in retrospectives

Key Takeaway

Agile isn't about ceremonies for their own sake. It's about creating feedback loops that make teams faster and more confident. As a CSPO and CSM, I've seen this pattern work across government projects in Bangladesh and enterprise platforms in Japan.

If you're building engineering teams, start with one ceremony done well — then expand.