Whose Project is it Anyway? Presenters: Bonnie Aumann, Rob Kinyon

From organizing the backlog of stories to choosing a branching strategy, developers and clients can find themselves wondering who’s really driving the project. These problems are only exacerbated when an outside team is brought into the client-space. In this session we will explore organizational patterns and anti-patterns, particularly focusing on conflict resolution, via improvisational role-playing.

The first principle of Agile is to deliver value to the customer. Understanding Business Value better can often do more than anything else to make your efforts better. We need to improve our Business Value Engineering.

In this Discovery Session, we intend to look at the principles and values that underlie Business Value and its uses. And we will look at how we practice Business Value Engineering throughout the life of the effort. Expect challenges, not pat answers. This discussion will enable you to improve your Business Value Engineering.

Presentation Description

The true measure of project progress is working software - or is it? Our team thought it was, and we were wrong. This is the story of our team, a team that set out to build a new order tracking system for a worldwide vehicle manufacturer, and failed.

Je viens de recevoir la note d’acceptation du comité de programme. J’accepte de faire cette présentation le jeudi 7 août, de 8h30 à 12h00. Je suis également prêt à refaire cette présentation le vendredi, le cas échéant.

Alain Désilets

“The hardest single part of building a software system is deciding precisely what to build.” — Fred Brooks

Résumé

Scrum focuses on collaboration with the customer, but what if your customer is actually a provider for yet another customer? Then who is your REAL customer? What if these two possible customers have a hostile relationship? Then who is your customer? These are the kinds of real world questions that we examine in this experience report.

The report describes a situation involving a complex customer relationship and the consequences of failing to identify the correct customer.

This workshop is aimed at exploring and understanding the customer role on Agile projects. It will answer several common questions about this role, like: What’s an agile customer? What’s the role of the agile customer? Why is this role so important? Is the agile customer one person or a team? What traits should a agile customer have? Why does the role break down? There will be a highly interactive breakout session that will bring different perspectives on the topic from the participants experience and tries to deepen the understanding of this important issue.

Extreme Programme exige du “Client XP” d’écrire des User Stories. Un format commun est “Comme <role> je veux <quelque chose> pour atteindre <un but>.” Est-ce que vous avez des difficultés pour trouver les roles, quelques choses et buts?

Est-ce qu’un client vous a déjà demandé d’implementer une solution, pour conclure “c’est bien ce que j’ai demandé, mais ce n’est pas ce dont j’ai besoin”? Est-ce que vous avez déjà eu de difficultés pour impliquer des intervenants importants dans vos projets? Est-ce que vous avez déjà eu de la peine pour vous mettre d’accord sur les critères de recette? Est-ce que vous avez travaillé sur un projet sans vision commune, où tout le monde allait dans une direction différente?

Si oui, la technique d’interview des “9 cases” peut vous aider à partir du bon pied.