• 1: WillemVanDenEnde
• 2: Lieven Govaerts
• 3: Tom Tabruyn
• 4: SvenGorts
• 5: Joachim Meganck
• 6: PascalVanCauwenberghe
• 7: Klaas Van Schelven
• 8: Barry Evans
• 9: MarcEvers
• 10: VeraPeeters
• 13: BernardNotarianni
• 14: RaphaelPierquin
• 15: Philip Almey
• 16: NynkeFokma
• 17: Christophe Thelen
• ## : your name here
• Not on the photo: StephanEggermont
  

Barry Evans likes to think of himself as a citizen of the world with an
Irish passport, a Welsh name, a home in France and a job in England. He
has worked in Australia, America, Ireland and the UK. He has
consistently promoted common sense as a methodology in systems
development. He believes that iterative, incremental development
techniques harness this great resource. He is currently working for
British Telecom as a lead Agile consultant working to effect an
ambitious organisational change there. He is specifically interested in
the social effects of collaborative work on quality and the effect of
happiness on productivity. 

• awareness of how our way of communicating influences others and vice versa
• consciousness of the change processes in self, others and the context so that we can surf the waves of change, rather than drowning in the surf of the waves

• a systemic approach - instead of focusing only on individuals, look at the team, organisation, family as a whole system
• a focus on coping - problems themselves are not the problem, the coping is the problem
• a positive focus: you are ok!

•   Introduce the context and subject. We have slides and handouts for the participants.
•   Set ground rules for the session.

• Introduce the Self-Other-Context model by Virginia Satir, using a presentation of 5 coping stances and modeling the coping stance by presenters and participants.
• Introduce counter stances, modeled by the presenters and played out by the participants stance-per-stance.Debrief stances and counter stances. Depending on how much work-related stories come out, we may spend more time on the debrief,

• Participants experiment with different combinations of stances in small groups through role play, based on stories from actual development projects we provide.
• Debrief

• We Introduce the Temperature Reading as a tool to evaluate and get feedback about feelings and issues present in a group, and as a way to find out what works well, and what can be improved.
• Practise the Temperature Reading tool by applying it to this session. If the group is large, we split up with one facilitator per group.

• lose less time and energy due to fighting
• balance interaction between developers, management and customers
• develop a long-term trust relationship between developers, management and customers
• get your team into a state of flow, where the team delivers more value, while being more relaxed at the same time
• focus on problems - create an atmosphere where underlying problems surface themselves, so appropriate solutions can be devised.

• how to recognize certain ineffective patterns in your communication and how to cope more effectively while balancing the interests of self, the other, and the context.
• what the effect of body stances on communicating are and vice versa.
• a tool to find out and discuss what the real issues and feelings in a group are.

Movements really rise or fall on the strength of on-going social occasions - XP user group meetings, XP Days, XP and Agile conferences, and the Agile Open Conference are the epicenters of the agile movement.

The Agile Open 2006 conference was the second international unconference on agile development. Agile Open is an Open Space intended for software development and business people from all walks of life, it took place on April 27th and 28th, 2006, in Mechelen, Belgium ... an amazingly open, warm and lively community space where people spark new insights in and relationships for collaborative (software) development and doing business together.

Agile Open 2006 was fun and educational. We look forward to seeing you at Agile Open 2007!

Agile Open is an unconference - for participants, by participants: we determine the actual program together at the start of the conference. We do not expect people to invent all the sessions on the spot, so we encourage you to put your IdeasForSessions on this wiki. Any ideas for sessions you would like to experience, or hear and see happen, as well as ideas for sessions you would like to organize and facilitate are welcome. 

The conference took place in Mechelen, Belgium (near Brussels), Europe. The ConferenceLocation is Elewijt Center (same location as last year). Start and end times are listed in the Schedule.

Share ideas on this wiki and subscribe to the RSS feed to be notified of the latest news.

The previous edition of this conference was held on 29 and 30 April 2005.

News and current activities

• Pictures of the conference are online. Please add your name in the Pictures page.
• Read the IdeasForSessions and SessionOutputs
  
• Meet your ConferenceHosts
• Several people are BloggingAbout Agile Open

---

Organized by Agile Systems

Thanks to Methods & Tools, media sponsor

Thanks to the Agile Alliance for sponsoring this event!

• Investement: the money that's tied up to generate throughput (e.g. machines, raw materials...)
  
• Operational Expense: the money that has to be spent to keep the company running (wages, electricity...)
  
• Throughput: the money that comes in to  the company through sales.
  

Friday

XP Game	Unplanned session
XP Game	Throughput Accounting Metrics
Prepare for the Worst	I'm not a bottleneck! I'm a free man!

Conference structure

• OpeningSession
• Day 1 sessions
  
• Day 2 sessions
• ClosingSession

• Project level metrics aligned with company level Throughput Accounting - PascalVanCauwenberghe
• PragmaticRiskManagement - MarcEvers
  
