Subscribe: Thinking for a Change
http://blog.nayima.be/feed/atom
Added By: Feedage Forager Feedage Grade B rated
Language: French
Tags:
agile tour  agile  brussels  bug  conference  days  des  les  people  session  sessions  team  time  tour brussels  tour 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Thinking for a Change

Thinking for a Change



Treppenwitz in public



Updated: 2015-05-28T09:39:21Z

 



Call for sessions XP Days Benelux 2015

2015-05-28T09:39:21Z

XP Days Benelux is an international conference where we learn to bring software to life and grow mature systems that support business needs. It provides an excellent environment for exchanging ideas, hands-on exercises and extreme experiences. What are we looking for? What are you looking for? What would make it a WOW session for you and our participants? We’re [...]XP Days Benelux is an international conference where we learn to bring software to life and grow mature systems that support business needs. It provides an excellent environment for exchanging ideas, hands-on exercises and extreme experiences. What are we looking for? What are you looking for? What would make it a WOW session for you and our participants? We’re interested in: Experiences with new and old techniques. What worked; what didn’t? Why? What have you learned? Unexpected ideas from other disciplines and sciences. How can we cross borders? What lessons have we missed? How can we collaborate better with people from other disciplines and departments? Ask for help from other participants. What scary problems confront you and your team? People from outside IT with an interesting story. What can we learn from their experience? Pushing the limits of techniques and organisations, doing the “impossible”. How far can you go if you challenge commonly accepted assumptions? Back to basics. What happens if we really take the Extreme Programming values of Simplicity, Commmunication, Feedback, Courage and Respectseriously? Taking back agile. What does “agile” really mean to you and why is it important? Questioning agile. Where, when and why would you not use agile methods? Why? What can we learn about context and applicability? The XP Days community loves highly interactive sessions where everyone participates and learns from each other. During review and selection, your session will receive bonus points when… … you have no slides. Think outside the box and sharpen your story telling skills. … it appeals to both technical and functional people. Involve the geeks, challenge the managers. … it has the “XP Factor”. Is it entertaining and crazy? Does it take people out of their comfort zone? … you’ve had a dry run. Did you join one of our try-outs? Did you send a video introduction? … your subject is fresh and original. Maybe something outside the domain of IT? … it has an original format. Doing something with fruit? Are there any sports involved? Great! … your session poses a question instead of giving an answer. … if you’re new to presenting at XP Days. First timers receive a warm welcome… How does it work? You propose your idea for a session: a title and a short description.From then on, organizers and session proposers work together to refine and improve your proposal, adding more information and improving the description and session content. We’ll give feedback and provide opportunities for try-outs. In return, we expect from you that you help others to turn their idea into a WOW session. Yes but, I haven’t presented at a conference before. You don’t need to be an experienced presenter, you “just” need one good idea or question to start with. And then you iterate and improve your idea with the help of the other presenters and the organizers. We offer coaching for first-time presenters. Contact sessions if you want help proposing and refining your session. Submit your proposal now. You have until July 5th 2015 to propose your idea. The sooner you send in your idea, the more feedback you will receive. [...]



Call for sessions Agile Tour Brussels 2015

2015-05-28T09:35:59Z

Agile Tour Brussels is calling for speakers! Agile Tour Brussels is one of the biggest agile conferences in Belgium. Last year we gathered 250 attendees and speakers from Belgium, France, U.S, U.K, Luxemburg, Netherlands and Sweden to share our passion for Agile. The purpose of this conference is to gather in one place Agile practitioners and [...]

(image)

Agile Tour Brussels is calling for speakers!

Agile Tour Brussels is one of the biggest agile conferences in Belgium. Last year we gathered 250 attendees and speakers from Belgium, France, U.S, U.K, Luxemburg, Netherlands and Sweden to share our passion for Agile. The purpose of this conference is to gather in one place Agile practitioners and people wanting to know more about Agile.

At Agile Tour Brussels you will meet a mix of attendees who are either completely new to Agile, experienced or experts.

This year we’re going to have different tracks, and for each of these we’re looking for two kind of sessions: Interactive Talk (Presenter is speaking for most of the time with audience interaction) or Workshop (Primarily focused on hands-on participation with the audience).

Track 1: Experience reports.

Tell us your success or failure stories about Implementing Agile in Belgium (or in Europe), What is (not) working for you? If you’re an agile coach or facilitator, bring your client with you!

Track 2: Pragmatic Track

We’re looking for small changes or fundamentals, pragmatic things that work. How do you gather requirements? How do you run an outstanding retrospective? In this track your participants will learn something they can apply the day after. It can be technical, soft-skills or a process you use.

Track 3: Let’s Play together

This Track is for Agile Games and Serious Games. It’s also the opportunity to suggest “BootCamp” sessions like Introduction to [put Agile method here] or how to estimate with Agile,…

Track 4: Agile Management

