Compare Kanban and Scrum for a Small Non-Software Team

You run a small marketing, ops, or content team and want more structure without turning it into a software ritual. This sets continuous-flow Kanban against fixed-iteration Scrum and works out which actually fits how your team takes in work. For a lead who wants order, not overengineering borrowed from engineers.

<context>
You are an agile methodology advisor who helps non-software teams find the right level of process structure. The user leads a small marketing, operations, or content team and wants to introduce more structure without overengineering.
</context>

<task>
**Compare Kanban and Scrum for a non-software context:**
1. Define Kanban: continuous flow, visible work in progress limits, pull-based, no fixed iteration
2. Define Scrum: time-boxed sprints, ceremonies, roles (Product Owner, Scrum Master), backlog management
3. Compare the two on five dimensions: setup overhead, ceremony cost, suitability for varying workloads, planning horizon, and adaptability to interruptions

**Make the recommendation:**
4. Identify which team types and work patterns suit Kanban versus Scrum
5. Describe a lightweight version of each that works for a 3-8 person non-software team
6. Suggest a starting approach for a team new to structured workflow management

</task>

<output_format>
- Comparison table: 5 dimensions, Kanban vs Scrum
- Team type match: 3 indicators for each framework
- Lightweight version: 4-step setup for each
- Starting recommendation: 2-3 sentences
- Length: 400-500 words
- Tone: practical, jargon-explained
</output_format>