OK, you know the standup is supposed to last 15 minutes, but yours’ last 45 minutes or more. You wonder, how can we say anything useful in 15 minutes?

In this 10 minute lighting session, which by the way is shorter than your standup, we will use a sample Team Board (I did say Team Board, not Task Board) to demonstrate how to hold an effective standup that will allow your team to quickly coordinate, and thus self manage their efforts.

We will also learn more about the Almost Daily Sit Down, and learn how sit downs, can be the cure for your sick standups!

People use social networks to contribute, share, subscribe and read about what is most relevant to them. There’s a reason why Facebook, Linkedin, Twitter are popular and growing.

We will talk about the importance and benefits of leveraging social networking paradigms in the Agile development world. Combining these two powerful concepts could help increase the use of Agile development, improve transparency, and also encourage collaboration amongst self organizing teams.

Learn how you can adopt these paradigms in your work environment with existing and new products.

Pair programming requires a certain level of social interaction that few developers are accustomed to, even with their peers. Learning to work effectively with people of different personalities and skills can sometimes seem daunting compared to working alone in a dark corner. We have seen pairing work wonderfully, we have seen it be an abysmal failure that involved some shouting and storming away, and we are going to bring our best-of moments to you in comedic fashion. Attendees will walk away with good understanding of pairing patterns, anti-patterns, and mentoring patterns.

This session will demonstrate how to apply BDD and Continuous Testing to a full project lifecycle. Using IDE support by Eclipse where applicable. From developing an Enterprise level SUT (System Under Test) with Selenium2 for regression test Fixtures to a preview of all relevant tests with the built‐in functionality of Eclipse. Plus an Automation Test Framework using the best of Easyb and Concordion. We automate those tests in a simple Test Cloud with CI servers like CruiseControl or Hudson/Jenkins. Allowing multiple releases, modules or stages to be tested simultanuously and continuously.

Our group of scientists have formulated a suite of open-source tools that make growing robust C applications an enjoyable endeavor. These tools facilitate organic growth of robust and maintainable applications. Unity, Ceedling, CMock and CException are open-source projects whose aim is to make setting up and growing embedded C applications a trivial effort so that developers can focus on features and content. A full overview of these tools will be given, followed by a demonstration of how these tools are used collaboratively to facilitate an efficient TDD workflow in C.

Solve complex problems, build consensus with other teams and managers, and share knowledge with the Lean tool called A3, short for ‘problem-solving A3 report’! But what is an A3? How do I write one? What results can an Agile team get from this Lean tool? You will learn all that, and more, through the true story of a group of courageous Agile practitioners who formed a Lean-Agile A3 community with the support of the Agile Alliance and Art Smalley, world expert on A3 thinking. Come and see real-life Agile A3s, and hear how you can start your own A3 community tomorrow.

Test Driven Development and Behaviour Driven Development are a key ingredient to any agile project. However what are the boundaries between them? What should be tested as a unit test and what should be tested as feature? Even seasoned developers and architects sometimes have a hard time trying to answer these questions. Join me in a session in which we will work together identifying common mistakes done while implementing both methodologies, discuss how to avoid them, how to improve our current practice and learn recipes for common scenarios that appear in most popular kinds of projects.

Agile and Kanban together to create maintenance releases separates the unpredictable job of fixing defects from the predictable work to validate them. Defect resolution times are hard to forecast because the environment may be hard to recreate and a safe fix may take analysis. Very short Agile sprints manage the constant prioritization of defects and team coordination. Defect validation time is more predictable and Kanban provides a reliable way to verify small batches of fixes for a maintenance release. Come learn how to use these processes together to improve your maintenance deliveries.

Test automation is software development. As with other software development efforts, most of the cost of test automation occurs during maintenance after the tests are first written. Automated tests can become brittle, so that a small change in a requirement or in the software renders scores of tests obsolete in the blink of an eye. How can we reduce the high cost of inevitable change? Dale Emery demonstrates key principles for writing adaptable automated tests: remove duplication, focus on the essence of the test, and name every important test idea.

From past experience, I developed minimal process artifacts which I found useful and reusable from one client to another. My objective is demonstrating these artifacts so that attendees can learn their objective and how they can instigate improvements in their organizations. My aim is to get Aha moment from the attendees on the usefulness and applications of those artifacts in their contexts. An example of these artifacts is the technical debt log. By attending this session you quickly can grasp these artifacts and use them to drive your agile initiative at your organization.