The slides used for this session are available to download from here.
Good projects make for bad software. The defining feature of a project is an end date, the defining feature of successful software is that it doesn't end. Software which is useful is used and demands change, stop changing it and you kill it. At best the concept of a 'project' is erroneously used for software development work. At worst the project metaphor leads to dead software, higher costs and missed business opportunities.
In this talk I will attempt to justify this somewhat radical view. I will examine the project model and show how it does not match software development. I will then outline an alternative to the project model and what organisations need to do to achieve it.
Allan Kelly works for Software Strategy, where he advises teams from many different companies and domains on adopting and deepening agile practices and development in general. When he's not with clients, he writes far too much. He specialises in working with software product companies and aligning products and processes with company strategy.
He is the author of 3 books: 'Xanpan - Team Centric Agile Software Development', 'Business Patterns for Software Developers' and 'Changing Software Development: Learning to be Agile', the originator of Retrospective Dialogue Sheets and a regular conference speaker. He blogs at blog.allankelly.net.