Kanban

via Bruno Baketarić: “There’s a commonly held myth that a lack of a time-bound delivery commitment, such as a sprint demonstration, will lead to a lack of focus, laziness, and increasingly long delivery times. There is, in fact, no such evidence from more than a decade of training and coaching for a living and wish to dissuade adoption of Kanban or customers from switching.” (David J. Anderson, 2023 in ‘Discovering Kanban’, p. 108)

via Mike Bowler: I’ve noticed anecdotally that for a development team, as WIP goes down, quality goes up. I’m thinking my way through how I would visualize that and any suggestions are welcome. I can easily pull WIP numbers out of Jira (all my clients use Jira - sigh). The trick is how to measure quality. Pulling number of bugs entered into Jira can be done but absence of bugs doesn’t prove quality. SonarQube has some technical quality data but quality is more than just code.

via Mark Levison: Kent McDonald offers a Kanban Board to visualize your current understanding of the state of the product backlog.

Hot take (that may lead to some “interesting” conversations when I get back from sabbatical): Points or other detailed project estimates in software project management are a waste of time.