When inflexible and wasteful software development processes are making your organization inefficient, it's time to introduce an agile methodology. Kanban vs Scrum then becomes an essential question: Which agile software development methodology is better suited for my own situation? And is Kanban agile? What about Scrum vs agile? Confusion is spreading... Let's have a look … Continue reading Kanban vs Scrum vs Agile
This is a story about merging two teams. One was using a physical Kanban board and the other was using an electronic one. Of course we were discussing the pros and cons of electronic versus physical boards. My role in the discussion was pretty funny: I used to be a very strong fan of physical … Continue reading Kanban Boards: Physical or Electronic?
Imagine you’re driving your car through uncharted territory to a destination only vaguely described by "That Guy" who told you to go there. "That Guy" was kind enough to give you an absolutely non-negotiable deadline too. With that in mind, you race to the first waypoint - you should already be able to see it … Continue reading Why projects fail and how to make them succeed with more transparency
This is a guest post by Boris Gloger (@borisgloger) A couple of days ago I commented on Matthias' post about the myth that Scrum forces a team to release new functionality only after a sprint is finished while Kanban would is more flexible. I wanted to know the difference between Scrum and Kanban, and why … Continue reading Scrum or Kanban – It does not matter
In the heat of introducing agile practices like daily stand-up meetings, retrospectives, unit testing, or defining "Done", you can get easily overwhelmed by all the new and shiny ideas. It's a real danger that implementing these new practices creates huge overheads, slows you down, and frustrates the team. They forget why you actually introduced agile … Continue reading The three essentials of any agile process
Product development needs consistency The basic idea of Scrum is to create a safe and change-free environment to enable a team to concentrate on the planned development tasks. The team plans out a sprint of typically two weeks and the idea is that they work uninterrupted during this period. This process really helps to get … Continue reading Scrum vs Continuous Deployment or why Scrum falls short for web applications
We've been using PivotalTracker for years to manage our agile software development process. It works like a charm for us. Whenever an idea comes up, we enter it into Tracker as an Epic (no matter how rough and abstract it might be). When the time comes to start implementing it, we usually break it down … Continue reading How Digital Agile Management Tools Make You Blind (And How A Physical Kanban Board Can Help You See Again)