The conference is organised by a team of volunteers who work tirelessly to make the conference a fun, informative and interesting event.

Let's meet the team:

		Vera Peeters (Tryx) and Portia Tung (emergn) lead the organisation team so that all the work that needs to get done, gets done smoothly.
		Nicole Belilos (Nspyre) and Marc Evers (Piecemeal Growth) manage the conference program and help presenters so that we can offer high quality, well-prepared sessions that are appealing to a broad range of participants.
		Rob Westgeest (Westgeest Consultancy) and Philippe De Bruycker (Federal Public Service Foreign Affairs Belgium) manage communications so that everybody involved knows about the conference and the XP Days community keeps in touch.
		Colinda de Beer (Hoogendoorn) and Vera Peeters (Tryx) manage all the practical details of the venue so that the conference takes place in great surroundings with good food and drink.
		Rob Westgeest (Westgeest Consultancy) and Colinda de Beer (Hoogendoorn) ensure that the conference runs smoothly so that participants can concentrate on what they've come for: sharing, learning and meeting people.
		Serge Beaumont (Xebia) and Tjakko Kleinhuis (Sioux) are in charge of fun so that we have a sociable atmosphere and lots of laughs and wow! moments at the conferences.
		Olivier Costa (Aegisoft) and Pascal Van Cauwenberghe (Nayima) ensure that all the infrastructure and resources are available so that everybody involved has what they need to make this a great conference.
		With the help of Lars Vonk (Zilverline) and Gino Marckx (Xodiac)

We help our customers to deliver more valuable software! To make your software effectively support you and your business we focus on:

• a strong relationship with business and users
• a common understanding of the business goals and processes and how the software can optimally support and amplify these
• frequent deliveries of working increments of software

To make you succeed in working this way and in delivering software that really adds value, we offer you Agile coaching and training services, and we build and completely deliver end-to-end the software you and your business needs.

INXIN: Infrastructure for the Independent.

With more than 5000 members located around the globe, the Agile Alliance is driven by the values and principles of the Manifesto for Agile Software Development

We recommend agile approaches to software development because they deliver value to organizations and end users faster and with higher quality.

Media Sponsors

	Methods & Tools is a free software development magazine on Software Testing, Project Management, Programming (Java,.NET, Ruby on Rails, Ajax), UML, Agile (eXtreme Programming, Scrum, TDD), Requirements, Databases, Software Process Improvement, Tools.
	Agile Holland is an independent, not for profit organisation of Agile practitioners in the Netherlands. Its mission is to promote Agile practices and principles in order to achieve better results faster. Agile Holland frequently organises events, like evening meetups and Agile Open Holland.

• Mary Beijleveld gets ready for XP Days and describes day one and day two of the conference (in Dutch)
  
• Ralph van Roosmalen shares his impressions of the conference
• Michael Sahota describes what he learned from the Soft Skills Essentials for Software Craftsmen and the Agile Community with Strategic Play sessions
• Pascal Mestdach gives an overview of the conference
• Nick Oostvogels blogs about XP Days Benelux 2010 revisited
• Guillaume Collic describes the sessions he attended
• Luka Minudel describes the whole experience from proposing a session to attending the conference. He'll be back!
• Laurent Morisseau gives feedback on the conference and the sessions he attended

Pictures and videos

• Peter Doomen posted videos of both days
• Yves Hanoulle's pictures of Agile Community Building - Using StrategicPlay with Lego
• Yves Hanoulle posted a video of the output of the Agile Community Building - Using StrategicPlay with Lego session
• Willem van den Ende posted pictures of the conference
  

Participant feedback

• Perfection games of the sessions can be found on the Program page
• How did you find out about the conference?
• What did you like?
• How would you make the conference perfect?
• Which (new) things are you going to apply or investigate further?
• What would you like to see in a next conference?

