The three essentials of any agile process

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

Scrum vs Continuous Deployment or why Scrum falls short for web applications

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

How to translate “business value” of things that are technically important

Agile teams often struggle with purely technical tasks. They just don't know how to translate technical necessity into business value. This makes it difficult to prioritize technical tasks against User Stories. In this article, I want to show you how to transform the hidden value of technical tasks into visible business value to ease prioritization … Continue reading How to translate “business value” of things that are technically important

How Digital Agile Management Tools Make You Blind (And How A Physical Kanban Board Can Help You See Again)

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)

Kanban: Changing story acceptance criteria whilst story is ongoing

In Scrum it's clear, a product owner can't change the acceptance criteria of a story in the current sprint without killing the sprint. Do you guys think the same principle should be applied in Kanban? I mean once a story has moved from a planning column and into an in-progress column, should the product owner … Continue reading Kanban: Changing story acceptance criteria whilst story is ongoing

[Question] How to implement Sprint Backlogs and Release cycles?

The company my team is delivering additive value to product in terms of continuous evolution there are two principles which makes me think more about release cycles. The company PO conducts Integration Testing and when it has passed they conduct User Acceptance testing. Without those procedures they are not releasing the release into production. User … Continue reading [Question] How to implement Sprint Backlogs and Release cycles?