This talk where held at Jfokus 2008. Those involved in software have a lot to keep in mind as they negotiate the worlds inside and outside of their code and the relationship between them. For those interested in improving the state of their art there are many (many) sources of specific recommendations they can use to sharpen their practice.
This talk takes a step back from the busy, overpopulated and often overwhelming world of such recommendations to focus on five general considerations that can inform more detailed recommendations and specific decisions.
Kevlin Henney is an independent consultant based in the UK. He specialises in programming languages, OO design, patterns, development process and software architecture, helping teams adopt techniques and improve their software development through training, mentoring and reviewing and training. He has been a columnist for various magazines and is currently a columnist for the Reg Developer channel of The Register. He is also coauthor of two recent volumes in the Pattern-Oriented Software Architecture series.
10 ways to screw up with Scrum & XP— In this talk I'll go through the most common mistakes, how to detect them, what the effect is, and how to address them. This talks assumes that you have basic knowledge of Scrum and XP.
Project anti-patterns. How to make your project fail— Why do 66% of all IT projects fail, 20% go over time and budget?! With over 20 years of IT experience, Sander Hoogendoorn talks about project anti-patterns stereotyping them as Titanic projects, Golf course projects and many more. Very enjoyable presentation.
Scrum in practice for non-believers— So why did Scrum change the way we do projects and will probably change the way you will do projects? We would like to answer this question in this session where we will share our experience in introducing the Scrum framework at Tourism Flanders seen from different viewpoints.
The Software Factory— The term software factory is controversial. But think about it... No industry has experienced more innovation than the factory industries. On the contrary, the key to meeting demand is to stop wasting talents of skilled developers on rote and menial tasks...
Evolving Agile— We are now facing critical issues which until now many within the agile community have preferred to avoid talking about. Activities such as modeling, documentation, exploratory testing, and database development must become more explicit within our methodologies. We need to find ways to fit into IT governance frameworks, process maturity frameworks, and regulatory guidelines.