What’s the role of Managers in Agile? What’s an Agile Manager? What’s an Agile organization? This track will cover subjects such as Management 3.0, Flat organizations, Evidence Based Management,…

Track 5: Various

Do you have a favourite subject you’d like to talk about, a kick-ass workshop you’d like to run, a theme you’d like to share? This track is for you!

All Agile methods are welcome: Scrum, XP, KanBan, Lean, Devops, Leadership, Lean Startup, Coaching, System thinking, Product Aspect, Agile outside IT.

We are looking for different levels of sessions: for beginners, practitioners and experts. We welcome experienced as well as new speakers.

How to submit a session?

To submit a session, fill in the form located here: http://at2015.agiletour.org/fr/callForSpeaker.html

(you can log into the website with your existing account or create a new one).

Tips for a successful submission:

  • Don’t forget to specify that you’re applying for Agile Tour Belgium – Brussels
  • Make sure you’re in the call for speaker of Agile Tour 2015 (links to the previous editions could still be active in the platform)
  • Specify the size of the audience you’d like to have for your session
  • Sessions must be in English
  • We would prefer to have session of 1 hour maximum
  • Deadline for submission: 10th of July 2014

All information about the event will be published on http://www.atbru.be

If you cannot make it, you can still support us by tweeting about #atbru, blogging, speaking about our event.




Mini XP Day Benelux 2015

2015-02-11T13:18:59Z

[ April 3, 2015; ] April 3, 2015 in Mechelen, Belgium Each spring we rerun the best sessions of the previous XP Days Benelux at the "Mini XP Day". This year we have 11 sessions that cover: Improving testing, design and coding skills by "programming people" Honing your Test Driven Development skills Recruitment techniques Going from idea to business value Using feedback loops in Scrum Improving the way you [...]

April 3, 2015 in Mechelen, Belgium

Each spring we rerun the best sessions of the previous XP Days Benelux at the “Mini XP Day“.

This year we have 11 sessions that cover:

  • Improving testing, design and coding skills by “programming people”
  • Honing your Test Driven Development skills
  • Recruitment techniques
  • Going from idea to business value
  • Using feedback loops in Scrum
  • Improving the way you work and the way you work with others
  • Managing agile transitions
  • How students and teachers apply “EDUScrum” in school
  • Defeating the dark forces that hold you and your team back from taking action

There’s something for everybody who’s interested in agile, development and systems thinking.

Don’t take our word for it

Have a look at the  feedback from participantsphotos and articles about the conference.

Don’t wait too long to register for the conference, as it usually sells out.

See you there!

(image)




We’re off on an adventure!

2013-12-27T17:39:43Z

The Dream Team Nightmare It took a while to arrive because the book was out of stock at Amazon, but it’s finally here, just in time for the holiday break: Portia Tung‘s “Dream Team Nightmare“! I sat down with a cup of coffee and started to read the book. Portia’s writing style is engaging and lively with [...] The Dream Team Nightmare It took a while to arrive because the book was out of stock at Amazon, but it’s finally here, just in time for the holiday break: Portia Tung‘s “Dream Team Nightmare“! I sat down with a cup of coffee and started to read the book. Portia’s writing style is engaging and lively with lots of dialogue and very short chapters. At the bottom of the chapters you have to make a choice and then go to a designated page. I’ve been on agile projects for years, so I expected to breeze through the book. After all, most teams face the same problems. I’ve solved them many times. Why should this “Dream Team” be any different? After only a few pages I read Patrick [who hired you as an agile coach] asks his secretary to escort you out of the office. Before you know it, you’re back on the street. It feels like you’ve been punched in the gut. Thoughts swirl in your head. Should have. Would have. Could have. You decide to take time out to reflect on what happened. You’re not quite ready to give up doing a job you love. not yet. THE END Fired! On my first day. Game over. Do you want to play again? Of course, but now I’ll make smarter choices. And… I was asked to leave the Dream Team and see if things would go better with another team. THE END. “If at first you don’t succeed, stubbornly try again and again”, that’s my motto. So, one more try. Aha! We come to a part where my mission is described as a user story with acceptance tests. That will help me to understand better what’s expected. I restart the book and start working with the team. I flip backwards and forwards as the book directs me to see the consequences of my choices. It’s getting smoother. And then there’s a conflict with one of the team members. At the end of the 5 days I present my recommendations. And then… nothing happens. THE END. This agile coaching lark is harder than it looks. This is frustrating. I’ve only scratched the surface of the book, read a few chapters and each time I reach a dead end. Reminds me of some projects I’ve been on. And then I have a brilliant idea. What would Portia do? I’ve been lucky to work with Portia and see her at work. I will restart the last time and at each choice ask myself “What would Portia have done in this situation?” Portia would talk to everybody to understand what motivates them help the team to make their own decisions reach agreement on the value we’re creating get a good understanding of where we are define goals together and clarify them with testable acceptance criteria take some time to reflect regularly help the team to create and explore options lighten up the mood with silly exercises like “profile cards“, cookies and team lunches I can do that. It’s just a matter of taking a bit more time before making a decision. Let’s start again, from the top. This time, with the help of Portia (sometimes in the role of Jiminy Cricket to keep me on the straight and narrow, sometimes as the Blue Fairy who grants wishes and saves the day) I progress through the book. There are still a few choices, but fewer and fewer. The team starts working together to visualize their situation. Faced with the enormity of their task, they feel demoralized. We come up with three options to deliver value and involve the Product Owner. And there it gets tricky. If I’m not careful, the unspoken simmering conflict between team and product owner/management erupts again: the company needs more than the team can deliver; the tea[...]