• Energy coming out of the sessions
• Interactivity of the workshops
• Quality of the speakers
• Organisation & format
• Multitude of sessions - great choice
• Concept of publishing session on website + 30 second intro worked very well
• Open & friendly atmosphere
• Fantastic learning opportunity
• Great, inspiring, well-organised
• Smooth organisation
• Location
• Presentations
• Location
• 30 second presentations
• Atmosphere, meeting people
• Atmosphere, friendly energetic
• Program rich and full of quality sessions
• The vibrant, friendly atmosphere
• Contacts
• Level of knowledge of participants
• The atmosphere
• Choice of many topics
• The atmosphere
• The "drills" at the start of sessions
• The sessions, good content
• Enthusiasm of the people
• Trust
• Meeting interesting people
• Interaction and interactive sessions
• High energy
• I heard a lot of laughing
• Very good sessions and all different in form & content
• Open atmosphere
• Useful conversations
• High fun factor
• That I could present something :-)
• The workshops helped learning retention a lot + made linking the soft skills very concrete for me as almost always adaopted already to the agile context. Very useful for me
• It was fun!
• The convivial and supportive learning atmosphere -> a buzz
• The inspiring sessions
• The interaction
• Different presentation types:
• managers, coders, product owers
• Brain-training assistance (mindmapping), ??? assistance (backlog, stories categorising)
• Code & tech, wolfpack...
• Large variety of subjects, great organisation, nice location
• Great atmosphere
• Talking, listening, learning, coding, painting!
• All topics (Lean, Games)
• Location, food
• Great sessions and atmosphere
• Exercises in plenary
• Suprising/fresh topics: political economy, flirting...
• Books present
• Pub quiz
• Lots of enthusiastic, smart people
• Good sessions
• The open-minded people, the nice location and the good talks between the sessions
• The whole atmosphere
• The format, the content
• Great energy, Aikido exercises at the opening plenary
• Topics, atmosphere, location
• Laurrens Bonnema - good presenter, interesting topics
• Murex succes story
• The great sessions and atmosphere
• Location + sessions + facilities + energy
• Sessions with interaction of the audience
• The whole! Content, location, way it's organised,...
• Product backlog-style program with feedback cards
• The sharing of information with other people in the field
• Location!
• Variety of presenters
• Open atmosphere
• Splendid organisation
• Much energy
• Lots of sessions to choose from
• Enthusiastic people, unexpected sessions
• Diversity, openness, location, well-organised, dinner
• The energy, the new stuff
• The fact that IT-guys can be extrovert too
• Location
• Atmosphere!
• Many of the sessions
• Playing Werewolves :-)
• Setting, atmosphere, quality of sessions
• All sessions I attended
• Making new friends
• Learning from great teachers
• Flawless organisation
• Food & hotel were super!
• Diversions!
• Lots of good sessions
• Well-organised
• Atmosphere
• The mix of presentations and workshops
• The interactivity, the relaxed atmosphere
• The quality of the speakers
• The food
• The evening programme
• The opportunity to connect
• The opening sessions with the 30 sec presentations
• Energy
• Nice to meet people in an open atmosphere
• It's clear that you've thought about much (detail) so that it's easy and runs smoothly
• The gadget - timer or bell
• Session boards with cards + A4 descriptions
• Fearless change session
• Flirting session
• Atmosphere
• Agile feedback session, the Aikido exercises, the energy
• Atmosphere, energy, quality of sessions and hallway discussions
• The practical information I can use during my work
• Interactivity, atmosphere
• Fun and high quality presentations
• Pub Quiz (encourages interaction)
• BOF on "Technical writer in Agile"
• Atmosphere
• A lot of play
• Energy
• Good talks
• Open atmosphere
• Venue
• Warm-up exercises in plenary
• Friendly people and atmosphere
• Variety of sessions
• High level of interactivity
• Feedback
• Relaxed and friendly atmosphere
• The people: no only developers and coaches, but business and PO too
• 30 min breaks: to get to know new people
• 90 min sessions: to try and listen, better sessions
• 30 sec presentations: to know what to see
• The contents: cool, practical stuff
• Very good organisation
• Place/building/environment very nice
• Interesting presentations
• Many different topics very applicable to day-to-day work
• The size
• The choice of sessions
• A large number of sessions I attended
• The format of the sessions: workshop & interactive
• The fun
• The discussions between participants
• The conference never stops
• Half minute presentations
• Variety of topics
• Duo presenters
• Venue, drinks & dinner
• Agenda timeslots
• Perfection Game for session proposals
• Good content, great ambience, good pace
• The single location for conference, meals, drinks and games was nice becuase it increased interaction. It was very positive, though that can be arguable
• Almost everything
• Great group of people: energetic, creative
• Concept
• Sessions
• 30 sec presentations
• Food, venue
• Art workshop
• Cosy atmosphere
• "Different" things like exercises in plenary sessions
• The atmosphere
• Lots of interesting sessions
• Meeting people and getting to know them better
• The relaxed atmosphere
• The variety of sessions: technical, soft skills etc.
• Good sessions
• Good organisations
• Great side activities
• The zebra carpet
• The atmosphere: positive, encouraging atmosphere
• The venue
• The sessions, the contact, the workshops
• Venue, food
  
