Tuesday 5th April, 2016
10:30am to 12:00pm
What if we could measure the indirect costs of pain building up on a software project? What if we could measure the effects of learning curves, collaboration pain, and problems building up in the code?
We've been trying to explain the pain of Technical Debt for generations, but we've never been able to measure it. Several years ago, I stumbled into a solution for measuring the “friction” in developer experience. Visibility introduces a whole new world of possibilities.
We can identify the highest leverage improvement opportunities and steer our projects with a data-driven feedback loop.
We can breakdown the “wall of ignorance” between developers and management by defining an explicit language for managing technical risk.
We can teach the art of software development with a data-driven feedback loop and codify our knowledge into sharable decision principles.
We can revolutionize our business accounting methods to take the pain of software development into account, so the costs and risks are visible at the highest levels of the organization.
We can conquer the challenges across the software industry by working together, learning together, and sharing our knowledge with the world.
With visibility, we can start a revolution in data-driven learning.
Mastering the art of teaching developers how to learn. Creator of Idea Flow Learning Framework http://leanpub.com/ideaflow bio from Twitter
Sign in to add slides, notes or videos to this session