All software development projects have finite resources, so they require making tradeoffs and prioritizing work. There are all kinds of ways to prioritize but without an intentional process, most organizations default to WYTL (whoever yells the loudest). Cost of delay is a way to consider the impact of time on the delivery of features and provides a way to discuss the economic impact of ordering work in different ways.

What others have said they liked about this session:

• Great examples & highly relevant
• Great examples and board visuals. Not too abstract.
• Good content. It's important to understand the basics.
• Great insight into visualizing the cost of delay.
• This training is great for a range of roles on the team as they play a part in informing or deciding work for a product/portfolio.