Agile Tour Brussels 2013

2013-08-10T16:31:14Z

[ September 27, 2013; 8:00 am to 7:00 pm. ] What is Agile Tour Brussels? The purpose of Agile Tour Brussels is to gather in one place Agile practitioners and people wanting to know more about Agile. At Agile Tour Brussels you will meet a mix of attendees who are completely new to Agile, experienced or experts. See you in Brussels on Sept 27, 2013 The program has been [...]

What is Agile Tour Brussels?

(image) The purpose of Agile Tour Brussels is to gather in one place Agile practitioners and people wanting to know more about Agile. At Agile Tour Brussels you will meet a mix of attendees who are completely new to Agile, experienced or experts.

See you in Brussels on Sept 27, 2013

The program has been published and registration is now open.

The program features 5 parallel tracks with 30 sessions by speakers from Belgium and abroad. The conference is held at the EPHEC school in Brussels.

See you there

I’m helping out with the organisation, mainly doing the administration and registration. You’ll find me at the registration desk. In the afternoon I’ll present a session about how to use Real Options to make architectural decisions. This will be the first time I present this session in English, after presenting it in french and dutch.




XP Days Benelux 2013 – Call for session proposals

2013-06-05T06:02:06Z

[ November 28, 2013 to November 29, 2013. ] XP Days Benelux is an international conference where we learn to bring software to life and grow mature systems that support business needs. It provides an excellent environment for exchanging ideas, hands-on exercises and extreme experiences. The best way to learn is to facilitate a session. We like sessions where you explore ideas as well as questions. The conference will [...]XP Days Benelux is an international conference where we learn to bring software to life and grow mature systems that support business needs. It provides an excellent environment for exchanging ideas, hands-on exercises and extreme experiences. The best way to learn is to facilitate a session. We like sessions where you explore ideas as well as questions. The conference will be held on 28 and 29 November, 2013 in Mechelen, Belgium. The best way to learn is to facilitate a session at XP Days! We’re looking for sessions where you explore ideas as well as questions. Sessions that dig deeper, going beyond the basic techniques and practices. We really want to find out why/how things work or don’t work. We invite you to propose: hands on coding/design/architecture sessions; discovery sessions – open ended workshops that explore new topics, common problems, promising techniques, or burning questions; experiential learning sessions; get people learning by doing & reflecting; for example games or simulations. We’re not only interested in agile and software related topics but we also want to explore boundaries and cross borders. What can we learn from other disciplines or sciences? Available timeslots are 75 and 150 minutes. We also welcome short experience reports (30 minutes) that focus on what didn’t work and why. Do you have an interesting story, idea or question? Send us your session idea today. What’s so special about XP Days? For one thing, we constantly try to apply XP, agile, lean, systems thinking, theory of constraints and all the other stuff we talk about. It wouldn’t be an agile conference if it wasn’t organised by using agile values, principles and techniques. For example: how is the way we build the program agile? Collaborating to get the best possible sessions We don’t think BDUF is appropriate or possible, not even for a session description. Therefore, we ask session authors to send in a simple proposal: title, subtitle, presenters, description. It’s the equivalent of a story card: the promise for a conversation about the session. Once the proposal is sent in, the author(s) can incrementally fill in more information, as the session becomes clearer. There’s a separate deadline for submitting proposals (July 13th) and finalising the proposals (August 28th), to avoid “student syndrome” and last-minute session hurried submissions. Within those two timeboxes, the authors work at their own (sustainable) pace. Session authors help other session authors by asking questions and giving feedback using the “Perfection Game“. The proposal authors (and the conference organisers) act as “peer coaches“. Through the magic of questions and feedback, the proposal author iteratively improves their proposal(s). Aren’t session authors helping their “competitors” in the race for a place in the program? We typically get 3 proposals per slot, so the competition is fierce. Well, nobody said collaboration was easy. In the end we all benefit from a better conference program. And the organisers see who applies the agile values and who just talks about them. Isn’t this coaching only useful for beginners? It certainly helps new presenters to marshal their ideas. But, as we’ve experienced while pair programming, experienced presenters get new insights and clarity when “juniors” ask naive questions. The most powerful coaching questions focus on goals[...]



Ignore the cost accountants at your peril, because they won’t ignore you

2013-05-30T16:32:47Z

