Knowledge base

Predictable operations for teams that ship

Operational mechanisms, prioritisation frameworks (RICE, WSJF, OKRs) and delivery practices for product managers, scrum masters and heads of operations. Each guide: 5-6 minute read, real examples, no corporate fluff.

Scrum & Agile

How do you plan a Scrum sprint that actually ships?

Good sprint planning means realistic scope against the team's real capacity, a measurable goal and dependencies cleared before day one — not a meeting where everyone commits to "what feels about right".

Read the answer

Scrum & Agile

What is the real difference between Kanban and Scrum?

Scrum ships in batches (sprints) with fixed ceremonies; Kanban ships in continuous flow with WIP limits. The same team can use one, the other, or both — it depends on how predictable demand is.

Read the answer

Planning

How do you write measurable OKRs for a product team?

An OKR has an ambitious Objective (qualitative) and 3-5 measurable Key Results (quantitative, with a clear "done" threshold). If anyone can look at it and say "hit" or "missed", it is well-written.

Read the answer

Planning

How do you handle scope creep on a real project?

Scope creep stops with one mechanism: every new request must change scope, deadline or budget — and the choice is made explicitly, in writing, before the task enters the backlog.

Read the answer

Team

How do you estimate a team's velocity correctly?

Velocity = the average story points shipped in the last 3-5 closed sprints. You do not estimate velocity in theory — you measure it. And you do not use it as a target (Goodhart's law), you use it as a planning input.

Read the answer

Planning

How do you build a Gantt with realistic dependencies?

A useful Gantt has explicit dependencies (FS/SS/FF/SF), a small number of clear milestones, and recalculates the critical path automatically when a task slips. Without that, it is just a coloured Excel calendar.

Read the answer

Tooling & migration

How do you migrate from Jira without losing the team's history?

Clean migration does 4 things in order: pull a complete copy of the data out of Jira (comments included), decide which statuses and workflows you keep, rebuild the structure in waves (a pilot project first), verify with the team, only then retire old Jira.

Read the answer

Team

How do you run a sprint retro that actually changes something?

A useful retrospective produces 2 concrete actions max, with an owner, deadline and "done" criterion — and verifies at the next retro what happened with the previous actions. Without follow-through, a retro is just therapy.

Read the answer

Planning

How do you prioritize a backlog with RICE or WSJF?

RICE = Reach × Impact × Confidence ÷ Effort, good for mass-market products. WSJF (Weighted Shortest Job First) = Cost of Delay ÷ Job Size, good for roadmaps where time matters as much as value — you use one, the other, or both depending on the kind of decisions you make.

Read the answer

Planning

What is project management and how does it work?

Project management is the discipline of planning, organising and controlling a team's work to deliver a defined outcome on time and on budget. It works through a five-phase life cycle (initiation, planning, execution, monitoring, closure) and methodologies such as Agile, Scrum, Kanban or Waterfall.

Read the answer

Tooling & migration

How do you choose project management software?

You choose project management software starting from how the team works (Scrum, Kanban, hybrid), not from the feature list. Check five criteria: methodology fit, real reporting, integrations, per-seat price at scale and adoption speed.

Read the answer

Tooling & migration

Jira vs Asana vs Monday vs ClickUp: a comparison guide

Jira is the most powerful for Agile software teams, but complex. Asana excels at coordinating non-technical work. Monday is the most visual and flexible for mixed teams. ClickUp packs the most features, at the cost of complexity. Choose by who the team is, not by the feature list.

Read the answer