XP Day Benelux 2011 http://www.xpday.net/ XP Days Benelux 2011 conference site en-us 29 January 2012 10:45 GMT 29 January 2012 10:45 GMT http://backend.userland.com/rss Feedback Olivier.Costa 27 January 2012 18:41 GMT http://www.xpday.net/Xpday2011/sessions/FedEx%20Days/Feedback.html http://www.xpday.net/Xpday2011/sessions/FedEx%20Days/Feedback.html
  • nice idea |||||
  • fun video and photos |||
  • subject
  • storytelling with pictures
  • experience sharing! ||
  • great ideas
  • nice material
  • calm presentation, answer to all questions
  • top!
  • nice experiment
  • I'd like to organise this in my company
  • good examples
  • inspiring concept
  • kanban used
  • dan pink movie is really good
  • clear talk
  • share experiences + practical tips
  • foto's van trotse mensen en andere foto's, zodat je je een beter beeld kan vormen
  • motivating
  • interesting
  • passionate
  • liked presentation style
  • movie
  • some ideas like the prize and trophy
  • that you created an open and safe atmosphere
  • want to get one of our clients to do this!
  • liked your mind map
  • visually interesting
  • made me want to do it
  • multisnesory session (stories, pictures, video)
  • didn't expect this!
  • great speaker
  • useful, well explained
  • nice ! nice video !
  • very practical
  • very motivating
  • not just theory, but real life stuff
  • good overview
  • 9,5 because there is always some room for improvement
  • you made me thinking & generating ideas
  • I want to do this
  • the idea
  • Dan Pink ?
  • good examples
  • a lot of interaction
  • well presented (clear)
  • introduction to FedEX
  • link with motivation
  • multi-media
  • geweldig concept
  • goede presentatie To make it perfect:
    • more focus on benefits
    • more interaction
    • hands-on -> give the rules and self-organise in small groups
    • integrate expectations
    • put pictures in PPT and use presenter stick
    • maybe provide link to video? -> got you out of time in the end
    • more experience with the concept
    • the assumption was not so clear
    • too much time (30 mins enough?) -> skip pictures
    • from the announcement, expected more interaction
    • drop the kanban board for the presentation
    • don't fill a backlog if you don't do anything with it
    • pictures took too much time
    • don't waste time explaining a scrum board to an agile crowd; Just do it.
    • no time for all the Q&A, but you used the time for valuable things, so it was fine :-)
    • I should have been on time
    • attention not to make contradictory statements
    • present real FedEx day as a timeline instead of pictures
    • open question on increasing motivation outside FedEx days (title misleading)
    • no need to get defensive during Q&A
    • don't see the purpose of question post-its
    • the movie was more interesting than the preso
    • little presentation style details
      • time management adjustments
      • the photos are not so interestingfor the audience
      • find time to get to the questions on the post-its (it helps with continuity and shows how you value the audience)
    • More interaction and discussion
    • ensure mindmap of fedex days is visible to everyone
    • slow pace at start (show video sooner)
    • show pictures of what was delivered during fedex days
    • longer
    • you deserve a longer session
    • FEDEX is not a good nme for it. it looks like a company. find a good agile name (like : MakeItHappenDay)
    • more info about the impact on the day to day work. Is the motivation there only for those 24 hours ?
    • cut off questions faster
    • be more enthusiastic
    • know more about wha didn't work
    • a little bit more dynamic
    • filmpje zou vervangen kunnen worden door een praktisch niet-software voorbeeld
    ]]> Feedback Olivier.Costa 27 January 2012 18:27 GMT http://www.xpday.net/Xpday2011/sessions/Jacob%27s%20Ladder/Feedback.html http://www.xpday.net/Xpday2011/sessions/Jacob%27s%20Ladder/Feedback.html
  • nice introduction
  • discover a theory
  • difficult concept made clear with clear examples exercise
  • challenging, thought provoking
  • talking about practical examples to refactor
  • references
  • availability on github (Neal Ford's code)
  • different look at classical problems
  • type and transform as to basic thinking unify
  • forces you to think
  • discovery about FP universe
  • good explanation of morphisms, functors, ...
  • surprised with the complicated java examples
  • discover of category theory -> help to design
  • it turned my head upside down like each time i've been explained morphisms - great levels of abstraction To make it perfect:
    • leave out the last part because that part goes too fast
    • shorter: don't browse all constructions, focus on some and relate more to benefits for programming
    • more practical examples, but then that would require more time !
    • spend less time, or prepare better the Food & Pix example
    • definitely needs more time to sink in with me
    • maybe more presentation time helps (stepping through what & why, then examples and discussion)
    • more exercises
    • more code ?
    • finish in time ? (last slides went very fast)
    • what does Christoph do ? Armand was the only talker
    • give me a better brain, mine is very limited
    • strange title (not good)
    • may be a little bit messy
    ]]> Feedback Olivier.Costa 27 January 2012 18:11 GMT http://www.xpday.net/Xpday2011/sessions/Quality%20requirements%20in%20agile%20development/Feedback.html http://www.xpday.net/Xpday2011/sessions/Quality%20requirements%20in%20agile%20development/Feedback.html
  • the concept of abuser stories
  • hands on use case to compare different techniques --> dot voting
  • a lot of room to experiment
  • good overview of usability of techniques of the end
  • good format : makes you think
  • your help during the exercises: clarified & added value
  • giving a different view on requirements using 4 axes
  • new techniques learned
  • interactive
  • highly interactive
  • interaction
  • leuke oefeningen
  • goed begeleid
  • the groups to practice with non-functional requirement
  • 1,5 hrs to spend on thinking on combinations of techniques and NFR
  • interaction
  • you get to try out known techniques in a new context
  • nice interaction
  • confortable atmosphere to discuss the techniques
  • dot voting
  • content
  • concrete techniques
  • different perspectives of 3 experts
  • concrete cases
  • good to learn about different techniques
  • good discussion
  • definition of done on user story niveau AND sprint niveau
  • topic: non-functionals are not often discussed in agile
  • abuser stories
  • feedback from other groups
  • good example application
  • excellent descriptions of techniques
  • the setup of the session
  • the dots helped pulling out a good discussion
  • good exercices
  • good interaction
  • discussion after hands-on
  • interaction
  • context
  • way of defining acceptance criteria
  • interactive
  • learned new ways for techniques To make it perfect:
    • retrospectives were not that great because it's difficult to estimate the good & the bad when you haven't done the technique
    • explain exercises more concise
    • more copies of material per table
    • a bit more exploration before, about the techniques instead of only on paper
    • some hints to think about (like the verifiability, but more)
    • I would give some more different use-cases as you get more familiar with the technique after 3 times the same use-case but with different techniques
    • give hard cases with how they were tackled
    • present more clearly what is being asked
    • you can never cover all the possible techniques in 90 minutes
    • a little more theory
    • limit quality aspects and techniques so not everyone chooses the same
    • more background
    • wat meer uitleg hoe het in het scrum proces zou kunnen 'embedden'
    • don't allow people to interfere in the plenary. they make too much background noise
    • faster
    • more info/tips upfront
    • end with samples for paycento
    • a bit more dynamic from the presenter
    • more time: i want to handle more cases
    • divide techniques/aspects yourself. not by choosing
    • some concrete advice/take away from experience
    • roadmap (how do you recommend we apply/proceed with these)
    • more theory about the techniques
    • force groups to take specific combinations to get more balanced voting
    • the techniques are related to each other
    • how do you integrate the technique in the product backlog and user stories
    • war stories of how you have used these in real life
    • some more detailed theoretical insight about the different techniques. use images for explanation.
    • explain a bit more the different techniques
    • hands-on took too much time. but at the other hand it helped to "feed" the discussion
    • "force" more to use different scenarios
    • review done by expert
    ]]> Feedback Olivier.Costa 27 January 2012 17:38 GMT http://www.xpday.net/Xpday2011/sessions/A%20War%20Story%20of%20the%20Rise%20and%20Fall%20of%20an%20Agile%20Company/Feedback.html http://www.xpday.net/Xpday2011/sessions/A%20War%20Story%20of%20the%20Rise%20and%20Fall%20of%20an%20Agile%20Company/Feedback.html
  • expressive, illustrative
  • slides!
  • way of telling the story
  • essence of story
  • details
  • nice presentation /pictures
  • the real life story
  • passionate about the story / like the slides!
  • learnt a couple of new things on coaching
  • real story with long horizons
  • content
  • presentation
  • slides
  • recognizable patterns
  • good story teller
  • lessons: I understand the questions / trust is fragile / use drawings / look where the business needs Agile
  • inspiring story
  • if I can't draw the problem, I didn't understand it!
  • events --> training --> workshops --> individual coaching
  • interesting != usefull
  • a concrete story, nothing theoretical
  • spoken from the heart
  • clear communication
  • "from the trenches"
  • slides
  • practical
  • clear pictures, clear text
  • good presenter
  • got me interested the whole time
  • great english story telling
  • nice slides!
  • great story
  • story idea
  • 5 thinkgs to lead change (events, training, workshops, ind cloaching)
  • openness about applying Agile values to other things
  • content
  • way brought
  • makes me think about my own company
  • real world problems
  • missing bullet points
  • motivating story
  • good presenter, easy + fun to follow
  • from the trenshes
  • practical tips (events, training, workshop, what is problem?/is this problem?, recruitement, if you draw problem, you understand it)
  • drawings and pictures
  • deep-heart felt
  • sweet visuals
  • different - story telling
  • the style, energetic
  • the slides
  • nice presentation (story telling) style, good slides, well prepared
  • practical advice, many techniques
  • handdrawn sheets
  • examples
  • way telling your story
  • mixing examples with general story
  • enthousiastic, good story, terrific examples, personal, nice "slides"
  • story of rise and fall
  • good story
  • "if you can draw the problem, you understand the problem" --> :-)
  • funny pictures on the slides
  • awesome to see agility organisation wide instead of just agile software development
  • brief, clear, easy to understand, good message
  • great knowledge
  • great intro
  • useful start
  • the way it was presented
  • the sheets with the drawings To make it perfect:
    • keep the time
    • could be less abstract
    • lessons learned are not quite clear
    • a bit shorter
    • make it more compact, the end of the story took too long
    • timing (but that's difficult)
    • more time to discussions, Q/A
    • more time to wrap up and focus on key points
    • would like to know more what happened after the switch
    • the end of the presentation was a bit directive
    • take more time to tell the story in a relaxed way
    • I heared a lot of interesting things, but nothing useful. Please take more time to go into detail on the critical part. Some examples would have been great!
    • add a bit of interaction
    • I'd like to get some 'best practices' which I can apply in my company
    • better timing
    • no spelling gerrors ;-)
    • more examples
    • faster pace
    • more examples
    • some more details
    • provide some time for questions after the talk
    • more structure around presentation, perhaps a timeline that you keep coming back to
    • a bit of reflection about how others could "prevent" a fall in an Agile company
    • it was for me perfect
    • examples of how to apply the change in the company (instead of just the result)
    • more practical tips :-)
    • some involvement - if it can be done without destroying the story-telling
    • even more "depth"
    • understand more context: how many people, why the beginning society belongs to a big group at the end?
    • a link with how problem solving (AC3,...)?
    • make it fit in an hour
    • more concrete examples
    • the stories blended together a bit so the personas were not always clear
    • bit more time for a conclusion
    • give an overview at front
    • more interaction with audience?
    • more details: why did the structure fail to adapt to the crisis? Firing people wasn't an option? Why did agile prevent that?
    • 10/10
    • 10/10
    • 10/10
    • maybe a separate workshop -> not part of this session
    ]]> Feedback Olivier.Costa 27 January 2012 17:37 GMT http://www.xpday.net/Xpday2011/sessions/Back%20to%20the%20future/Feedback.html http://www.xpday.net/Xpday2011/sessions/Back%20to%20the%20future/Feedback.html
  • great fun
  • easy setup / good cheat sheets / good excercises
  • get to use the language in the environement, tests, etc + cheat sheet
  • learned something new and very different
  • historical insights about agile & small talk
  • hands on the machine fast: USB keys
  • hands-on technical session, there aren't so many interesting topic
  • hands on
  • new stuff
  • cheat sheet
  • learn how easy is to use the new environment
  • liked ST story
  • liked easy to set-up To make it perfect:
    • maybe a bit slower introduction to the language
    • i would like to understand more thoroughly. bit confused/overwheled
    • too tired at the end of friday...
    • sometimes too fast as manipulation
    • couldn't go to the end of the excercises
    • less "smalltalk is better than x": this might be true (to your opinion) but this is annoying.
    • code examples, sometimes frustrating trying to use only cheat sheet
    • easier examples first
    • better tutorial
    • edito/env browser key : some more help about that
    • pair one beginner with one expert
    ]]> Feedback Olivier.Costa 22 January 2012 20:35 GMT http://www.xpday.net/Xpday2011/sessions/Change%21%20Change%21%20Change%21/Feedback.html http://www.xpday.net/Xpday2011/sessions/Change%21%20Change%21%20Change%21/Feedback.html
  • Theory about change
  • good interaction
  • good slides
  • real-life situation
  • we won :) !
  • six conditions for change
  • we know too much truth
  • interaction
  • factual presentation
  • exercise
  • structure & theory
  • very interactive
  • interactive
  • very good ideas to go for change
  • great !
  • interactive
  • energetic
  • experiment
  • criteria to asses the current context
  • the exercise
  • everything
  • interaction between presenters
  • very good story + supporting slide
  • challenging workshop
  • speakers know what they are talking about
  • use of small experiments
  • overview of the conditions of change --> concept I hadn't heard before
  • practical exercise: feedback from participants
  • Very usefull
  • loved the theory & interaction (thanks Pierluigi & Dirk, Ole)
  • Great !! like it a lot, insights, devising experiments, good to learn
  • subject
  • simple framework
  • interaction
  • experience sharing
  • fun and interactive !
  • loved the presenters' style & interaction
  • the "experiment" aspect of change - makes it safe to fail.
  • my group was great to work with !
  • great theory :
    • usefull
    • new
  • great presentation techniques
  • workshop: let's you remeber better To make it perfect:
    • this is a big domain, it needs more explanation
    • perhaps add some more background info (books, urls, put it on the blog)
    • more time for experiments
    • more time
    • slow down or take more time
    • explain essential of the experiment
    • maybe a little more time for discussion
    • time management
    • too much details in the case to get them all in a few minutes
    • explain purpose of experiment more
    • a jury looks to work better than the voting captains
    • i found the difference between 'old problems' and 'new problems' potentially confusing
    • the teams rating each other ironically didn't work well, maybe better to use perfection game ?
    • time mgt, we missed 'open, arrested, close'
    • focus on the 6 conditions and leave enough time for interaction part. that is the best way to understand what the conditions need: experimenting
    • less tolerance for discussion on points
    • change examples are of changes which are irreversible, so no way for someone NOT to change. Add examples of others ?
    • switch the concept of the session:
      • let the teams define different solutions on the path to change
      • then try to map those solutions to the conditions of change
    • time management !
      • shorter first explanation
      • more focus/tips on/for experiments
    • voting
    • let the audience find the conditions themselves
    • the only thing for me is the 3rd item: dissonance. I am struggling to know if it is really necessary to create pain (or some pain). There's a lot of other research - including what's in the books POSITIVITY & SWITCH about how being more open & motivated helps enable people's willingness to change.
    • all people have to give explanation when they rate (the explanation is the interesting part, not the rating)
    • timebox sections/people (ie: max 1 min explaining idea to group)
    • "planning poker" for rating --> so people don't vote strategically
    ]]> Feedback Olivier.Costa 08 January 2012 17:15 GMT http://www.xpday.net/Xpday2011/sessions/Difficult%20Conversations%20Workshop/Feedback.html http://www.xpday.net/Xpday2011/sessions/Difficult%20Conversations%20Workshop/Feedback.html
  • the 3 part of view stories
  • the link to psychology
  • exercises were not too hard to play
  • good balance exercise + theory
  • interactive
  • tools are helpful (using other perspective)
  • content: story telling
  • roleplay: balance between model/action
  • organisation
  • learned about 'difficult conversations' book
  • very clearly explained
  • very practical
  • very real
  • use cases / workshop
  • great outcome
  • breaking down of the problem
  • interactive
  • good exercises/scenarios
  • participating !
  • well controlled scenario's
  • important skill, fun, interactive To make it perfect:
    • more conflict in first example
    • not quite sure what to note during sessions
    • just touching service (but still informing)
    • clarify last exercise( instead of rewriting ask for suggestions (post it !)
    • have cards ready and complete with full text
    • lot of roleplaying requires a lot of energy, so friday end-of-day difficult for participation
    • all ok
    • some summary/overview of what we have learned
    • a bit an abrupt end
    • ending was a bit hasty
    • use 'DISC' profile ?
    • tips on how to control 'deadlock' due to 'adrenaline rush'
    • a little more on the 3 story approach
    • maybe play out 2nd scenario first, before explaining how to think differently. To avoid 'traming' 2nd scenario (or go straight to new story)
    ]]> Feedback Olivier.Costa 08 January 2012 16:59 GMT http://www.xpday.net/Xpday2011/sessions/Solving%20Tough%20Problems%20using%20the%20A3%20Process/Feedback.html http://www.xpday.net/Xpday2011/sessions/Solving%20Tough%20Problems%20using%20the%20A3%20Process/Feedback.html
  • interactive
  • small groups
  • theory/practical combination
  • dynamisch
  • veel oefenen
  • introductory
  • A3 is cool
  • good practice !
  • kernachtig, bruikbaar & praktijk
  • belovende techniek
  • A3 achtergrond oefenen met A3
  • goede case
  • goede workers example
  • goede interactie
  • bevlogen manier van brengen To make it perfect:
    • ask questions to confront us with what we are doing during workshop
    • shorter cycles -> more feedback -> better end result
    • more focus on A3 itself, less on the roleplay
    • ask more time for the session
    • provide solutions
    • make the case simpler for smaller groups
    • smaller & simpler problem case (situation)
    • in plaats van te laten proberen, een voorbeeld geven van hoe het gedaan werd. met 5 minuten over A3 worden te veel fouten gemaakt
    • less text
    ]]> Feedback Olivier.Costa 08 January 2012 16:50 GMT http://www.xpday.net/Xpday2011/sessions/Business%20Constellations/Feedback.html http://www.xpday.net/Xpday2011/sessions/Business%20Constellations/Feedback.html
  • it was just great
  • the out-of-the-box methods
  • the 'quiet interaction' of the session
  • how it stimulated thinking about the relationships in a organisation
  • nice to get in touch with what you really want
  • the simplicity
  • the power & impact
  • surprisingly useful
  • loved the interaction
  • totally surprising the approach from "constellation"
  • very valuable; thanks
  • chance to practice non-judgmental awareness
  • chance to put past problems further behind me
  • you offered relatively little directive advice To make it perfect:
    • take 2 slots next time to go deeper
    • perhaps more theory around the process
    • is there a way to measure this ?
    • also i can see that (even for Rik) it is difficult to judge the constellations ;-)
    • reflect a bit more on how to proceed with this
    • more description & clearance on roleplaying
    • i didn't always understand the game
    • recommend a single book & resource for further study
    • recommend some things to do with the information just uncovered
    ]]> Feedback Olivier.Costa 08 January 2012 16:39 GMT http://www.xpday.net/Xpday2011/sessions/Training%20from%20the%20back%20of%20the%20Room/Feedback.html http://www.xpday.net/Xpday2011/sessions/Training%20from%20the%20back%20of%20the%20Room/Feedback.html
  • best session for me today !
  • hands on practice & exercices
  • the 'mini trainings' in small groups
  • I became really motivateo !
  • active, trainings that i like
  • interactive !
  • applied training from the back of the room tech - myself. as expected of course :-)
  • very interactive training
  • applying the concepts
  • interactive
  • sticky
  • lot of energy
  • time flied by
  • how the subject was applied
  • it sticks !
  • great knowledge sharing
  • great ! the ideas are what I need
  • as a trainer this is very useful material
  • having interaction and real-life experience is really great
  • theory provided with book. great as well
  • interactive
  • apply the things you are to learn ourself
  • teach your self
  • open & 'gentle' atmosphere
  • most extreme session
  • doing everything ourselves with good guidance
  • de opzet, het zelf werken/doen, dus het aanschouwelijke To make it perfect:
    • some of the theory went a little too fast
    • make it longer : one day
    • first part, writing own thoughts was a bit too unorganized an chaotic
    • more stories of their usage in practice
    • tell a story from your experience in applying this
    • more oxygen in room :-)
    • keep in mind to tell, not to take it to much to a meta level
    • i do not know ! possibly in the future I'll be able to help more
    • make the first exercise less chaotic
    • first game could be better explained
    ]]> XP Days Program Pascal.Van.Cauwenberghe 24 December 2011 17:00 GMT http://www.xpday.net/Xpday2011/XPDay/Program.html http://www.xpday.net/Xpday2011/XPDay/Program.html Thursday December 1st   Room 16 Room 17 Room 18 Room 1 Room 2 Room 1B 7:00
    8:00 Early Morning sessions
    hosted by Olivier Costa
    Feedback 8:30 Registration and coffee 9:00 Opening plenary All Day Softwarewolves - sidetrack hosted by Johan Peeters & Peter Doomen
    Feedback 9:30 Test-driven application in 60 minutes

    Marcin Floryan & Marc Johnson
    Feedback A War Story of the Rise and Fall of an "Agile" Company

    Jan De Baere
    Slides
    Feedback Scrum for dummies

    Jef Cumps & Philip Almey
    Slides
    Feedback Wireframing: Part of your Agile Analysis Toolbox

    Pascal Mestdach & Nick van Eeckhout
    Slides
    Agile Analysis Toolbox Poster (large pdf)
    Feedback Exploratory Testing in Pairs

    Markus Hjort & Tiina Kiuru
    Feedback   10:30 Coffee break 11:00 Server Login Considered Harmful

    Stephan Eggermont & Willem van den Ende
    Feedback It Takes Three to Tango: a story on distributed Scrum

    Bart Reyserhove
    Feedback Visualising Quality

    Gojko Adzic
    Feedback Lean Startups: what happens before iteration 0?

    Vladimir Blagojevic & Nick Boucart
    Slides
    Feedback Building High Performing Agile Teams

    Henk Jan Huizer & Ronald de Leeuw van Wenen
    Feedback   12:00 Lunch 13:00 Afternoon opening plenary 13:30 Architecture Refactoring - Dramatical changes

    Bruno Thomas & Jean-Philippe Caruana
    Slides
    Feedback
    Buildr, a simple, powerful and efficient build tool

    Jean-Philippe Caruana
    Slides
    Feedback Speed Reading for Beginners

    Bernard Van Der Beken
    Feedback Crucial Confrontations

    Yves Hanoulle & Christophe Thibaut
    Slides
    Feedback Features, who cares? It’s the benefits that count

    Jenni Jepsen
    Slides
    Feedback Agile Coaching Dojo

    Nick Oostvogels & Olaf Lewitz
    Slides
    Feedback   15:00 Coffee break 15:30 Test-Drive your Application End-to-end

    Lars Vonk & Sander Nieuwenhuizen
    Slides and Code
    Feedback The Lazy Team Game

    Nicole Belilos & Vincent Lussenburg
    Feedback Agile Contracting Games

    Remi-Armand Collaris & Dick van de Sar
    Feedback Innovation Needs Waste!

    Pierluigi Pugliese & Dirk Lässig
    Slides
    Feedback Human nature and why Agile works

    Ole Jepsen
    Feedback   17:15 Day closing 17:45 Drinks sponsored by inxin 19:00 Dinner sponsored by iLean 20:30 Evening activities

     

    Friday December 2nd
      Room 16 Room 17 Room 18 Room 1 Room 2 Room 1B
    7:00
    8:00    		 Early Morning sessions
    hosted by Olivier Costa
    8:30 Registration and coffee
    9:00 Opening plenary
    All Day Softwarewolves - sidetrack hosted by Johan Peeters & Peter Doomen
    9:30 Extreme Startup

    Robert Chatley & Willem van den Ende
    Feedback    		 The Lean Agile Sandwich

    Cesario Ramos & Wim Van Broekhoven
    Slides
    Feedback    		 Experience the power of visualization

    Gero Vermaas & Sander van den Berg
    Feedback    		 Product Management using Effect Mapping

    Gojko Adzic
    Feedback    		 From 3 weeks to 30 minutes - A journey through the ups and downs of test automation

    Peter Thomas
    Feedback    		  
    10:30 Coffee break
    11:00 Extreme Startup: CONTINUED
    Feedback    		 TDD with Mock Objects: Design Principles and Emerging Properties

    Luca Minudel
    Slides
    Feedback    		 Agile in the Enterprise: a practical toolset

    Koen Aben
    Feedback    		 Agile through the Eyes of the Business

    Amerik van Rijn, Joris Lange & Vincent Lussenburg
    Feedback    		 FedEx Days: Awakening Intrinsic Motivation

    Rob van Lanen
    Whitepaper
    Feedback    		  
    12:00 Lunch
    13:00 Afternoon opening plenary
    13:30 Jacob's Ladder

    Arnaud Bailly & Christophe Thibaut
    Session materials
    Feedback    		 eXtreme Personal Finance

    J.B. Rainsberger
    Feedback    		 Solving Tough Problems using the A3 Process

    Marco Mulder & Lars Vonk
    Feedback    		 Quality requirements in agile development

    Alexander Helleboogh, Nelis Boucké & Johan Peeters
    Slides & Handout
    Feedback    		 Change, Change, Change!

    Pierluigi Pugliese & Dirk Lässig
    Slides
    Feedback    		  
    15:00 Coffee break
    15:30 Back to the future, (Re)Learn Smalltalk

    Stephan Eggermont & Willem van den Ende
    Feedback    		 Difficult Conversations Workshop

    Marcin Floryan
    Feedback    		 Training from the back of the Room

    Jef Cumps & Kris Philippaerts
    Slides
    Feedback    		 Business Constellations - Create a Breeding Ground for Change

    Remi-Armand Collaris & Rik Hurkmans
    Feedback    		 Tribal Leadership - Create the place where you long to belong

    Portia Tung
    Slides
    Feedback    		  
    17:15 Conference closing
    17:45 Drinks
    Legend
    Technology and Technique
    Team and Individual
    Process and Improvement
    Customer and Planning
    Cases and Intros
    ]]>         Feedback vera 11 December 2011 20:52 GMT http://www.xpday.net/Xpday2011/sessions/Product%20Management%20using%20Effect%20Mapping/Feedback.html http://www.xpday.net/Xpday2011/sessions/Product%20Management%20using%20Effect%20Mapping/Feedback.html
  • high energy
  • the exercise
  • great idea, love it! definitely going to use it.
  • interactivity
  • sunject
  • useful
  • new ideas
  • lot of energy from presenter
  • interactive
  • very useful technique
  • good explanatin
  • good to have exercise (then you remember it more and you experience the outcome)
  • very energetic
  • nice practice!
  • good pace
  • clear instructions
  • well facilitated
  • knowledgeable speaker
  • quite good mix between theory and practice
  • very interesting approach
  • hands-on exercises, great example!
  • easy techniek
  • well explained
  • the Effect (Mind) ap, I will use it and want to learn more
  • excellent insight on reducing creating waste
  • really going to try this!
  • motivated speaker
  • hands-on
  • no death by powerpoint
  • interesting
  • good example
  • practical
  • really insightfull
  • no sheets
  • short and clear explanation
  • good hands-on excercise
  • very practical, I can use it tomorrow!the talk! had seen the material, but never the talk
  • interactivity
  • very interesting and inspiring
  • someting I'm going to use next week
  • will take this away next week at my project
  • good mix theory/exercise/tips
  • interesting technique
  • easy to understand
  • effective!
  • creative technique
  • awesome!
  • good example
  • good conceptualisation
  • easy model
  • the example given
  • very interesting ideas: I will try it on Monday
  • references
  • dynamic presentor, with good sense of humans
  • fast workshop, bu twe can see the power of this technique
  • liked spontanity
  • liked balance between preserntation and activities
  • the dynamic
  • high energy speaker
  • little bit of theory and practice --> good
  • real life examples
  • very passionate
  • states the context
  • simple yet powerful
  • energy
  • practical
  • powerful tool, good pointers
  • very energetic, inspirational way to share your thoughts and ideas with us
  • strong presentation
  • interesting exercises
  • no slides, whiteboard presenting
  • good speaker
  • useful practice that canb easily be implemented
  • practical, simple and powerful technique To make it perfect:
    • +30 minutes to give more feedback on how to xxx a usefull map
    • 10/10
    • more time/interaction in effect mapping
    • 10/10
    • 10/10
    • does it require facilitation?
    • selection of coloured pens to annotate/make drawing (help in/learning)
    • ask particiapnts to show map drawn
    • have somebody playing the business role
    • this is not enough
    • 10/10
    • ?
    • more "welcoming" atmosphere
    • better technical and room preparation
    • try treating people better -your Q&A approach could be softer
    • found the criticism of others presentations ("the day before") offensive
    • keep up the good work! (Poet of Rotterdam)
    • smaller group so you can interact in exercise
    • limit # of people
    • more time for exercise
    • have a laptop setup beforehand
    • smaller group (reduce number of attendees)
    • increase length to min 1.5 hours
    • make session a bit longer
    • limit # people to session
    • slides
    • 10/10
    • better guidance during the exercise
    • more feedback
    • 1 slide with the links
    • "start with WHY"
    • 10/10
    • 10/10
    • 10/10
    • session was just too short or group too large to fully benefit from the exercise
    • bigger room to accomodate the audience
    • longer session
    • less hands-on (shorter), I would have liked to see this feature injection, also more real-life examples
    • the "effect map" that you used as an examle could be more completed if you also showed the "working products" that were made by this
    • spend time to answer questions at all tables during exercise
    • more time for the exercise
    • longer session
    ]]> Feedback vera 11 December 2011 20:29 GMT http://www.xpday.net/Xpday2011/sessions/Human%20nature%20and%20why%20Agile%20works/Feedback.html http://www.xpday.net/Xpday2011/sessions/Human%20nature%20and%20why%20Agile%20works/Feedback.html
  • Theory/practice
  • entertaining and interesting
  • experiments
  • illustration of ideas
  • good one!
  • interactive
  • good mix of xxx/exercises
  • met new people
  • learned about xxx project
  • interactivity
  • sharing experiences
  • mixing powerpoint whiteboard
  • the whole idea combining psychology with development/agile
  • give me a new way of thinking and looking at agile
  • a session whose value probably increases over time
  • good interaction
  • good presentation skills
  • nice mixture of agile and individuality
  • a lot of energy here
  • it's good to think why agile works
  • a new perspective makes you think
  • describing and showing the effects of the "muid" facts
  • all the tests, workshops
  • theory and practice, combination
  • interactivity, gaining insight through examples
  • timeboxed excercises
  • very interactive informing and fun
  • enthousiastic
  • doing push to new things
  • exercises
  • innovation
  • creativity
  • interactiveness
  • your spirit and humor
  • stories..
  • interactive exercises
  • relaxed atmosphere
  • very interactive
  • working in small groups
  • made you think
  • the exercises
  • some science talk (just enough) To make it perfect:
    • at the end: to much work sessions. add more theory
    • more of this ;-)
    • more knowledge, more structure
    • 1 more chair ;-)
    • new "gorilla" game
    • more peole doing simultaneously "green, red, blue, yellow" test
    • just more!
    • I don't know, it's an experiment
    • perhaps add some background references
    • I am always interested which kind of people you meet. Does this makes a difference
    • more concrete examples
    • more cases on how to use...
    • more human nature examples
    • maybe even more creative exercises, eg LEGO
    • drop the gorilla
    • 10/10
    • make hard science facts - not just anecdotal
    • define "human nature"
    • slightly quicke mace
    • clarify WHY (reason) for session
    • provide takeway/summary of session
    • make it 'smoother'
    • change the gorilla examle (most people already know it)
    • clear goal of what you try to achieve with the session and exercises
    ]]> Conference Feedback Pascal.Van.Cauwenberghe 11 December 2011 19:19 GMT http://www.xpday.net/Xpday2011/Feedback.html http://www.xpday.net/Xpday2011/Feedback.html Conference Feedback

    Pictures

    Tweets

    ]]> Feedback dirk.devriendt 05 December 2011 23:34 GMT http://www.xpday.net/Xpday2011/sessions/Agile%20in%20the%20Enterprise/Feedback.html http://www.xpday.net/Xpday2011/sessions/Agile%20in%20the%20Enterprise/Feedback.html

  • nice idea
  • nice discussion
  • the subject
  • your experience To make it perfect:
    • Better structure and more practice
    • it was messy
    • Talk more about real life examples
    • try to adapt your preparation to the need of the public (experienced agile practitioners)
    ]]> Feedback dirk.devriendt 05 December 2011 22:54 GMT http://www.xpday.net/Xpday2011/sessions/eXtreme%20Personal%20Finance/Feedback.html http://www.xpday.net/Xpday2011/sessions/eXtreme%20Personal%20Finance/Feedback.html
  • challenges what's really valuable in life
  • It's almost stand-up comedy
  • you clearly believe in it
  • out of the box
  • interesting subject
  • story told from personal perspective
  • the link with XP practices
  • the talk was fun
  • open mindset
  • eye opener
  • super fun
  • great ideas & stuff to think about
  • great! thank you!
  • very interesting
  • sharing personal experience To make it perfect:
    • make sure that calculation are understood for everybody - I didn't follow... For example: put up an example on a projector
    • more facilitation rather than just walk up and down the floor
    • overall: the meaning of the message just didn't come across
    • add examples that are visible (slides etc)
    • doesn't really make a "click" for me
    • you ask questions to the audience but don't seem interested in the answers
    • be prepared! ("in the words of the great Scar")
    • compare to similar ideas (80/20 rule book, 4HWW, ...)
    • compare to other people
    • some slides
    • European culture...
    • more presentation slides
    • face it: we're lazy, we like some examples
    • respect agenda a bit more
    • material
    • exercises too fast
    • group exercises
    ]]> Feedback dirk.devriendt 05 December 2011 22:41 GMT http://www.xpday.net/Xpday2011/sessions/TDD%20with%20Mock%20Objects/Feedback.html http://www.xpday.net/Xpday2011/sessions/TDD%20with%20Mock%20Objects/Feedback.html
  • +- the same insights that I gained doing TDD with Mockito, just explained better, by using design principles
  • more ignoring insginificant diff between agile methods, generalize appropriately
  • explanation of the context
  • good structure in presentation
  • using code to demonstrate/clarify explanation
  • clear explanation
  • good topic, not new, but certainly interesting
  • explanations
  • level of detail
  • practical relevance
  • "TDD vs good developer effects"
  • good quotes
  • focus on context
  • good philosophical view on TDD (but could be shorter)
  • real life experiences instead of just theory
  • solid principles are always good to refresh To make it perfect
    • te weinig concrete voorbeelden om te overtuigen; veel minder praten/herhalen van wijsheden en meer tonen: code voor / code na
    • make it more a doing session
    • good tips and tricks
    • design patterns
    • sometimes difficult to understand (practice english more?)
    • visualise more
    • more cohesive story, maybe some more slides illustrating points. Not only proposition - quote - conclusion
    • more code examples
    • you explaine the different mocks and designs well, but will be even clearer if you indicate on the slide or write down what you explain (ISP = Interface Segragation ...)
    • I did like the quotes in the beginngin of the presentation, but there are so many that they distract from what you are saying
    • I would prefer to skip the history and delve deeper into the why's
    • add something interactive
    • interaction with public?
    • big part was about promises of TDD and what you observed after TDD, I expected more practical usage of mock objects to see if I do it in a similar way
    • spend less time per statement
    • what is your goal (explain, motivate, ...)?
    ]]> Feedback dirk.devriendt 05 December 2011 22:23 GMT http://www.xpday.net/Xpday2011/sessions/Agile%20through%20the%20Eyes%20of%20the%20Business/Feedback.html http://www.xpday.net/Xpday2011/sessions/Agile%20through%20the%20Eyes%20of%20the%20Business/Feedback.html
  • nice to hear agile works so well for Rabobank
  • the 3 different viewpoints ||||||
  • time for questions ||||||||
  • bringing the product owner
  • the last part with the interaction, especially since all three roles were represented
  • introductory
  • clear presentation of business person vision
  • different perspectives, good answers to the questions
  • got better in the second half, thanks to the questions from the audience
  • you have slides, this helps us after the conference
  • real examples ||
  • replying to questions
  • good presentation
  • interesting case
  • interesting viewpoint
  • peak into how they do agile To make it perfect:
    • use remote to flip through slides
    • keep lights on, it was too dark
    • intro is too long
    • skip the Rabobank & Xebia commercials |||||||
    • make it less of a success story, there must have been failures and problems
    • if you must play the video, do it while we are on the way out, I completely lost focus :(
    • tell us, don't show us, I don't need the commercial for agile
    • I would like to be able to see you; light would have helped
    • Introduce Rabobank in a shorter way
    • 15-20 minutes of introduction, the rest Q&A
    • less videos ||
    • personal stories in a structured way (1. PO, 2. PM, 3. ...)
    • drop the videos - wrong audience and boring
    • explain more the very beginning of the motivation and the adoption of agile
    • you don't need to sell "Agile" at this conference
    • doesn't really deliver the abstract, it's not focused on business, but on the different viewpoints
    • make it less for dummies ||
    • more focus on: explaining how you bring about the change of mind
    • could have been a bit more about what agility brings: communication, focus on business
    • explain a bit more the roles of everybody
    • elaborate preparation
    • more info on top-down support
    • more specific would be nice
    • it was sometimes hard to follow the discussion; maybe repeating the questions or writing them down would help
    • introduction was a bit long; could have concentrated on what was special about this project, not that general
    • more visualization (pictures, drawings)
    • less marketing stuff
    ]]> Feedback vera 05 December 2011 21:47 GMT http://www.xpday.net/Xpday2011/sessions/Test-Drive%20your%20Application%20End-to-end/Feedback.html http://www.xpday.net/Xpday2011/sessions/Test-Drive%20your%20Application%20End-to-end/Feedback.html
  • context of GOOS and TDD
  • interactif walking skeleton
  • practical examples are nice
  • use of Ruby and RSpec
  • practical applicability
  • smoothness of the coding kata
  • live demo project -> even a coding-newbie understands!
  • no buzzwords or trends, functional and systems approach to what you test and xxxx
  • live demo
  • goed duidelijk GOOS uitgelegd
  • great session, a lot of information (to learn)
  • worked example
  • well prepared (UI mockup, diagrams etc)
  • having a reference (the book)
  • the 3 layers test/apprunner/testDriver
  • the demo!
  • explained concepts very well
  • good balance of theory + demonstration
  • great session on how to write your simple UI test for web apps (really great)
  • nice case and live programming
  • convincing demonstration
  • session format
  • nice example
  • sharing of experiences
  • working code
  • knowledge of the tools used
  • the topic
  • content is good
  • interactive
  • examples
  • interesting approach
  • great 30s presetnation
  • great beginning (3 styles of TDD) -> GOOS
  • practical insights
  • live coding + ruby
  • give me the will to re-read GOOS
  • explanations backed up by a successful handson coding session
  • well prepared
  • theory cleanly explained
  • coded something working
  • concept nice
  • kata
  • xxx interoduction + kata To make it perfect:
    • the examples may be presented a bit faster
    • framework for swing application
    • what about backend-focused dev. usually xxxx other party builds a frontend. -> how to keep your xxx happy?
    • borelnootjes en bier ;-)
    • a little bit easier code sample, it was really fast
    • less time on explaining styles
    • clarify crucial concept (walking skeleton) early on
    • focus example on concept of working skeleton
    • better colors to be able to see the blue/purple (maybe best on a white background)
    • keep the naming in the code exactly in lin with the overview (auction-driver=test-driver)
    • a solution for swing applications!!
    • interactive part (but of course maybe not possible because of time limit)
    • introduction shorter
    • give an overview of good practices and experience
    • go a little further to demonstrate the whole end-to-end chain
    • need more time again!
    • consider more complex real life cases
    • make code more readable
    • speak both in small turns, to make it more living
    • post-it too little (unable to read from the end of the room)
    • choose a != example than from the booko
    • (sorry for falling asleep: too tired)
    • make a != between stubbing and mocking and faking (see xUnitPatterns)
    • example too simple tov real C++/C# appl
    • kata: less time on tdd (alread known) to focus more on the outside in approach, on the GUI-specific TDD (e.g. classes could have been written before). Example fo how product owners can write the GUI acceptance tests (tooling like selenium...)
    ]]> Feedback vera 05 December 2011 21:29 GMT http://www.xpday.net/Xpday2011/sessions/Agile%20Contracting%20Games/Feedback.html http://www.xpday.net/Xpday2011/sessions/Agile%20Contracting%20Games/Feedback.html
  • Een interessant, vaak ondergewaardeerd, onderwerp
  • Leuke spelletjes
  • Geeft stof tot nadenken
  • Heel duidelijke linken om dingen te begrijpen
  • practical games to illustrate something boring like IT-contracts
  • veel interactie
  • De "games"
  • praktisch gemaakt
  • practical an surprisingly applicable
  • was erg leuk! Link tussen spelletjes en projecten was erg duidelijk
  • Ontzettend leuk
  • zet aan tot denken
  • Games and link to IT contracts
  • interactive
  • participation
  • similarities games and IT in terms of contracts
  • game component
  • motivates you to question
  • game/project link
  • vgl contract met regels van een spel
  • duidelijk uitleg, rustig
  • cool simulations for real world problems
  • saboteur to simulate real project
  • ! games rules as basis for agile contract ! To make it perfect:
    • meer tijd zou nuttig zijn
    • een aantal contracttypes bespreken met voor-en nadelen
    • meer van uit de groep laten komen, meer discussie -> soms trekken jullie te snel conclusies vanuit eigen referentiekader
    • give an example of an agile contract
    • a little more time
    • wat is er te vertellen over kleine teams
    • contract example (function points?...)
    • ook aandacht voor bedrijven met interne klanten zonder budget of contract
    • iets dieper op theorie in (consequentie is mogelijk, spel minder)
    • bit more time to go deeper in the subject
    • some practical examples on agile contracts
    • more examples/elaboration/explanation on details of agile contracts like the functiepoints
    • a bit more presentation and a little less gaming
    • a lot of info on the slides
    • conclusions, summary @end
    • minder spel (doe ik niet graag), meer uitleg en vbn
    • add a real life example of a game rules contract
    ]]>