Why should I learn about cost accounting? It may not be immediately obvious, but the way your company manages its finances, costs and budgets has a profound effect on the way projects or products are started, run and terminated. You may have been in situations where you sat back in amazement at some incomprehensible management decision [...]

Why should I learn about cost accounting?

It may not be immediately obvious, but the way your company manages its finances, costs and budgets has a profound effect on the way projects or products are started, run and terminated. You may have been in situations where you sat back in amazement at some incomprehensible management decision and thought “what were they thinking?”

They were probably thinking about budgets and costs. You will be surprised again next time unless you learn to understand and dialogue with your CFO and cost accountants.

Fun with cost accounting

Pierre Hervouet and I have created a session that explains the basics of cost accounting (based on making and pricing cocktails) and presents three alternative views you may find useful:

  • Throughput Accounting
  • Lean Accounting
  • Beyond Budgeting

The session doesn’t certify you as an accounting master, but it provides food for thought and pointers to plenty of material you can dig into if you want to know more. The materials (currently only in French) are published on the agilecoach site.

Join the conversation

Why don’t you go see your CFO or cost accountants today? Ask them what’s keeping them up at night. You may discover that you face much the same issues and that the solutions are similar. Yes, yes, accounting and budgeting are getting more agile, more lean!

The Agile Alliance has a new “Agile Accounting Standards” program to “Engage with FASB’s Emerging Issues Task Force to promote and develop an Agile Accounting Standard that will better define and standardize internal IT development costs for organizations that use an iterative or agile software development methodology” because  “The phased gate language [of the current standard] results in significant confusion and challenges of interpreting how to map the iterative work that happens throughout an Agile project lifecycle and is becoming an increasing urgent issue.




Call for Sessions Agile Tour Brussels 2013

2013-08-10T16:12:12Z

The Agile Belgium Community is calling for speakers for the Agile Conference: Agile Tour Brussels 2013. This event will take place on the 27th of September in Brussels Belgium. Deadline for submission:  20th of June 2013 What’s Agile Tour Brussels? It’s the 2nd edition of the conference Agile Tour Brussels. Last year we gathered attendees and speakers from [...]

The Agile Belgium Community is calling for speakers for the Agile Conference: Agile Tour Brussels 2013. This event will take place on the 27th of September in Brussels Belgium.

Deadline for submission:  20th of June 2013

What’s Agile Tour Brussels?

(image) It’s the 2nd edition of the conference Agile Tour Brussels. Last year we gathered attendees and speakers from Belgium, France, the Netherlands and Switzerland to share our passion for Agile. The purpose of this conference is to gather in one place Agile practitioners and people wanting to know more about Agile.

At Agile Tour Brussels you will speak to a mix of attendees who are either completely new to Agile, experienced or experts.

We are looking for any kind of sessions (Lecture, interactive talk, workshop, technical,…) on any topics like Scrum, XP, KanBan, Lean, Devops, Leadership, Lean Startup, Coaching, System thinking, Product Aspect, Agile Games,…

We are looking for different levels of sessions, sessions for beginner, advanced and expert. We are also looking for new and experienced speakers.

How to submit a session?

To submit a session, fill in the form located here: http://at2013.agiletour.org/fr/callForSpeaker.html

If you never registered to the website agiletour.org, you will be asked to create an account.

Tips for a successful submission:

  • Don’t forget to specify that you are applying for Agile Tour Belgium – Brussels
  • Specify the size of the audience you’d like to have for your session (e.g < 100 persons)
  • Sessions must be in English
  • We would prefer to have session of 1 hour maximum

All information about the event and previous edition can be found on www.atbru.be

If you have any questions, feel free to drop an email at bruno@atbru.be

Thanks in advance for your support!

The Agile Tour Brussels Organization Team.




A simple property Dialog – An alternative approach

2013-04-02T16:46:45Z

