News

Agile Prague 2012

Agile Prague Conference 2011 is over, but you can already looking forward to the next year. Agile Prague Conference will be organized in September 3-4, 2012 again!

World Cafe

Agile Prague will also have an open space in World Cafe format: the unconference inside the conference!

Home » About Conference » Last Year (2011) » Program 2011 » Speakers and Talks » J. B. Rainsberger /Canada/

J. B. Rainsberger - The Economics of Agile Software Development

J. B. Rainsberger /Canada/

J. B. (Joe) Rainsberger /Canada/ helps software organizations better satisfy their customers and the businesses they support. Expert at delivering successful software, he writes, teaches and speaks about why delivering better software is important, but not enough. He helps clients improve their bottom line by coaching teams as well as leading change programs. He helps software organizations off the treadmill of over-commitment and under-delivery, addressing all aspects of software delivery including understanding the business, gelling the team and even writing great code. Learn more about how Joe will inspire your software organization at jbrains.ca, at conferences world-wide, or by writing him directly at get.started@jbrains.ca.

 

 

twitter jbrains

LinkedIn profilehttp://www.linkedin.com/in/jbrains

Author of: JUnit Recipes: Practical Methods for Programmer Testing

http://www.jbrains.ca
http://blog.thecodewhisperer.com


The Economics of Agile Software Development

Every month, someone new asks me the question, “How do I convince my manager to let me refactor?” While it’s true that a manager shouldn’t constrain the programmer’s plans to deliver high-quality code, the fact remains that some organisations allow their managers to assert this level of micro-control. In this talk I outline a set of models for justifying evolutionary design with basic economic concepts that relate directly to delivering, planning, and funding software projects. This talk will provide you with a solid argument to meet any skeptic’s rational objections to writing tests first and letting both low-level design and architecture emerge.