• Overall organisation
• People
• Atmosphere
• Program
• Day 2 had good sessions
• The people were really fun this year
• Great location
• Variety and quality of sessions
• Great content & contacts
• The location - great conference center
• The talks - all interesting

• examples used
• using cucumber for testing
• experience the complete test project
• hands-on session
• nice slides
• the presentation = ok
• the demonstration of exploratory testing on paper
• Discussion about exploratory testing
• good example of case
• highly relevant problem
• cucumber introduction
• the interaction
• good theoretical introduction --> costs vs feedback time
• learned feedback format for exploratory tests and the importance of it
• I liked to see/hear that testing is an important part of development life cycle
• It is very brave to have exercises in a session :-)
• Demo of Cucumber (I'm a FitNesse user :-)
• active

• regression info
• when? how? who?
• explain more about why test: "testing is about generating info, like CSI (the tv series)"
• Make the exercise in Ruby more clear --> we lost a lot of time
• learn how to use test specification in a big system with a small cost
• a bit more information about Cucumber
• being thrown into Rails was a bit dazzling
• skip technical implementation part or else explain the environment/language
• I haven't really seen how testing is involved in agile environment
• limit the scope of the session or make the session longer so that you can go deeper in detail
• clear sheet

• It might help if the room limits were "imposed" to avoid overcrowding
• Time between dinner and last session of day 1 was too long
• Not so much time between last presentation and dinner
• Add an open space at the end
• Have coffee even at 17h
• Sleeping at Tulip sucks!
• Have more time for BoFs/Open Space to accomodate spin-offs; ligh the fire if there's a spark somewhere
• Keep it like this
• More Open spaces
• More technically, skills oriented (Software Craftsmanship. More balanced program
• Some session the AC was making it really cold
• Stay in this hotel instead of Tulip
• Not possible, but the choices you have to make. Ahhhh !
• I really have no idea... Keep on going!
• Provide fruit during breaks
• The rooms could have been warmer
• The glasses weren't changed in the room for the scoond session (at least on day one)
• On the first night we ended up on a table right away from everyone else so didn't help to initially meet others. We then missed the painting workshop as we didn't yet know where the rooms were (signs may have helped from reception)
• More real experience things, like pair-porgramming
• Pseudo / Game "Code"-ing like a year (or 2) ago with Haskell functional programming "game" and presentation: puzzle pieces represented data or an operations. Focus on underlying idea, not syntax
• Somehow I often had the impression I don't really know what a session is going to be about from the abstracts
• Less Aikido
• The ability to clone myself so I can attend multiple sessions at the same time
• Provide soda, cola and juice. The climate was hot, people
• Plenary presentation by better presenters
• Keep it this way, it's great!
• Run some open space on a third day
• Last session of the day: everybody tired. Make it shorter, start earlier on the last day
• No tech session in the last slot
• Fruits and juices in the hall
• Hard to say. A clock in the hall?
• Leave time for a BoF as opposed to running them in parallel with the sessions. Also known as "open space conference". A mix of both would be good
• It was so good I have no suggestions
• Drop the "you got to have a card to follow a session" rule. In 2 sessions I've been in people have had to go because someone - who was too late - had a session card and "claimed" his seat. This doesn't feel right
• (Some) presenters should improve their presentation skills
• It's more and more difficult to come up with improvements
• Somewhat less participatns would make the sessions a little smoother - 40 people in a room of 25 feels a little crowded
• Put a base of attendees online, searchable by country, industry... like at the Amsterdam Scrum Gathering
• More games and tools
• Actually, I think it's already perfect
• A shorter break between end of sessions and dinner. Finish earlier on Friday
• Communicate the hotel checkout times more clearly
• Offer actual BoF slots (only BoFs)
• Better walls in conference rooms. You couldn't tape anything into walls and the magnet system was too high up
• Choose bigger conference rooms. I was in 4 sessions where the room was too small
• Make the Aikido optional and not part of the opening sessions
• Add the room on the Kanban cards
• More Aikido exercises: 10 minutes instead of 5
• Ever more coaches
• Less ceremony at end of day
• Have all the presentations/videos downloadable from XP Days website, including links to tools/trainings
• Video taping of sessions
• Don't put the interesting sessions together :-)
• It already is ;-)
• More workshop and interactive stuff in the morning as well. Now all the interesting stuff was in the afternoon. Also longer slots for workshops if they require it
• Location of the cards
• Some sessions too crowded
• More advanced sessions
• Looks already greta! Don't know how to make it better
• Keep people in the same place
• Sessions tend to be too theoretical so I would suggest to organise a role game in the 3 first hours faking a work situation with a team (fake company, fake short mission). And then all the sessions would refer to the morning session
• Something else to drink than coffee and tea
• It is already perfect :-)
• Make webcasts about sessions
• Put a big clock somewhere on a wall
• Video of sessions
• Resolve payment issue with Jagershorst hotel upfront
• Don't change anything. Maybe make the Yoga thing optional
• Limited number of people in a room
• Room names on Kanban cards
• Opening explains Kanban system and perfection game
• It already is! (except the carpet, it makes me dizzy)
• More rooms at the venue so that everyone can stay in one place
• Drop the yoga
• Some program slots had lots of interesting session at the same time, (first & last sessions). Friday 2nd session in the morning seemed less "high quality"
• Organise it in the summer outside
• More games
• Make it more FUN
• More accessible location
• Better balance technical subjects - organisation subjects
• Water & fruit juice in the lunch (there was only coffee and tea)
• A few more innovative and/or controversial sessions
• Session feedback per session, not at random
• Floor plan of the location of the rooms in the conference package, so we don't have to look at the sime time to the small maps on the wall. Alternative: give the rooms a number
• Add a bell for the presenters in each room: almost everybody brought one, so it would make sense to have one as part of the room setup
• An indication of the level of the session: beginner / middle / advanced
• To be at the conference hotel! Would have loved to rest and go back to the dinner, but couldn't
• More things to get people to mix together. Get strangers to talk + share experience
• There is the danger that XP Days will become something for Agile "experts" only. Maybe add more "beginners" sessions or organise an "XP Day for dummies" (no copyright :-)) or something
• For sessions with a participant limit, also limit the number of Kanban cards. Now there were people with a card, but couldn't attend because the session was full.