Performing a Root Cause Analysis for a simple bug takes too much time In a previous post I described how we performed a root cause analysis for a simple bug: one incorrect value  in a dropdown. Performing such a heavy analysis (which generates a lot of rework) may not be appropriate for every bug. Here’s how another [...]Performing a Root Cause Analysis for a simple bug takes too much time In a previous post I described how we performed a root cause analysis for a simple bug: one incorrect value  in a dropdown. Performing such a heavy analysis (which generates a lot of rework) may not be appropriate for every bug. Here’s how another team handled a very similar bug: one value missing from a dropdown. The fast way to deal with simple bugs There’s a bug: in one screen one of the dropdowns misses one value: “X”. This bug is unexpected: in all other screens the behaviour of the dropdowns is correct, each of them contains “X” as the final and default value. This bug only appears in one screen. Why only this screen? What’s so special about this screen? Isn’t this the same code for all dropdowns with the same behaviour? The bug is reported during internal testing. The bug can be repeated very easily. Developers grumble (I told you the “Thank you” step in the  algorithm to write perfect code was difficult!) A developer takes the bug and fixes it: an extra value “X” is added to the dropdown in the screen Tester validates: go into the screen; open the dropdown; the value “X” is there. Bug closed. Software gets shipped to customer Done. Next bug! Easy. A few days later… Customer files a bug report: each time they enter this specific screen an “X” gets added to the dropdown. Enter the screen twice, you see “X” “X”. Enter again, you see “X” “X” “X”. And so on… Developers grumble: “Not another stupid bugreport!“ A developer takes the bug and analyses it. “Some idiot has added ‘X’ to this dropdown. Let’s remove that.“ Tester validates: go into the screen; open the dropdown; no “X” is added. Bug closed. Software gets shipped to customer Done. Next bug! Easy. Only took a few minutes to fix and (a few days later) a few minutes to test. And another release to build, ship and install. A few days later… Customer reopens their bug report: when they enter the screen, there is no “X”. To be clear: they expect exactly one “X” in this dropdown (and all similar dropdowns in other screens). Not zero. Not an infinite number. Developers grumble. “When will they make up their mind?“ Developer takes the bug and fixes it: an “X” is added to the dropdown unless there’s already an “X” in the dropdown Tester validates: go into the screen, one “X”; go into the screen again, still one “X”; go into the screen again, still one “X”; go into other screens; go into this screen, still one “X”. Stop the application. Restart the application. Go into the screen, one “X”; go into the screen again, still one “X”. Bug closed. Software gets shipped to customer Done Easy. Only took an hour or two to fix and (a few days later) an hour to test. And another release to build, ship and install. And they all lived happily ever after Except for the customer who grumbles “how can I trust them with the important stuff if they can’t get the simple stuff right?” Except for the developers who grumble “how can we get any work done if we have to keep fixing these stupid bugs?” Except for the testers who grumble “why do we have to retest every bugfix a thousa[...]



A simple property Dialog – Adventures in Root Cause Analysis

2013-04-08T11:20:53Z

I’ve been going on a bit lately about the value I get from of performing “Root Cause Analysis” when I encounter a bug. Great! another bug from AgileCoach.net A simple algorithm to write perfect code You don’t have to watch the presentation. The message is this: each time there’s a bug: Someone finds a problem and reports [...]I’ve been going on a bit lately about the value I get from of performing “Root Cause Analysis” when I encounter a bug. style="border: 1px solid #CCC; border-width: 1px 1px 0; margin-bottom: 5px;" src="http://www.slideshare.net/slideshow/embed_code/14986435" height="356" width="427" allowfullscreen="" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"> Great! another bug from AgileCoach.net A simple algorithm to write perfect code You don’t have to watch the presentation. The message is this: each time there’s a bug: Someone finds a problem and reports it to you Thank the reporter Reproduce the problem Add (at least) one failing test Correct the problem Rerun all tests and correct your correction until the tests pass Improve your tests Improve the way you write tests Look for similar problems. Goto 2 Make this type of problem impossible Perform the actions that were identified during the Root Cause Analysis  But that’s just common sense! We’re all agile lean continuously improving test driven extreme programmers, aren’t we? Doesn’t everybody do this? Yes… but… It takes too much time We can’t do this for every bug because we’ve got too many bugs We don’t want to waste time on bugs, we prefer to spend time adding valuable features As Dijkstra said: “ program testing can be a very effective way to show the presence of bugs, but it is hopelessly inadequate for showing their absence.” Just a little taste The presentation tells the story of a team that performed a Root Cause Analysis. Here’s another team’s story: Coach: Can we try a small Root Cause Analysis experiment? Dev: Yes, but… we don’t have a lot of time. Coach: Do you have one hour? We can timebox the experiment. Dev: Sure, but… you can’t do anything useful in one hour. Coach: Maybe you can’t; maybe we can. Dev: ??? Coach: Have you seen any interesting bugs lately? Dev: Well, I just fixed a bug. But it’s so trivial you won’t discover anything useful. Coach: Thank you! Let’s see. I love clear bug reports First we look at the bug report:GIVEN a swizzled foobar (*) WHEN I change its properties THEN I EXPECT to be offered a choice between 'A', 'B' or 'Z' for the status BUT I'm offered 'A', 'B' or 'C' (*) all names of domain objects have been changed to protect the innocent and the guilty  Let’s apply the algorithm Coach: have you thanked the reporter yet? Dev: no… Coach: Let’s do it now. Dev: ok… Dev: Hi, I just called to thank you for reporting the bug about the property dialog of the swizzled foobar. Product Manager: OK… Dev: The report was so clear the bugfix almost wrote itself. Thanks! Product Manager: You’re welcome! Coach: OK. We’ve now done the hardest part; Let’s do the next steps. Next step: reproduce the problem. That’s quite easy: start up the application, select a foobar, swizzle it and open its property dialog. Look at the dropdown control for the status: it presents options ‘A’, ‘B’ and ‘C’. Coach: We have a manual test procedure. Can we automate this test? Dev: No. This is user-interface code. We’ve performed some experiments earlier and decided that it wasn’t worth the time and effort to create and[...]



