How I work

Agile / Scrum

Process that serves the team, not the other way around

My Agile philosophy

Agile is a mindset, not a compliance exercise. The worst teams I've seen are the most 'Scrum-certified' - they follow the ceremonies perfectly and miss the point entirely. The goal is fast learning loops, not perfect process adherence. I adapt ceremonies to team size, maturity, and context.

Sprint setup

2-week sprints as default. Sprint goal is written before backlog items are selected - the goal drives the selection, not the other way around. Definition of Done is agreed upfront and includes: code reviewed, tests written, documentation updated, analytics event live, and deployed to staging. No DoD exceptions without explicit team agreement.

Ceremonies I keep lean

Planning: 90 min max, goal-first. Daily standup: 15 min, three questions only. Refinement: 60 min/week, async pre-reading required. Review/demo: 45 min, real users or stakeholders present when possible. Retro: 45 min, action items owned and tracked. Total ceremony overhead: ~5 hours per 2-week sprint.

Scrum Master mindset

As Scrum Master at Datachain, my focus was not on running meetings but on removing impediments. I kept a live impediment log, reviewed it daily, and measured my own performance by how fast blockers were resolved. Average blocker resolution time: under 48 hours.

Scaling across teams

At SmartNews I applied Agile processes across 5 teams simultaneously using a lightweight Scrum-of-Scrums: one cross-team sync per week where each team lead shared the top blocker and upcoming dependency. No status updates - only decisions and blockers. Team velocity increased 25% over 2 quarters.