If you’ve never been on a team that’s fully bought into Test Driven Development (TDD) and Pair Programming, then you’re missing out. These teams tend to learn much faster from each other, be more cohesive, write more modular software with fewer defects, refactor with confidence, and are generally more fun to be on.
Come experience what it’s like to work on a team that’s using XP dev practices!
You will need a laptop with wireless connectivity and a web-browser.
Open Innovation is transforming how organizations manage their innovation processes. Open innovation fundamentally challenges how organizations innovate new product development ideas by extending the pool from which ideas are drawn. This model is concerned with combining internal and external ideas, as well as internal and external paths to market, to stimulate and advance the development of new products and technologies. Consequently Open Innovation has implications for how we view ‘the customer’ in agile projects.
Ever tried to study a tune for an acoustic guitars? Or trained for a marathon? Or rehearsed a scene in a stage play? Key to success in all those disciplines is steady practice day after day.
Code Katas (jap. 形, means “form”) are a way to practice programming (BDD/TDD). A coder will solve a coding problem given by a task repeatedly in regular intervals such as every day to achieve better solutions and skills.
In this workshop we’ll do Code Katas (several tasks with several constraints will be provided). And of course we expect lots of fun during this event!
This workshop aims to share experiences on implementing, managing and leveraging agile practices in globally distributed projects. The workshop will set the scene for an edited book on practicing agile distributed software projects published by Springer in 2010 - www.springer.com/computer/swe/book/978-3-642-12441-9. The content will be based on a combination of research and industrial presentations offered by the authors of book. Participants will engage in discussions and develop an understanding of dos and don’ts through a synergy of experiences from industrial companies.
Many agile development teams deal with restricting environments which make it impossible to “done” any feature in an iteration. These restrictions originate in external regulations (laws, norms) and internal habits of an organization.
If it is not possible to remove these impediments, how are you able to get your features done? How to strengthen agile approaches in such environments?
This workshop elaborates the Definition-of-Done in regulated environments for further transition to agile development. Participants exercise tailoring their own environments for improvement.
It seems to be a common understanding that retrospectives are the major practice that enables agility. However, conducting virtual retrospectives is often not straight forward. One possibility is to conduct a retrospective at each site and then to swap the different findings afterwards. Another one is to facilitate a joint virtual retrospective using different virtual communication channels. In this workshop we will explore practices and facilitation techniques that have helped in different global projects. Moreover we’ll indicate supporting tools and how to prepare such a workshop.
Agile has shown that doing prolonged analysis upfront bears little to no value to the customer. However, doing none means the project lacks the direction that it needs. The question is, how much analysis is enough before the project starts?
Often times, the inception activities can set a project up for success or failure. In this 3-hour workshop, we aim to give an introduction of how an intensive, focused series of activities can kickstart a project. Led by a Business Analyst and a Developer, the participants will simulate a short inception that shapes a project from concept to delivery.
Yaser Ghanam,Frank Maurer,Kendra Cooper
So you deliver perfect code with no technical debt, on time and budget using Agile methods. Yet you remain unconvinced, and the resulting system is no success with users. But why? You even had an interaction designer onboard and “great UX” was part of the requirements list.
Our experienced facilitators will use examples of project failures to show how agile can mess up the best attempts at creating great experiences. Together we’ll discover why that keeps happening and what needs to be done to fix it so that your project can deliver a great experience and real business value that matters.
Most Coding Dojos follow 2 main formats: Kata and Randori. Both formats try to give as much information as possible to the audience by evolving solutions from scratch. This is great when dealing from Novice to Competent level but tends to get slightly less interesting to people at a higher level. The Kake format goes beyond competent by adding an extra challenge. It increases dynamics by putting people into a more “real” world exercise. Participants deal with unknown code bases and have to evolve from them. This clinic will present the format and initiate a real session with the attendees.