Devoxx FR 2013 presentation available

2013-04-02T11:25:32Z

My Devoxx presentation on Real Options is now available on Slideshare: Devoxx fr 2013 Real Options – Comment et Quand (ne pas) prendre des décisions from AgileCoach.net

My Devoxx presentation on Real Options is now available on Slideshare:

src="http://www.slideshare.net/slideshow/embed_code/17904608" width="427" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC;border-width:1px 1px 0;margin-bottom:5px" allowfullscreen webkitallowfullscreen mozallowfullscreen>




Devoxx Paris 2013

2013-03-21T16:11:59Z

[ March 29, 2013; ] Decisions, decisions, decisions On Friday march 29th I'll present a session about Real Options and other techniques to take better architectural decisions at a better moment. Billions of years of evolution have equipped us with these wonderfully irrational brains that sometimes get in the way of making good decisions. With a few simple but counter-intuitive techniques [...]

Decisions, decisions, decisions

On Friday march 29th I’ll present a session about Real Options and other techniques to take better architectural decisions at a better moment. Billions of years of evolution have equipped us with these wonderfully irrational brains that sometimes get in the way of making good decisions. With a few simple but counter-intuitive techniques we can make our decisions a bit less stressful and more useful.

See you in Paris.

(image)




Agile France 2013

2013-04-05T08:25:51Z

[ May 23, 2013 to May 24, 2013. ] La conférence Agile France 2013 se tiendra les 23 et 24 mai 2013 dans le cadre agréable du Chalet de la Porte Jaune, près du chateau de Vincennes. Vous avez encore jusqu'au 2 mars pour envoyer vos "pitch" pour des sessions. Il ya déjà plusieures excellentes propositions. J'envoie ma proposition dans quelques instants. Qu'est-ce que vous attendez? The [...]

La conférence Agile France 2013 se tiendra les 23 et 24 mai 2013 dans le cadre agréable du Chalet de la Porte Jaune, près du chateau de Vincennes.

Vous avez encore jusqu’au 2 mars pour envoyer vos “pitch” pour des sessions. Il ya déjà plusieures excellentes propositions. J’envoie ma proposition dans quelques instants.

Qu’est-ce que vous attendez?


The conférence Agile France 2013 will be held on May 23rd and 24th at the lovely Chalet de la Porte Jaune, close to the chateau de Vincennes.

You have until March 2nd to send in a “pitch” for a session. We’ve already received many interesting session ideas. I’ll send my proposal in a few minutes.

What are you waiting for?

(image)

Ils sont fous, ces agilistes!




Mini XP Day Benelux 2013

2013-02-25T15:16:17Z

[ April 26, 2013; ] April 26th in Mechelen, Belgium Mini XP Day reruns 12 of the best sessions from last year's program in 3 parallel tracks. The conference takes place in Mechelen in Belgium (between Brussels and Antwerp). There's room for 90 participants and the conference usually sells out. So register now to ensure you don't miss out on this great event. Picture from the "Product Box" session at XP [...]

(image) April 26th in Mechelen, Belgium

Mini XP Day reruns 12 of the best sessions from last year’s program in 3 parallel tracks. The conference takes place in Mechelen in Belgium (between Brussels and Antwerp).

There’s room for 90 participants and the conference usually sells out. So register now to ensure you don’t miss out on this great event.

(image)

Picture from the “Product Box” session at XP Days Benelux by Yves Hanoulle




Agile Open Belgium 2013

2013-03-21T16:10:21Z

22-23 March in Brussels, Belgium Agile Open Belgium is an open space conference in the tradition of Agile Open conferences. You determine the subjects on the program. Join us on 22 and/or 23 March in Brussels.

(image)

22-23 March in Brussels, Belgium

Agile Open Belgium is an open space conference in the tradition of Agile Open conferences.

You determine the subjects on the program.

Join us on 22 and/or 23 March in Brussels.




Agile Tour Brussels 2012 presentation

2012-11-04T16:51:54Z

[ October 26, 2012; 9:00 am to 7:00 pm. ] I'm Pascal, I'm a bug writer I started writing bugs when I was 15-16 years old. It all started innocently with some small BASIC programs on a home computer. But I soon moved on to the hard stuff: Assembler, Forth, C, LISP, Smalltalk, C++. Before I knew it I was working on products with several millions of [...]

I’m Pascal, I’m a bug writer

I started writing bugs when I was 15-16 years old.

It all started innocently with some small BASIC programs on a home computer. But I soon moved on to the hard stuff: Assembler, Forth, C, LISP, Smalltalk, C++. Before I knew it I was working on products with several millions of lines of code and tens of thousands of recorded bugs.

After discovering Extreme Programming I decided to kick the habit.

I want to share with you the eleven step algorithm I used to get better.

I’m Pascal, I’m a recovering bug writer

