Some Less Controversial thoughts on Agile: Scrum -v- Kanban
So, I've had a few rants thoughts on process in the past . I'd like to revisit those with my Big Boy pants on. For one thing, during my current job search process, my experience in Agile in the past 4 years always comes up, so I thought I'd parrot here what I generally say in the interviews, on why you'd choose one versus another. If you'll allow me, I'm going to argue that both are valuable, and both should be in your organization. First, let's define our terms. When I say Scrum , I generally mean the process that arose in the early 2000's employing same-size sprints, Product Owners, Scrum Masters, and backlogs. See the wiki link for more detail. When I say Kanban , I mean the process employing same-sized units of work in a continuous delivery stream with a strong focus on Service Level Agreement (SLA) for a given team. Things I'm explicitly not discussing: XP or "Extreme Programming" Scaled Agile Framework (SAFe) Any...