JavaZone 2011 - Beheading the Software Beast
For any code base there comes a time when you want to change it. But if you just steam ahead making changes that break the code and then fixing errors, a common situation is that every fix or change creates several more errors. It feels as if you have picked a fight with a beast, the Software Hydra - for every scary head you cut of, two more grows out!
Instead, come learn The Mikado Method (http://mikadomethod.wordpress.com), a systematic approach to beat the Hydra and change the code in a safe way. The method helps you visualize, prepare and perform business-value-focused changes while delivering continuously, and without having a broken code-base in the process. It enhances team communication, collaboration and learning, and helps individuals stay on track.
Ola Ellnestam
Ola Ellnestam likes to combine technology, people and business, which is why he finds software development so interesting. After coming in contact with eXtreme Programming he realized that developing software doesn't necessarily mean big and seemingly endless projects. There are flexible and fun ways to develop software too. More than anything else, he likes to share his knowledge with others because he believes that this is how new knowledge and insights are created.
Daniel Brolund
Daniel Brolund has a small working memory. He tries to compensate for his bad memory by using and spreading solid working habits, like limited work-in-progress, TDD, and automation. He is a co-creator of the Mikado Method, a process and memento for large transformations of legacy systems. The method has enabled him to actually perform such transformations, in spite of his memory shortage! If you meet him, please refresh his memory and tell him your name.
Twitter: @danielbrolund