background preloader

Agile

Facebook Twitter

6 Backlog Prioritization Techniques - DZone Agile. There are several ways to prioritize the requirements in the backlog.

6 Backlog Prioritization Techniques - DZone Agile

Some of the most popular ones include, MoSCoW M - MUST have this. S - SHOULD have this if at all possible. C - COULD have this if it does not effect anything else. Each requirement will have the priority which would be tagged to MSCW. This site gives a very good explanation about this technique. Business Value Based In this case, each requirement carries a business value it could potentially generate to the company. The requirement with highest business value is implemented during earlier releases . Technology Risk Based In this method, requirements are prioritized based on the risk associated in implementing it. The requirement with highest technology risk is implemented during the earlier iterations. Kano Model.

Estimating Business Value Agile2014. L'itération agile : entre SSII et agence, un nouveau mode de prestation informatique. Contrat agile et pilotage par la valeur - Agile Enterprise Partner. Le digital impose un nouveau rythme et redéfinit les organisations, les processus, la culture, les valeurs, les pratiques et les comportements.

Contrat agile et pilotage par la valeur - Agile Enterprise Partner

Les entreprises agiles, capables de tirer partie de l’innovation, s’adaptent mieux à ces bouleversements. L’agilité ne se réduit toutefois pas à la capacité d’anticiper, d’innover et de coopérer. Agile Contracts: Money for Nothing and Your Change for Free. The origins of Money for Nothing and Your Change for Free contracts can be found here.A team was working on the Open Plans Agile Contract Project in 2008.

Agile Contracts: Money for Nothing and Your Change for Free

The following general principles were agreed upon.Definitions We mutually agree on working together, and thereby build trust in each others expertise. Customer Participation in Scrum Team: The Customer is expected to be active in the project. The role of the Customer includes the following: Pratiques_de_lagilite_2_1_15. Le TOP 10 des conneries que l'on peut voir lors des réunions d'estimation Agile. Connerie /kɔn.ʁi/ féminin (Vulgaire) Fait d'être con, état de celui qui est con.

Le TOP 10 des conneries que l'on peut voir lors des réunions d'estimation Agile

(Familier) Erreur ; acte stupide. +Réunion d'estimation (Planning Poker) Une méthode ludique d'estimation, utilisées par de nombreuses équipes Agiles. L'équipe se réunit avec son client ou Product Owner. Autour de la table, chacun dispose d'un jeu de cartes représentant des valeurs typiques pour l'estimation en points d'une user story (Planning poker référentiel Institut Agile Mélanger le tout et regarder ce qu'il est possible de faire. 1/ Penser que 1 point = 1 heure Bien sûr c'est tentant de détourner la "Suite de Fibonacci" comme ceci : 1 point = 1heure, 2 points = 2 heures, 8 points = 1 journée... Getting to Done: Encouraging Team Ownership - Scrum.org Community Blog. In a previous post describing challenges to creating a done Increment, I identified a lack of team ownership as one of those challenges.

Getting to Done: Encouraging Team Ownership - Scrum.org Community Blog

The Development Team is accountable as a whole to create a done Increment by the end of the Sprint. When team members do not feel team ownership, individuals focus on getting their product backlog item done. There is not a focus on the outcome of the Sprint. In order to use Scrum effectively and have transparency over our progress and quality, we must create an environment that encourages and enables team ownership. This is easier said than done. In my experience, there are five common problems that prevent a Development Team from feeling a sense of team ownership. Regression Test Automation in Scrum: Why and When? |April 26, 2016 Why First, let’s talk about why we need regression test automation.

Regression Test Automation in Scrum: Why and When?

For many this is obvious, for others it’s not exactly so, everybody has their own theories and experience. [devil-advocate-mode] When features change fast automated tests need tweaking all the time. So, for many functional tests, if we need to have them executed once per release, it might be cheaper to run them manually. Automation? There are many reasons why you actually do want to automate lots of things, and “test automation” is a very broad term and covers many different topics. Every new feature is a liability. So, in every release we should spend cycles on re-verification of previously implemented features; let’s call it regression cycle. Manifeste pour le développement Agile de logiciels.

Nous découvrons comment mieux développer des logiciels par la pratique et en aidant les autres à le faire.

Manifeste pour le développement Agile de logiciels

Ces expériences nous ont amenés à valoriser : Les individus et leurs interactions plus que les processus et les outilsDes logiciels opérationnels plus qu’une documentation exhaustiveLa collaboration avec les clients plus que la négociation contractuelleL’adaptation au changement plus que le suivi d’un plan Nous reconnaissons la valeur des seconds éléments, mais privilégions les premiers. © 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice. 12 principes sous-jacents au manifeste View Signatories About the AuthorsAbout the Manifesto site design and artwork © 2001, Ward Cunningham French translation by: Club Agile Rhône-Alpes, Arnaud Pierrel, Bruno Orsier, Christophe Deniaud Reviewers: Claude Aubry, François Beauregard, Laurent Bossavit, Nathalie Gilbert.

Agile Tools

Methodes Agiles.