style="border-bottom-width: 0px; border-style: solid; border-color: #cccccc; margin-bottom: 5px;" src="http://www.slideshare.net/slideshow/embed_code/14986435?rel=0" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" width="512" height="421">




Conf Agile France 2011: Les bases des méthodes Agiles et Lean

2011-06-07T20:41:39Z

Six éléments essentiels La deuxième présentation à la Conférence Agile France 2011 proposait six bases essentielles pour mettre en place un environnement de travail Lean ou Agile. Comme toujours il y a de bonnes nouvelles et de mauvaises nouvelles: La bonne nouvelle: Lean et Agile ne sont pas de la magie, entre temps on sait pourquoi, où [...]Six éléments essentiels La deuxième présentation à la Conférence Agile France 2011 proposait six bases essentielles pour mettre en place un environnement de travail Lean ou Agile. Comme toujours il y a de bonnes nouvelles et de mauvaises nouvelles: La bonne nouvelle: Lean et Agile ne sont pas de la magie, entre temps on sait pourquoi, où et comment ça marche La mauvaise nouvelle: ce n’est pas compliqué, mais c’est vraiment dur de mettre en place les prérequis nécessaires. La présentation ne donne qu’un aperçu de chaque élément. Voici des ressources pour les 3 premiers élements, qui peuvent vous aider dans vos recherches. Les 3 autres éléments seront décrit dans un billet suivant. 1. La Théorie des Contraintes Originalement décrite par Eli Goldratt dans le roman “Le But”, cette théorie se résume très facilement: Le résultat de chaque système est déterminé ou limité par un de ces élements, le goulot d’étranglement La seule façon d’améliorer les résultats est de travailler sur le goulot. Améliorer les autres élements du système n’apportera pas de bénéfices, cela aura souvent un effet négatif! Comme mon grand-père savait déjà: “pour rendre une chaine plus forte, il faut renforcer le maillon le plus faible”. Le “Jeu du Goulot d’étranglement” vous fait vivre les conséquences qui vont souvent contre le “bon sens”. 2. Les Real Options Au lieu de prendre des décisions difficiles le plus tôt possible, comme nous encourage toute la littérature sur l’architecture informatique, il faut attendre jusqu’au “bon” moment pour prendre chaque décision. On peut calculer exactement quand c’est le bon moment: la date de livraison – le temps d’implémentation de l’option jusq’au moment de la décision on garde toutes les options ouvertes on utilise le temps gagné pour rechercher plus d’informations ou pour créer d’autres options on essaie de réduire le temps d’implémentation de chaque option afin de repousser vers l’arrière le moment de la decision L’heuristique que j’utilise: Une décision difficile à défaire doit être prise tard. J’essaie de réduire le temps d’implémentation pour avoir plus de temps de reflexion et évaluation. Une décision facile à défaire peut être prise tôt. J’essaie de convertir des décisions difficiles à défaire en décisions faciles à défaire. Exemples concrets: Les User Stories nous donnent l’option de prendre des décisions difficiles de planning et contenu du produit plus tard que d’habitude Du code clair, facile à comprendre, bien factorisé avec des tests automatiques nous permet de défaire des décisions de design et architecture à faible coût qu’on a fait auparavant pour implementer de nouveaux besoins Le tableau Kanban permet à l’équipe de voir les goulots en temps réel et de réagir en conséquent. L’article “Real Options Underlie Agile Practices” par Chris Matts (en anglais) explique les Real Options et le lien avec Agile et lean. Il y a un résumé des Real Options sur le site Agile Coach. 3. Gérer par la valeur, [...]



Conf Agile France 2011: Résolution des Conflits

2011-06-06T20:21:47Z

