How to solve your toughest impediments - Jef Cumps
Did you ever struggle getting management support or decisions? Are you looking for ways to assess and address organizational impediments that are blocking or holding back your implementation of Agile? Then join this session to learn how the Lean A3 tool helps you in:
- defining a problem or desired outcome
- quantifying costs and benefits
- getting buy-in and approval to solve the problem
- following-up on the solution
This session will be a guided exercise, where the facilitators provide the necessary insights and knowledge 'just in time' during the session. You will work in small groups that first identify common, hard-to-solve impediments or problems. After clustering and prioritizing all impediments, each group will build an A3 for one of them. This will provide all session participants with A3’s for all chosen, top impediments that they can use in their own team or organization.
Case studies: Kanban at personal, software, non software and portfolio level - Jan De Baere
As project management office in a large and traditional Belgium company we promote - unofficaly - agility in the company. One of the things is that we started to use kanban/visual management. It starts with a quick overview of kanban so everybody should be able to follow. Main thing is to show real live examples:
- Three maintenance teams
- Two non software teams
- Portfolio level (200+ projects)
As well in the maintenance teams as in the non software teams we have distributed team. As side information on the portfolio level topic you'll also receive an idea on how we included agile in our project management method.
Bridging the Management Gap - Tiago Garcez
While Agile implementations have been experiencing considerable successes in many cases, there seems to be an inverse relationship between the size of the company adopting Agile and the level of success experienced in the adoption. Large organizations still do, in general, treat Agile as an "IT initiative", while smaller organizations (who are more used to being flexible and responsive) typically have an easier time treating Agile as a company-wide philosophy. Why does this happen? Why do we keep hearing the same question in Agile conferences - "where are the managers?" Why does Enterprise Agile seem like an unachievable goal? And most importantly, what can we do about this gap that often manifests itself between organizational management and Agile teams? This session will address this topic by going through 4 distinct parts:
1. Are companies starting off their Agile change initiatives with the correct mindset (and goals)?
2. Experience in implementing Enterprise Scrum in large Belgian organizations (bpost and Belgacom)
3. Retrospecting on successes and exploring the root causes for problems and difficulties experienced in these cases
4. Proposing actions, behaviors and community activities to effectively close the gap The session will be a mix of presentation and interactivity as we explore the root causes and implications behind this challenging issue.
The algorithm to (learn to) write perfect code - Pascal Van Cauwenberghe
What's your first reaction when someone finds a bug in your application?
Sadness? Anger? Pain? Rage? Someone dares to criticize my baby?
Why don't you feel thankful, happy and energized?
Every reported bug is an opportunity to improve your product, your team, your way of working and yourself.
We'll walk through how one team solved one tiny bug. On the way, we'll see a number of techniques you can apply immediately with your team.
You'll go away with a simple 11 step algorithm to (learn to) write perfect code.
And maybe your team will become one of those teams who have so few bugs that they celebrate each bug report....
Warning: the techniques are both simple and very hard. It's a slow and expensive way of writing software. But every other way I've seen is even slower and more expensive...
Taking baby steps - Erik Talboom
How often do you commit to source control? Do you also have the feeling that you want to do too much? Do you split up your commits enough? Do you really take the smallest step possible before committing? We human beings are not that disciplined in general.
This session will help you keep that discipline and will also show you that you are not taking the smallest step possible. If you want to know more about this session idea: http://talboomerik.be/2012/01/16/taking-baby-steps/
Lessons learned from a Scrum Master - Alan Hortz
You have been appointed to your new role within the organization, Scrum Master, Congratulations ! It is not an easy role and there is a long to way to go. Alan Hortz wants to share with you the lessons he learned from the role and from being part of a scrum team without being the team leader.
The virtues of emergence - Christophe Addinquy
The emergent thinking is one of the hardest concept to understand. Often restricted to architecture considerations, this way of thinking is even reneged by non or fake agilists. This talk will show that emergence, beyond its way of thinking is a fundamental mechanism of agile projects, well beyond architecture considerations : to understand problems, the way teams work and even enterprise strategies. We'll see that emergence surpass the agile projects field and also applies to unsuspected domains.
Learning How (and why) to Estimate User Stories - Stephane Rondal
Experience has shown me that in most projects, be them Agile or not, user stories are not being estimated. Is this your case too? Actually, there's no need to estimate user stories. Lean principles even drive us to consider such estimation to be a waste. Well, now you have an excuse for not having estimations ;-) but usually management and/or customers don't see it this way, and do require estimations in order to calculate a release date for the project.
The good thing is that estimating user stories does not need to be painful. In fact, Agile techniques exist that are simple, quick, surprisingly efficient and even fun! During this session, you'll learn about story points, velocity, planning poker, etc. A small workshop will allow you to experiment live with these techniques. And even if you're already familiar with the above techniques, or if you are more into Kanban/Continuous delivery rather than Scrum/Iteration-driven, you'll see other/simpler ways to reach the same goal.
Agility at large scale : a return on experience - Mathieu Depriée & Hervé Lourdin
A software project implying 80 people, divided in 9 teams across 4 countries. A product that must sustain an activity of more than 5'000'000 sale transactions per day. A first deployment to production expected 6 months after project startup. And new features every 2 months. Who said that Agile was not adapted to large projects ? We will share with you our experience on a project involving a rollout of agile methodologies at large scale : feature-teams, communities of practice, switching to continuous stream of work without iterations, using lead-time metrics, frequent delivery and deployment to production in a single click, collaborative decision-making... What you will learn:
- Our "do's and don't's" about agile methodologies when applied to large projects
- The organization models we put in place
- Our best practices to keep the stream under control in a large project
- Key tools and skills to start such a project.
Introduction to Scrum, the most used Agile Method, through Games - Bruno Sbille
Scrum is the most used Agile Method to manage and realize projects.
Via this practical Workshop, we will simulate a project. Participants will work as a team using Scrum Principles and Values.
The objective is to:
- Experiment what it feels to work in Scrum Mode
- Learn about the Scrum Framework
It will give you an introduction of what it's like to work using Agile Methods. It will also give you some "comparison" points with others Project Management methods like Prince2 et PMI.
To achieve those goals, we will use Agile Games (same philosophy as Serious Games)
How 146 people created 13 projects - Yves Hanoulle
I have created lots of online collaborations: - the agile conference calendar - the retroflection of the day - who is agile - Agile Thursday quiz etc... In this presentation I will talk about the 146 people that helped me in these projects, what I have learned about teams & projects by doing these projects.
The Agile Tipping Point - Ron Enriga
This session is based on the New York bestseller "The tipping point" by Malcolm Gladwell. We will use the practicle examples from the book to have a discussion on finding discriminators that can help in coaching an organisation to a higher performance level. The session is an interactive workshop with room for bringin in examples from the audience.
The goal of the session is to determine a concrete plan for each participant. Participants are invited to think of their own environment to see if we can find the factors that might reach a tipping point in their organisation. We will discuss a case in the workshop as an example.
Organize effective meetings and rituals - Céline Stauder
Have you ever felt that your planning sessions are too long and heavy; that your retrospectives are not dynamic; that you don’t know why you are in this meeting; or the participants prefer playing with their phones to participating?
If it’s the case then you are the right person to be in this workshop. You’ll learn several tricks and practices to boost the efficiency of your meetings/workshops/rituals.
TDD by example - Pierre-Emmanuel Dautreppe
You may have already heard about Test Driven Development. It sounds nice, but how can we test something that does not exist (yet) ?
Let’s explore together the benefits of testing (unit testing or UI testing) and let’s see in practice how we can set up TDD in our project.
This session will be split in two parts:
A bit of theory:
- Why do we test?
- What is TDD and what are his benefits?
- This code is not “testable”!
A lot of practice
- A short presentation of a Unit Test framework
- Let’s do katas! Demo of the TDD cycle : test, develop, refactor, commit
- ATDD (Acceptance TDD) : there are many ways of doing ATDD. Let’s explore one technic, that provides high level code, readable to everyone.
All demo will be done using C# and the .NET testing tools (MsUnit and CodedUITest).
How to do great Retrospectives! - Steve Conard
One of the most important parts of Scrum are the Retrospectives held at the end of every sprint. But how do you ensure that these meetings are varied and do not become boring? How to get to concrete results that make a real difference? In this session you will learn tools and techniques to organize fun and effective Retrospectives. Guided by our experienced Scrum coaches, participants will share ideas and best practices on how to make Retrospectives kick ass!
* Get more insight in the possibilities for organizing interesting Retrospectives
* Share ideas amongst the participants
* Hear real-life examples and opinions about Retrospectives Target Audience Everybody interested in Scrum and improving its Scrum implementation through Retrospectives is welcome! Session Outline Our goal is to define and discuss how to run Retrospectives that are fun, interesting and effective during all sprints in the project. After an introduction on the subject, participants will be divided in small groups to do an actual Retrospective, focused on sharing experiences and ideas to improve Retrospectives . At the end of the session we will debrief results and draw conclusions on how to run the best Retrospectives.
* Brief presentation about retrospective (15 min) Set the stage, Gather data, Generate insights, Decide what to do, Closing
* Short sprint were the the participants can compete with each other. They will build a tower or paper plane. (15 min)
* Retrosession (30 min) Then the retro's will start about the sprint they just did. Each group have to choose a Scum Master who will facilitate their retro. In the room will be mini manuals available about techniques they can use during the retro. Of course the groups are free to use other techniques if they like.
* Teach back session among the groups (30 min) What did each group learned in the retro session. What was their experience?
Mission to Mars - Pierrick Revol
"Mission to Mars" is a brand new game simulating the rocket construction by a team. You will play one of the 5 characters: Nadia the electronic, Jane the architect, David the tester, Steve the developer or Omar the junior.
Don’t mention the war! - Wim Boolen & Ben Cassiman
The Agile Manifesto states its very first value as: “[We value] Individuals and interactions over processes and tools”. Hereby the Agile community captures the importance of communication. In many teams - and even more so in Agile teams – communication can turn into a major obstacle, thus blocking the transition. Make sure you fix this obstacle first before moving on. This playful workshop encourages teams to experience simple but profound lessons in the psychology of communication.
It will give you insight in your communication style and how to align your communication style to others. And it demonstrates how balanced communication can truly build an Agile team. All (Agile) team members, team leaders, Scrum masters and their product owners are invited to participate.
Hard Choices - Julien Biezemans
We are all in debt. We all have dark bits in our codebase or spaghetti code. Someday, we have to pay it back. This is not only a developer issue: everyone is concerned.
In this session, you will understand what technical debt is and learn how to deal with your technical debt and the involved trade-offs.
After a short presentation about technical debt, you'll experience the tough decisions that are related to it in a hands-on session based on the Hard Choices board game.
The Hard Choices game simulates a software development process. When you start a project you want to be first on the market and release a quality product to delight your customers. The game will put you in front of the difficult decision between taking a shortcut that gives you an advantage over your competitors or gaining more knowledge. It's all about strategy and being conscious of the accumulated debt.
We'll then follow up with an open discussion about strategies to avoid or recover from technical debt.