Organisations that have technical founders have a very different character to their work internally, need to make knowledge of the quality of software more pervasive – the business need to understand more about the technical side, and the developers need to understand more about the business
Code that has excessive error handling typically has other design problems – benefit in thinking about whether certain things should be treated as errors or not
Entropy happens in all systems, including code, so technical debt is not a surprise, need to make the case for hygiene, putting a dollar amount on technical debt does not add much value
Use low impact probing to determine whether code is dead
Potsel’s Law – an implementation should be conservative in its sending behaviour, and liberal in its receiving behaviour
State of quality is improving and there is more recognition to build quality in
Property based testing is becoming more prevalent as we move from object oriented to functional languages
Holacracy was designed by a software person, Sociocracy talks about applying democratic principles to governance, these are all interesting experiments
It can be hard to recognise if something is intrinsically difficult or not something you are familiar with
We weren’t really battling waterfall, it was the lack of any process at all…
Renee, Tony and Craig are at Agile Australia and sit down with Adrian Fittolani from Envato and discuss program management and monte carlo simulations. Renee also makes an estimate that is super accurate!
utilise bottom up program management at Envato, they have 4 main themes as a company and use self organising themes to meet those themes
had to evolve from co-located teams as could not find local resources, they now have any person working in any team wherever they are and make that work, they try to keep teams in close timezones and use asynchronous communication tools, have a policy to work anywhere and additionally a policy to travel and work from anywhere in the world for 3 months
the teams responsibility is to radiate program status, currently using a short document with a timeline view
launch wall for important items kicking off in the next 2 weeks – helps eliminate surprises
project is where more than one team is involved, form a circle around the project (like holacracy)
Craig and Renee, sitting in a shoe-box sized hotel room in Sydney eating peanut M&Ms, decided to rustle through the mailbag and answer a bunch of outstanding questions.
Note: this episode is not sponsored or endorsed by M&Ms but we certainly enjoy their product!
Crossing The Chasm
more and more organisations seem to be crossing the chasm to Agile, but too many are still just doing and not being Agile
inimal viable product (MVP) is still the trend word, the next stage is Minimal Viable Experience and then Minimal Viable Robustness to Minimal Marketable Product and finally Continuously Evolving Product