• Myself being present
• Some more about testing (like Fitnesse, Cucumber)
• More on core Agile
• Something on OOP and OOD - perhaps I will propose it!
• An introduction into Satir
• More open spaces
• More technically, skills oriented (Software Craftsmanship). More balanced
• Kata from the hat
• More of this, since there were a lot of session I found very interesting but couldn't attend
• More of the same
• More people of my profile (training managers) to share experience
• More XP things. A lot of sessions are about Scrum and not XP
• Improvisation (again), because I couldn't attend
• More on philosophy
• People theory
• A good keynote, like John Seddon did at Lean&Kanban in Antwerp
• How does Agile/Scrum scale in bigger companies?
• More on Lean techniques you can apply right after the conference
• Even more personality building sessions
• Concrete link with coding
• A lean success story
• More of the same, since there are a lot of sessions I missed
• The same great mix
• Popularity poll (result sholdn't be made public up front) of the sessions in order to give everyone the opportunity to follow the sessions they want. That means taking into account the number of participants & concurrency in the sessions
• Just continue!
• Sessions repeated, so that parallel session can be followed (too much choices to be taken)
• More interactive sessions, more opportunities to share with others in a systematic way (open space?)
• More 'famous' Scum/Agile people (like Mike Cohn, Jeff Sutherland)
• Recognition of dev role (rather than product owner / coach / project manager)
• Something on agile contracts. Have to think about this
• Working with lots of team & even more applications, release management
• Three hour slots for workshops
• More traditional "technical" workshops. I do like games but there seems to be less and less sessions with real software
• Make it cheaper
• All kinds of "soft skills" sessions. I love them!
• Sessions I didn't see: frog factory, Lean vs Complexity
• A lot of enthusiastic agilists
• More workshops - pooling of knowledge for experts vs presentation
• Some interdisciplinary cooperation. I.e. Invite psychologist, sociologist, social complexity scientist
• A track for product owners
• Excercises, practical session like this year
• More real business cases where the techniques have been applied. Talk about cases where it worked and where it did not work and why? Reality is always different and that is the most interesting lesson!
• New emerging techniques
• More on Lean, ToC, maybe a pecha-kucha, a fishbowl
• More workshops and more depth in them. Though most non-workshop presentations are very good
• More in-depth experience reports on Agile implementations
• Practical: how did we do this? How do we do things now?
• More of the same!
• Everyone with the same energy
• A bit more C#/.net during the sessions
• Domain specific lanaguages talk: feedback, example
• C/C++ subjects, psychology and software engineering
• A few more innovative and/or controversial sessions
• More of the same

Detailed perfection games are available on the Program page]]> Pascal.Van.Cauwenberghe 28 November 2010 17:52 GMT http://www.xpday.net/Xpday2010/feedback/Try%20new%20things.html http://www.xpday.net/Xpday2010/feedback/Try%20new%20things.html Which (new) things are you going to apply or investigate further?

