Racontez vos outils

VersionOne, Rally, RTC, TFS etc

Ca vous parle ?

Les outils de gestion de backlog sont de plus en plus mis en avant. Exit le kanban mural quand une équipe est dispersée aux quatre vents. (Dommage quand même, il apporte beaucoup à l'animation d'une équipe co-localisée, y réfléchir à deux fois...)

Donc, on n'échappe rarement à l'outil de gestion de backlog. Se pose alors la question de la mis en œuvre de la méthode dans cet outil.

Une manière efficace que j'ai pu expérimenté est la forme user story. Les exemples suivant (in English) proviennent d'une thématique "agile pour système temps-réel", où les exigences normatives présentent de nombreuses contraintes et défis par rapport à l'agile "cœur de cible" (site web, système d'information, jeux vidéo etc), où on distingue la vision "système", "sous-système" et "software" et où les chaque activité de vérifiaction doit être menée par une entité tierse.

Voici donc quelques besoins vis-à-vis de l'outil, exprimés sous la forme user story. J'ai regroupé les stories par features (thèmes d'utilisation de l'outil)

Backlog preparation and planning

As a Product Owner, I want to associate Doors requirements to a backlog item in few clicks, in less than 5 seconds, so that I can redo that hundred times in a sunstainable way

As a Product Owner, I want to perform a roadmap so that I can define assign in releases

As a validation responsible, I want to perform a release plan so that I can assign stories in sprints

As a Product Owner, I want to perform a backlog review so that I can define work units for next sprints

As a Scrum master, I want to prevent a sprint to be between two releases, so that I can ensure the planning consistency by respecting agile principles

During sprints

As any team member, I want to filter the requirements of a document in Doors by sprint or release, so that I can identify quickly the document scope to be reviewed

As a test representative, I want to know my tasks in the development stream so that there is no confusion with my others tasks in the test stream

As a tester, I want to add a task in the sprint backlog of a development stream so that test failures/bugs can be investigated/fixed quickly

As any team member I want to manage defects (or group of defects) in the backlog so that I know the part of sprint n-1 corrections to be fixed during sprint n

Project control

As a Product Owner, I want to see to value delivered at the end of a release, so that I can control the actual project progress regarding the total value target to be delivered at the end (burn-up)

As a Scrum master, I want to see a burndown chart of a sprint, so that I know if we will reach the sprint target or not

As a Scrum master, I want to see a burndown chart of a release (counting the story points of work items and stories), so that I know if we will reach the release target or not

As a team Scrum master – validation responsible I want to plan a release without detailing work units of all sprints, so that I can leave the last sprint as stories form

As a Scrum master, I want story points to be consolidated automatically from work units points of childs

General

As a people who manages backlog items, I want no duplication of data between Doors, backlog management tool and other tools, so that implementing agile will not raises additionnal risks in project management, especially when managing changes in requirements

As a team member I want to manage impediments backlog and improvement backlog so that I can support retrospectives

etc

La forme user story n'est pas à négliger. Elle permet de valider point par point la mise œuvre de la méthode dans l'outil.