Value first and #noestimates – two sides of a coin? Part 3: value focus

Value First and #NoEstimates – two s >

Recently I came across two approaches that claim to solve the problem “Always to succeed with your projects by delivering always on-time, on or under budget”: Kai Gilb’s Value first and Vasco Duarte’s #NoEstimates. As I have studied these approaches a bit deeper (I have a note on a workshop at Vasco’s at NovaTec and I attended a webinar with Kai, besides reading their respective books and other related stuff) in common but focus different areas of project work.

This small series of blog posts starts with Value First and #NoEstimates – two sides of a coin? Part 1: Value First which provided a look at the key points of Kai Gilb’s Value first. Part 2 explained Vasco Duarte’s #NoEstimates. The comparison in this final part 3 closes the blog series.

Comparison

If you have read part 1 and part 2, you might have the same feeling than me. Both approaches have a focus on different aspects of the development process. They both focus on value that the initiative has to deliver to the stakeholders. Both focus on doing that at the moment.

Value Focus: Quantified Values ​​as guiding North Star

Kai Gilb on business side by trying to quantify value and to check after delivery how far did we go. Kai aims to get the most important value at the moment. The development team aligns every decision and every action to that guiding compass. They are aiming to deliver value in every delivery cycle. Kai Gilb proposes to measure the value added at the beginning. So Kai does not only prioritize but quantify the results.

Value Focus: Lean Principle, Delivering Value and Problem Slicing

Vasco Duarte does not mention prioritization. He takes identification of the most important thing for granted, but shows a method to concentrate on value delivery without distraction by estimation. It provides an indication, if we are able to deliver the current planned scope (backlog) on ​​time (at the release milestone projected). This enables us to talk about the problem we try to solve. Vasco concentrates on Lean principle: you do not need to reach your objectives. He provides an approach to support the team in that endeavor. The Lean principle will end up being a project, if the cost of iteration is higher than the monetized business value.

Vasco Duarte thus provides a method for complexity reduction or slicing the problem. This method can be used to solve small small problems.

Conclusion

Value First is an issue that focuses on what matters. #NoEstimates helps in forecasting scope that will be in a release in an easy and reliable matter and thus focus on what matters – while developing and implementing a solution. Both approaches can go hand in hand for streamlining value discovery and value delivery.

Final advice from Kai Gilb: Decide not to plan (extensively), but start to do immediately.

This sounds familiar from Vasco’s workshop where you can find out more.

Final advice from Vasco Duarte: Always be ready to stop the project at any time.

If we combine both approaches, we can focus on value and practice continuous value delivery. Not only some vague value, but real long-term value for our customers. And that is the real secret behind the claim of both approaches, that allows them to claim they help projects always succeeds on-time and on or under budget.

What do you think? How do you solve the problem of focusing on values ​​and outcomes? What do you do to avoid shopping on a shopping list? How do you define and forecast your delivery scope in an agile development?

Related Posts

Like this post? Please share to your friends:
Christina Cherry
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: