Gone are the days when requirements were frozen at the start of a project and were not expected to change. Responding to change in a smart and effective manner is a common expectations from development teams.
Should we accept changes within a sprint? If we do, won’t it disrupt our sprint plan that is in progress? And, if we don’t, would we be less of an ‘agile’ team? Let’s explore how a mature Scrum team would respond to changing requirements.
While management’s intentions may be well placed when they sign up for an Agile transition, they often end up being a roadblock in team’s Agile journey. Here are 5 common ways traditional management thinking may compromise agility.
Two friends, Ravi and Neeraj, have both been successful IT professionals and are now in a very similar profile – Agile Coach. While their roles are same, their approaches to Agile Coaching differ. See which one makes better sense to you.
Kanban is a vaguely understood term in the IT industry – two professionals talking about kanban usually have different level of understanding. This post attempts to throw light on different kanban terms.
Kanban is a poorly understood term, and as it happens with poorly understood concepts, myths and misconceptions flourish. Here we look at the common myths around Kanban prevalent in the Agile community.
While many see Scrum and Kanban as competing process frameworks, it is common and often practical to combine them both – the result popularly called Scrumban. There is no secret recipe though. Here we explore one possible option.