The world of software development is constantly changing and evolving. New ideas arise all the time and existing ideas go in and out of fashion. Software development processes find it very hard to keep up with this rapid rate of change, especially as they find themselves quickly going of fashion or becoming bloated as they bolt on more and more information. Teams find themselves struggling as they try to mix-and-match practices from various sources into a coherent way-of-working or work out where to start their improvements.
Dr. Ivar Jacobson is a father of components and component architecture, use cases, aspect-oriented software development, the Unified Modelling Language and the Rational Unified Process.
He is the principal author of six influential and best-selling books.
Ivar Jacobson is the chairman of Ivar Jacobson International which has subsidiaries in the US, UK, Korea, China, Singapore, Australia, Norway and Sweden.
Ivar Jacobson Consulting, USA, UK, Korea, China, Singapore, Australia and Sweden
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.
SOA methodolology— A major complaint in IT and business organizations is that they don't have a common basis from which to have discussions. One talks technology and the other talks financials and goals, in between lies a lot of confusion. In 2005, Capgemini contributed a business centric SOA methodology to OASIS in the hope of fostering a movement away from technical SOA towards business centric SOA, and it remains the only publicly available SOA methodology in that space. This presentation covers that methodology, how to apply it to businesses, how to use it to better understand where technology investment should be made, but most importantly to understand how the business operates and IT's role in helping the business achieve its goals.