• Retrospectives
• Giving feedback
• Try difference techniques in retros
• Ask for bigger goal behind user stories: understanding prioritisation of main goals will help to put more detailed stories into order
• Mindmapping
• Flirting with stakeholders
• Other retrospectives
• Improvise
• Focus on the left side of the manifesto
• System Dynamics diagrams from Dave and Marc's session
• Psych tools from Pierluigi
• The values underneath
• Diagram of Effects
• Story mapping
• TCI
• Fitnesse
• Retrospective cookbook
• Storytelling & architecture
• Systems thinking
• Flirting with stakeholders
• Solution-based thinking
• Lean architecture
• Systems thinking
• Think & be more Agile (more on the left)
• Soft skills
• A lot! Almost from every session 1 thing at least
• I'm going to teach my 5 year old daughter how to draw mindmaps (and also see how we can use the tool in pedagogical material to help people retain training).
• Will try the value stream mapping with our team processes
• Will definitely try to notice my soft skills giving feedback + correcting my language and behaviour to ensure it's always congruent
• Better testing -> clean test
• Story mapping
• Mindmapping
• Backlog management techniques (user stories, Kano thingy)
• Complexity vs Lean
• Backlog prioritisation
• Customer involvement
• Mindmapping
• Story mapping
• Multitasking problems
• Look at my role as company owner and lessen the automatic authority I get
• Mindmapping
• Solution-focussed coaching
• Value streams
• Business Value modeling
• Innovation Games
• Story mapping
• Story mapping
• Devops
• Business Value
• Fairytales
• Mindmapping
• Ideas behind problem-driven development
• Power! (Political Economy)
• Solutions thinking (Agile feedback)
• Political economy
• Diagram of effects
• Value stream mapping
• Mindmapping
• Thinking about the forces that shape your software
• Nearly everything I heard! (though this might be a "little" too optimistic...)
• Feedback skills
• BA Be (more) Agile
• Value stream mapping
• TCI
• Concentrating on the individuals in the team
• The feedback thingy
• Story mapping
• Value stream mapping
• Prioritising backlog based on ???
• Estimation with "round trips"
• Remove waste only if it helps you approach your goal
• Things from coding dojo
• Problem-driven development
• Flirting with stakeholders
• Fearless change
• Story mapping
• Value stream mapping
• Flirting with stakeholders
• Political economy
• Story mapping
• Observing soft skills / psychology at work -> Investigate how to respond differently
• Diagram of effects
• Some new ideas for retrospectives
• Retrospectives
• Agile manifesto
• Story mapping
• Value stream mapping
• Organising coding dojos, use them for teaching
• I'm going to flirt more with my stakeholders
• Many, many small things
• Flirting - be aware how to make contact with others
• Change processes, how people have their role in it
• Flirting
• Story mapping
• Feedback
• Design of error correcting process (Regis Medina)
• Flirting with my stakeholders
• Mindmapping
• Fearless change
• Systems thinking
• Read books!
• Kanban
• Open-closed principle
• Flirting
• More aware of how I communicate
• Apply some more Agile techniques
• Regular feedback
• Thinking about status implied in my responses
• More reflection on aware use of power
• Diagram of Effects
• Effective way to give/accept feedback
• Behavioral patterns to deal with problems
• More things that I can't remember now
• Soft skills
• Mindmapping
• Problem mapping
• Flirting with stakeholders
• Business Values
• Planning
• Retrospectives
• Business value
• Retrospective
• Value stream mapping
• Pomodoro technique and other stuff I heard during the sessions
• The open-closed principle
• Value stream mapping
• Parts of "My buddy is over the ocean"
• Story mapping
• Strategic play with Lega
• Retrospective techniques
• Flirting with stakeholders
• Lars Vonk's material on clean unit tests definitely
• Story mapping will be useful and I can imagine using it soon
• Retrospectives also definitely
• Open-closed principle
• Clean unit tests
• Cucumber?
• Story mapping
• Christopher Alexander's book
• Objective C and iDevice programming
• Mindmapping and several techniques I found out about communicating
• TDD
• Quality Software Management books
• Mindmapping
• IFs are evil
• Frog factory game
• The "Power" techniques
• The interpersonal sessions in practice (Portia/Jenni & Jenni)
• Mindmapping (missed the session)
• Problem-oriented programming
• Problem-driven development with Lean
• Lean techniques for architecture (and others)
• Value stream mapping in my organisation
• In Pomodoro: tracking interruptions & giving colleagues a means to know if I am currently available
• More visualisation and "??ology"
• A lot of things
• Lean

