DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 963,673 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Jonathan Hall
Jonathan Hall

Posted on • Originally published at jhall.io on

Don't become complacent

I was recently introduced to the concept of Tickets don’t move left (TDML), and the question of whether this is a good practice.

It got me thinking. And I won’t go into a detailed analysis of TDML, instead I want to focus on what became my conclusion, because I think it applies to many things:

If TDML helps your team identify and fix problems, you should use it. But don’t become complacent with TDML as the new status quo.

Immediately after saying this, I realized that this advice can apply to almost anything.

β€œShould we use a kanban board?”

If a kanban board helps your team identify and fix problems, you should use it. But don’t become complacent with a kanban board as the new status quo.

β€œShould we try 1-week sprints instead of 2-week sprints?”

If a 1-week sprints help your team identify and fix problems, you should use them. But don’t become complacent with a 1-week sprint as the new status quo.

β€œShould we estimate with story points?”

If a story points help your team identify and fix problems, you should use them. But don’t become complacent with story points as the new status quo.

β€œShould we pair program?”

If a pair programming helps your team identify and fix problems, you should use them. But don’t become complacent with pair programming as the new status quo.

β€œShould we eat ice cream every afternoon?”

Yes. Yes, we should. Rocky Road, please.


If you enjoyed this message, subscribe to The Daily Commit to get future messages to your inbox.

Top comments (0)

⬇️ The only reason people scroll to the bottom...

is because they want to read more. Sign up for an account to bookmark, comment, and react to articles that interest you.