Why Agile Testing
The business case for agile testing practices: faster feedback, higher quality, reduced stabilization costs, and the shift from testing-as-gatekeeper to testing-as-embedded-quality.
The business case for agile testing practices: faster feedback, higher quality, reduced stabilization costs, and the shift from testing-as-gatekeeper to testing-as-embedded-quality.
Reframing the Scrum Sprint commitment/forecast as an expectation rather than a promise — how treating it as a learning vehicle rather than a delivery guarantee drives better continuous improvement.
Stack ranking work items in a Kanban system: when explicit priority ordering is essential vs when it creates unnecessary overhead. The case for WIP limits over rigid ranking.
Takeaways from LSSC 2012 Boston — where lean product development flow, Lean Startup, and Kanban converged in a rich mix of practitioners pushing boundaries.

Can you go straight to Kanban without doing Scrum first? David Anderson says start with what you do now. Yuval explores when each path makes sense.

ScrumBan is not a development process — it is an application of the Kanban Method for evolving a Scrum instance towards lean and flow. A practical walkthrough of ScrumBan principles, core Kanban practices applied to Scrum, and what typically emerges when teams go on this journey.