|Put your ideas for sessions here with a one line summary. The purpose of this page is not to fix the program in advance, but to get the flow of ideas going before the conference and to give other interested people an idea of what to expect from the conference. The definitive program will be determined by all participants present at the OpeningSession.
See also the Schedule for details on start and end times and time slots available for sessions.
As an inspiration for new session, you could take a look at last years' ideas for sessions
and last year's outputs are an indications what topics the participants liked.
- Project level metrics aligned with company level Throughput Accounting - PascalVanCauwenberghe
- PragmaticRiskManagement - MarcEvers
- AutomatedAcceptanceTestingWithWatir - MarcEvers
- SurvivingNonAgileEnvironments - SvenGorts
- IncrementalConstruction - BernardNotarianni
- 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