Developing Business Value



I was listening to this on the way in to work recently, and it seemed to talk about lots of things that have been floating around my mind recently.


Some highlights:

07:57 - Continuous feedback
08:27 - The default is continuous, he compares his stance to an SOA person who see's the contract as set in stone
09:32 - The end of business requirements being flung over the fence, a more learning approach, what ideas should we try next?
10:12 - As devs we love micro-benchmarks, but aren't so enthused by AB testing, or I changed a button colour now we make more money
10:39 - We're not just writing it to be fast and fun but to also support a business
10:55 - Devs and the business are treated like islands, We want to break that. ideas can come from anywhere.
12:08 - Fast feedback cycle means, devs are more interested in business side, we can see the stats change.
13:32 - Fred George, broad business metrics, do what you like but improve these metrics
17:15 - Optimise for cycle time, cross discipline teams and slack
18:06 - Should we organise by activity or some domain outcome, Martin Fowler prefers the later.
beyond - deployable systems


I like the idea of more cross functional teams. I'm also quite intrigued by the, "here's the business metrics we need to improve off you go" ~ Fred George.

What are the business metrics that are important to your team and are they on your monitor? 

for example a team building a payments system could have number of transactions on a monitor, but maybe revenue would be a better figure?

 


blog comments powered by Disqus

Search

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2013