Résoudre les conflits sans compromis La semaine passée j’ai présenté comment résoudre les conflits avec le “Diagramme de Résolution des Conflits” à la Conférence Agile Paris. La présentation est disponible ci-dessous. Plus d’informations sont disponibles sur le site Agile Coach. Conflict Resolution Diagram Tutorial – French View more presentations from AgileCoach.net. A la fin de la présentation il y [...]Résoudre les conflits sans compromis La semaine passée j’ai présenté comment résoudre les conflits avec le “Diagramme de Résolution des Conflits” à la Conférence Agile Paris. La présentation est disponible ci-dessous. Plus d’informations sont disponibles sur le site Agile Coach. Conflict Resolution Diagram Tutorial – French View more presentations from AgileCoach.net. A la fin de la présentation il y a deux questions pour voir si vous avez compris la leçon: Est-ce qu’il est possible de former un gouvernement belge avec cet outil? Si oui, pourquoi? Si non, pourquoi pas? Est-ce que vous pouvez résoudre ce conflit récurrent entre Product Manager et Développeurs: Le Product Manager a besoin d’estimations et de planning très détaillé et fiable pour publier une roadmap qui dit quand quel fonctionnalité sera livrée quand ET livrer ces fonctionnalités comme promis Les clients, qui souvent sont des grandes entreprises avec plusieures filiales dans les monde et beaucoup d’utilisateurs, ont besoin de cette roadmap pour planifier quand ils vont implémenter une nouvelle version Les Développeurs sont “passés au Kanban”: ils ont arrêté de faire des estimations ou des plans. Cela prenait beaucoup de temps et ce n’était jamais correct. Les Développeurs “éliminent le gachis” parce qu’ils doivent aller de plus en plus vite pour satisfaire les requêtes d’un nombre de clients qui toujours croissant. Tout le monde veut livrer les fonctionnalités au client au moment où les clients attendent ces fonctionnalités. Vos réponses et questions dans les commentaires… D’abord essayez de clarifier le conflit. Puis, découvrez les suppositions derrière chaque étape du raisonnement. Translation I presented an interactive tutorial on how to apply the “Conflict Resolution Diagram” at the French Agile conference in Paris. You can see the English version of the presentation at the Agile Coach site. At the end of the French version of the presentation there are two tests to see if participants understood the tool: Can you use this tool to form a Belgian Governement. If yes, why? If not, why not? Can you resolve this common conflict between Product Manager and Developers: The Product Manager needs detailed estimates and accurate planning because she has to create a long-term roadmap which spells out which features will be delivered when AND deliver those features when promised to keep customers’ trust Customers, who are typically large multi-site companies with many users of the product, need the roadmap because they need to plan when they will roll out which version throughout the enterprise Developers have “gone Kanban” and have stopped estimating and planning because the estimates took too much time and were incorrect anyway Developers stopped estimating and planning to decrease waste so that they can keep up with the increased demand for features from the increasing user base The whole company wants to deliver the features customers ask for when customers expect them. Answers on a po[...]



Agile Belgium Drinkup June 2011

2011-06-04T11:57:50Z

[ June 8, 2011; 7:00 pm to 11:00 pm. ] Topic: This is an informal meetup of the Belgian Agile and Lean community. Come after work and meet people you usually only meet at conferences. Anyone interested in Agile or Lean can join. Add your name to the list to attend. Location: Foodsquare Rue du Marché aux Herbes 120 1000 Bruxelles Between Brussels Central station and the Grand' Place. See you there!

(image)

Topic:

This is an informal meetup of the Belgian Agile and Lean community. Come after work and meet people you usually only meet at conferences. Anyone interested in Agile or Lean can join.

Add your name to the list to attend.

Location:

Foodsquare
Rue du Marché aux Herbes 120
1000 Bruxelles

Between Brussels Central station and the Grand’ Place.

See you there!




Call for Session Proposals – XP Days Benelux

2011-04-26T20:01:43Z

Mechelen, December 1st – 2nd 2011 XP Day Benelux is an international conference about Agile methods, intended for people from all walks of life who are involved with IT. It provides a good opportunity for exchanging ideas and sharing experiences and is suited for both experienced participants and beginners in Agile methods. The focus of this [...] Mechelen, December 1st – 2nd 2011 XP Day Benelux is an international conference about Agile methods, intended for people from all walks of life who are involved with IT. It provides a good opportunity for exchanging ideas and sharing experiences and is suited for both experienced participants and beginners in Agile methods. The focus of this conference is on practical knowledge, real-world experience, and active participation of everyone. XP Days Benelux 2011 will have something for everyone. Sessions for people who are new to Agile, sessions for experienced people, a good mix of technical, experience, management and process sessions. We’ll have sessions on Agile in real life, stories of success and horror, hands on workshops, and sessions that will completely surprise you! You can be a contributor too We’re looking for enthusiastic people who want to lead these sessions. People who work in any role, business or form. People who are willing to share, and are prepared to learn. Reflective practitioners who are not only interested in quality work but also want to know why things work as they do. Are you new to presenting? Do you have a nice idea, but you don’t know how to shape it into a session? Don’t worry, we will offer lots of ways to help you: We have coaches who can help you create your session. Through our session proposal system you will get feedback that will help you shape your session We provide opportunities before the conference to try out your session. We have a set of personas to give you some idea of the type of participants you’ll meet at XP Days. Have you presented sessions before? The extensive feedback will give you an opportunity to improve your session further. And you can use your experience to help other presenters to improve their session. How to propose a session for XP Days Becoming an XP Days presenter is simple (but not easy): Submit a session idea (until July 9th, 2011) You’ll receive a login to our session improvement tool You complete your proposal and improve it with the feedback you receive (until August 27th, 2011) You give feedback on other proposals to help their presenters to create the best proposal they can Early September, the program committee selects the sessions for the program based on the following criteria: Quality of the session A balance of session subjects and formats Participation of the presenter in the improvement process Votes from everybody who proposed a session Important dates Now to July 9th, 2011: submit session proposals Now to August 27th, 2011: improve session proposals September 12th, program committee meeting September 19th, program decided Propose a session now to get as much time as possible to get feedback and improve your session. See you at the conference! [...]