• Some site with a list of Agile events
• Lean & Kanban conference (Pascal Van Cauwenberghe)
• From colleagues who attended last year and Portia Tung
• Xebia
• Long-timer
• I started it :-)
• I just know
• Twitter
• Invited by Nicole Belilos
• Earlier attendance
• Agile Holland
• Mailing list
• Through our agile coach
• Colleagues at work
• From Marc Evers during TDD course
• It's my 8th conference
• Regular visitor for about 4 years
• Some mailing list
• From Xebia colleagues
• A colleague told me to check the webpage
• Presented two years ago
• Call for presentations, sent by a colleague
• I got your email
• Can't remember... Probably NLScrum
• Heard about it from others
• Friend
• Web site
• Agile community, but don't remember the medium
• From colleagues
• XP Days mailing list
• Can't remember
• Mailing list NLScrum / Agile Holland
• Web, colleagues
• It's my 4th one
• Colleagues at Seek You Too
• email / internet / previous editions
• Via NLScrum
• On the web?
• Have been here a few times already
• Someone told me
• Marc Evers asked me to propose a session
• Website
• I'm a "Bram" persona, coming for years
• Marc Evers
• Via colleagues
• Bloody consultants
• Colleague recommended it
• Colleague
• Friend / organiser
• Friends from Italian Agile commuity: Matteo Vaccari, Antonio Carpentieri. Your website
• The best conference that I attend and that I'm waiting for
• Colleagues of mine
• From a software developer colleague
• From last year
• I participated in the past 2 years
• Already proposed a session before. Friends
• Mailing, Pascal Van Cauwenberghe
• Googled for Agile related conferences and events
• Email
• Other people - previous attendees
• Euh... organising it?
• I'm a regular visitor
• Colinda told me
• I've been here 2 years ago
• My speaking partner
• Already participated last year
• Pascal Van Cauwenberghe
• At the previous XP Days?
• From other participants
• Word of mouth

