The Battle of Scrum vs. Kanban
Over the past ten years, Scrum has become the leading project management approach in agile development. Now, there’s a new kid on the block-Kanban. Devotees of each approach emphasize their fundamental differences, debating pros and cons of one versus the other. Recognizing that their principles and practices are not utterly dissimilar, Jean Tabaka leads an open discussion about Scrum and Kanban approaches. For instance, both approaches create high project visibility and work in smaller increments than traditional development. And yet, each approach emphasizes its principles that influence which practices and measures guide the team and its organization. Scrum uses a Burndown Chart for visibility on progress; Kanban tracks work-in-process (WIP) as one of its tools for progress visibility. Is one better than the other? Or more importantly, when is one better than the other? Join this lively discussion on how Scrum, Kanban, or both can lead to success. After all, that is our ultimate goal.
Upcoming Events
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 08 |
AI Con USA An Intelligence-Driven Future |
Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |
Recommended Web Seminars
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |
On Demand | Agile Transformation Best Practices |