Velocity vs Throughput – What’s the difference?

In the context of software delivery, velocity and throughput are two performance metrics used to measure the effectiveness and efficiency of a development team. They help stakeholders and teams understand the progress and productivity of software development processes. While both metrics provide valuable insights, they have different focuses and should be used for different purposes. In order to understand velocity, you need to understand story points as well. Story Points: Velocity: Throughput: When to use Velocity vs Throughput over the other: Downsides to velocity/story points in software delivery: Overall, both approaches have their pros and cons, and teams should choose

Work In Progress Limits (WIP) In Lean + Kanban

In other news, I don’t only write about esports and crypto but I am also an expert in software delivery! Going forward, I’ll be trying to balance all three and write a bit more about software delivery. One of my passions is to delivery stuff on time, with a high amount of quality in the hands of customers. MVPs aren’t always ideal especially when you think of it from a customer lense. Anyways, we’re here to talk about limiting work and WIP limits from a software delivery standpoint. This will be introductory and introduce some benefits / challenges of WIP.