• Well prepared, easy example allowed focus on the topic (coding is fun) (tried something like this myself once with a complex example, which did not work at all)
• Good concept
• They were good sports about doing what people wrote on the slips of paper
• This session is to programming what "waiting for godot" is for the theatre, funny and magic
• Very funny, good laugh
• Pair programming can be fun
• It was fun
• Philosophy for developers
• Te courage to sit down and let it all happen
• Fun & code & fun
• It was fun
• Good fun, lots of code

To improve

• Heal the chicken's eye
• A little more structure after the dojo when reflecting what happened
• Less coding, more philosophy
• Would make it more interactive
• More interaction with the public
• Keep it short(er) e.g. 60 min
• Wear 2 clown's nose
• Involve session attendees as programmers instead of having them just wait
• Reserve more time for the discussion
• Ask people for rules driving the session. Now, it was not interactive at all
• Add a learning element
• Explain the setup a bit more upfront
• A bit more interaction with the audience

• Nice examples
• Gets you thinking
• Form and content
• The voting was provoking good things
• Openness, interaction
• Engaging & nice interaction with participants
• Practical information
• Practical experience
• The game

To improve

• Connection to theory
• Reflect more and compare with values of agile
• When asking to choose an option, also provide an open choice, “not listed”
• Not too much... I think that the material is pretty good
• Have Arnaud

• The meat metaphor
• The fact that you included some tools to show us
• the presentation itself
• especially the first paart went very fluent
• Good questioning
• Nice slides
• lots of namees/tools... mentioned
• good slides
• parallel with dev (eg the tests)
• good presentation
• a bit technical towards the end
• the story with BBQ :-)
• overview of the tooling --> makes devops possible
• a lot of meat! and ideas!
• new insights on what devops is
• survey of available tools/approach
• Gives a good view in development and ideas of quality improvement of deployment
• Pragmatic, useful, necessary, experience based, a natural next step in CM

• less slides, but more to-the-point
• have a clear message. I could not make chocolate from it
• stay on-topic even if questions distract you
• I would like a real example of a recipie
• make it a bit more concrete
• clear examples
• maybe a bit attention for devs, I thougth there was too much attention for apps
• too "advanced" for participants with only dev experienci. A general, easy intro/overview would have been nice. Or usr more business language
• present a little "stronger"
• try to make Microsoft minded people to leave the sessin with a good feeling. it's hard, I know.
• timing
• How to do it on a microsoft environment: an example, .net conv/ powershell
• time frame
• spend less time on first story
• less insist on BBQ metaphore
• Allow time for discussion on how to concretely get devs and ops to talk together
• give pointers to books/mailinglists/conferences
• Repeat it in as many venues as possible
• Summary of a couple of best practices

• Practical approach to gaining the benefits of agile thinking when building an SOA environment
• Nice to see how SOA and Agile fit together
• SOA + Agile = LOVE
• Video about common vocabulary!
• The handout!
• Nice drawing of SOA cycle at end of presentation!
• Interactive, open
• Presentation style
• Wonderful insights -> provocative
• Discussion and reflection

To improve

• The discussions generated by the presentation require more time
• Not as technical as I expected
• More practical case studies (like Facebook, opensocial)
• Explain what is ment with "Services" as part of SOA
• What is the difference between Agile and SOA?
• Stick to your plan to do questions & discussion at the end!
• More depth in the story
• Do more presentations. Didn't go smooth, but the content was good. That's what matters in the end.