• AutomatedAcceptanceTestingWithWatir - MarcEvers
• SurvivingNonAgileEnvironments - SvenGorts
• IncrementalConstruction - BernardNotarianni
• NextAgileOpen
• XP Game  -- (a classic) I'd love to run it again if someone is interested - VeraPeeters
• Drawing Carousel I would like to try out some new ideas in this session -- VeraPeeters
• I'm not a Bottleneck -- I'm proposing it, because I haven't had the chance to participate in it yet, I hope Pascal or Marc don't mind to run the session if it gets selected. -- VeraPeeters
• Coders Dojo -- Pascal and me have a well prepared Kata, but also a Randori is always an interesting experience   -- VeraPeeters
• Do You Get What You Measure? --  Sounds like an interesting session, I regret I wasn't at one of the previous runs -- hope someone can organise it  -- VeraPeeters , PascalVanCauwenberghe
• Continuous Integration Game -- experimental --VeraPeeters
• PresentationZen - PascalVanCauwenberghe
• Thinking for a Change -- another session that I propose because I regret so much not having been able to attend it before. And since I know the presenters will be at Agile Open, .......  -- VeraPeeters
• CongruentAction (balancing act / simple tools for feedback, courage and communication, the next generation) - WillemVanDenEnde
  
• AGoodRead - bring a book that inspired you, and we'll tear it to bits :). WillemVanDenEnde
• Agile Customer Documentation -- writer scrums, pair documenting, write doc tests before docs (Can you turn your procedures into scripts or Wizards?),  daily doc generation and sanity tests from source, group doc reviews with Engineering, Support, and Marketing...
• PrepareForTheWorst -- the benefits, but also the costs, should guide development planning. Development effort is one type of costs, but there are many more such as operation and administration, social costs, security vulnerabilities, loss of reputation and damage through incompetent use -- JohanPeeters
• Agile Internal Documentation -- documentation for internal use only: use cases, functional design documents, technical design documents, ... What is needed, what is superfluous according to Agile?
• Intellectual property rights -- who holds the intellectual property rights on software? What are the rights and duties of software developers with respect to software that they developed themselves?
  
• CRC Cards -- Class Responsibility Collaborator cards are an interesting way to learn Object Oriented thinking.
  

Artists' impression of participants selecting sessions on the first day of the 2005 conference

• The timeless way of building by Christopher Alexander (WillemVanDenEnde)
• Smalltalk, Objects and Design by Chamond Liu (BernardNotarianni)
• Refactoring to Patterns by Joshua Kerievsky (SvenGorts)
• Does  it have to be non-fiction? (VeraPeeters)
• YourBookHere

By car

The Elewijt Center is located in Zemst, to the south of Mechelen, near the E-19 highway between Brussels and Antwerp. From the highway exit, it's about 1km to the conference center. See the map for more information.

The Center has plenty of parking space next to the building.

Note for people who drive from The Netherlands: when coming from Breda or Eindhoven, you take the Ring around Antwerp and then follow the directions for Brussel/Mechelen E19. 

By train

• From Belgium: Mechelen is situated on the line Brussels-Antwerp. See the route planner.
• From The Netherlands: Mechelen is a stop on the international line from Amsterdam or Rotterdam to Brussels. See the route planner
• From the United Kingdom and France: the Eurostar brings you from London and several cities in France to "Brussels Midi/Zuid". From there, take the train to Mechelen, which departs every 5-10 minutes. See the route planner.

Add your name to the carpool list if you're offering or looking for a ride between the train station and the conference location.

By plane

You can fly into Brussels Airport from most cities in Europe and the United States. From the airport, you can take a taxi, which will bring you to the conference center in about 25 minutes.

Arrival / Departure times

Add your name and arrival / departure location+time, you might meet a travel companion to share a plane, a boat, a train, a taxi...

http://www.refactoring.be/sven/index.html]]> 84.194.167.217 25 April 2006 22:35 GMT http://www.agileopen.net/2006/SurvivingNonAgileEnvironments.html http://www.agileopen.net/2006/SurvivingNonAgileEnvironments.html So how can one deal with such a situation ? What where the things you tried ? What worked and what didn't. What would you do differently now ? In short the idea of this session is to share first hand experiences with nonagile environments.

Suggestions on how to run this session are appreciated.]]> 134.58.253.130 25 April 2006 20:54 GMT http://www.agileopen.net/2006/PrepareForTheWorst.html http://www.agileopen.net/2006/PrepareForTheWorst.html How do you deal with non-functional requirements in an agile project? User stories are a great way to keep track of the functionality to be implemented. But what about all the things that the system must ensure will never happen?

I have developed an approach to rationally plan the effort invested in preventing malicious users from abusing the system. It extends traditional value-focused planning with costs incurred as systems increase the risk of undesirable events occurring. The approach is not limited to security threats, and I would like to spend this session thinking how it can be applied to other fields such as incompetent users, or system failure due to overload.

In this session, I give a brief introduction to planning security requirements with abuser stories. This is followed by a goldfish bowl discussion on whether and how the techniques can be extended to other non-functional requirements. I am particularly interested in hearing how other people have tied non-functional requirements into a user story driven project.

Agile methodologies encourage an incremental development of applications.

Given the fact your preferred customer feeds you with priorized stories for your iterations, the agile methodologies ensure you that your iterations will finish with a managed level of project risk. However, little information is provided in literature about how to produce this flow of priorized stories for an agile team.

This workshop attempts to explore strategies to produce those stories.

The workshop will be largely interactive, calling for participants’ experience.  A collective brainstorm will be conducted using mindmaps.

Tasks

Done

Friday, April 28th