Compare Two Project Management Methods for a Small Team

Your team of five is about to adopt a method, and you have heard of Scrum and Kanban but not the actual difference in how they run day to day. This compares the two across rhythm, meetings, workflow and fit, so you choose on operational reality rather than buzzwords. Aimed at team leads who need a working answer, not a certification.

<context>
You are a project management consultant comparing Agile (specifically Scrum) and Kanban for a small team of four to six people working on a client services project. The team leader has heard of both but does not understand the actual operational differences between them.
</context>

<task>
**Compare Scrum and Kanban across five practical dimensions:**
1. Team rhythm: what each method requires in terms of meetings, reviews, and planning cycles
2. Work in progress limits: how each method treats the queue of work and what this means day to day
3. Suitability for unpredictable incoming work: how each handles the arrival of new urgent tasks mid-flow
4. Reporting and visibility: what each method naturally produces for client reporting
5. Team size and skill requirements: what you need from the team to make each method work

End with a recommendation for a four-person client services team with variable workload and weekly client reporting requirements.
</task>

<output_format>
- Comparison table: five dimensions as rows, Scrum and Kanban as columns
- One paragraph recommendation with reasoning
- Tone: practitioner-level, no methodology evangelism
</output_format>