• Energetic, well-facilitated
• I still thrill! My hairs stand up
• The whole session was improvised so it showed by example that it's OK to put yourself in danger - I learned a lot. Thank you
• Practical experience
• Learned a lot about improvisation and how I react to it, how it makes me feel
• Moving around, playing, laughing
• Presenters always ready to step in at the right time
• Very funny. Very different
• Good energy for last session of the conference
• Everything: constant animation, plays
• Doing, everyone participated and tried very well
• Open, stimulating, presenters and attendees :-)
• Nice to improvise without fear to do it "wrong"
• Love the presenters
• Fun
• Instrucutive
• Spontaneous
• Wonderful how you were able to create safe environment
• Interaction, improvisation
• Never thought I could do it, but it is very funny :-)
• The idea of supporting each other and not trying to be funny
• Very energising
• Exercises
• The energy in it
• Switching off my mind
• Everything
• Everything
• The game
• The team interaction

To improve

• A small break in the middle
• Try another title that people do not fear (I was afraid of coming)
• Feedback about pimping could be given more delicately - it made me feel uncomfortable. I think it was good to raise the point to show what pimping "could be" but the assumption that it was done to transfer the improvisation made the moment negative rather than a learning moment for everyone
• Maybe one example before every exercise
• Hand out a list of "exercises" to play back home
• Longer :-)
• Finish with a few hands-on tips to use this while coaching
• Correlate the findings in the working life
• Place it on first day. Would be greta way to get to know people and maybe could try the things in the conference
• More theory to take back home
• Make it longer!
• Especially for the wheel, it's not really clear what to do. So be a bit clearer about it

• Good overview
• Lots of info
• Dynamism
• Simple but effective exercise
• It was very good to mention upfront that there will be handouts. That made me "enjoy" the overview and know I'll look at the details later
• Great interactive, didn't feel unnatural
• Good games
• You presented as a perfect pair
• You involved the audience
• You put a lot of valuable info in the session
• Speed -> lots of info -> need reflection
• Limited time
• Different techniques
• Looking from different views
• Basic introduction to several tools: starting point for looking at these in detail
• Lots of techniques, overview
• Very good presenters
• Dynamic
• Lots of info
• Enthusiastic presenters
• Good to stress the mix of perspectives
  
• Objectivity
• A lot of different ways and views
• Very dynamic. I liked the last overview of strategies, figures and workshop examples + handouts
• Gives a quick glance of opportunities & views on the backlog

To improve

• More time, less speed (less exercises, some more depth)
• Use the real Superman sign
• There wasn't enough time for really elaborating enough on the content. Presentation was rushed
• Slow down and dig deeper
• Company point of view: too fast
• Hand out play rules for games for all exercises
• Provide your presentation somewhere online
• Connect to IT problems
• More time to do exercises
• Need more time to practice
• More time?
• Smaller backlog
• A bit more in depth on the business perspective, the assignment there was not so clear
• More details for some specific views/methods
• More... time. But then again, maybe not. The goal is a glance, I believe...
  

• Contains interesting stuff
• Real life examples
• Remove wasqte only if it helps you reach the goal
• Focus on problems
• Some inspiration
• Good overview

To improve

• Less chaotic
• Keep one example, do not mix: it's confusing
• Add interaction
• Increase the size of the slides
• Remove French from the slides
• Make it interactive
• More interaction
• Less is more
• Little time spending on agenda + introduction

• A real life example I recognised and solved in a similar way
• A real tech session
• I was interesting to see the different steps that you have taken to improve the DB change maagement
• Nice presentation and topic about a problem lots of devops are encountering. Will definitely have a look at RoundhousE
• Clear presentation, heard for the first time about RoundhousE which can be useful for the projects I work on
• Interaction between presenters
• Demo
• Practical examples
• Good topic
• Well presented

To improve

• Shorten the session
• Have the audience interact more
• A bit more theory
• What if the customers decouple the DB version and app version? E.g. user updates DB without updating the app communicating with it?
• Shorter: 30 mins