Kanban

Let me help you avoid some bad advice I see out there about what user stories are and how they can help (or hurt) you.

Ever been on a software development project where one team is putting pressure on another because of a hidden agenda? I was, and things got interesting…

When talking about the differences between scrum (or kanban) and agile development, the motor and steering wheel of a car can be a useful analogy.

It’s always been popular to tell people how they’re “doing it wrong” and agile software development is just as easy to call “fake”.

Does it ever feel like the daily scrum meeting is really just another status meeting in disguise? Get help in this episode of healthy software developer!

In working with over 30 companies, I’ve seen 7 common agile software development fails that have little to do with whether you’re using scrum or kanban.

Planning poker might be just what your team needs – but depending on the culture it can also cause big problems.

A team that learns from software project failure produces better software – when you plan to exploit this ability.

Cross functional teams get people with different disciplines to work together better when developing software.

Embarking on the journey to let customers lead YOU to the most profitable solutions? You’ll probably need to decide between the two most popular ways agile teams work, and I’m here to help you make that decision.