Jesper Boeg, TweetTrifork Software Pilot
Biography: Jesper Boeg
Jesper has worked as Agile Coach and Consultant for the past 5 years and is now in charge of Trifork’s department for “Agile Excellence”. He has a Masters degree from Aalborg University in the area of Information Systems and wrote his thesis on how to successfully manage distributed software teams.
Jesper helps teams and organizations adopt Agile and Lean practices with a relentless focus on flow and the creation of highly motivated teams. He believes that measuring the wrong things and lack of communication are the roots to all evil, and trust can only be established through transparency in the entire organization. Jesper’s work is guided by Lean principles and the believe that to achieve success one must look at the entire value stream to establishment flow and continuous improvement.
It is Jesper’s experience that specific Agile Best Practices rule sets are enforced in many organizations, which is unhealthy in terms of continuous improvement and counter to the values of Agile. Ultimately restricting teams from using the resources at hand effectively and adapt to the context they are faced with.
Presentation: Tweet"Deliver early and often - there is no excuse!"
In terms of delivering early and often the situation for many large and complex projects is troubling at best. While each iteration might end up with a release to a test environment the software does not reach production. In some cases it might take more than a year before the system finally hits real users using the software to solve real problems. Excuses are many: Contract, Legal, Hardware or simply the idea that an enormous amount of functionality is needed to establish a minimal marketable feature set. But do we truly understand the consequences of this and the economic aspect of having to wait more than 12 month before our system generates actual business value and real feedback? Have we made it clear to our customers and do we really believe in it ourselves? Are our excuses valid or a result of fear, distrust, sub optimization or hidden agendas?
While early and often delivery is almost taken for granted in Agile software development these days. Reality is that many teams are still a long way from releasing code to production! In this session Jesper will take a look at the reasons behind late Agile delivery and share some real life experiences dealing with both successful and unsuccessful attempts to try to change the situation. We will take a look at some of the techniques that proved helpful in changing the situation and what did not work, and dive into some of the theory behind Agile development to help us better understand the true consequences of ignoring these basic principles.