MANIFESTE AGILE | 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. 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
Kanban - A brief introduction Shortened time cycles Cycle time is a key metric for Kanban teams. Cycle time is the amount of time it takes for a unit of work to travel through the team's workflow—from the moment work starts to the moment it ships. By optimizing cycle time, the team can confidently forecast the delivery of future work. Overlapping skill sets lead to shorter cycle times. When only one person holds a skill set, that person becomes a bottleneck in the workflow. Additionally, this approach empowers the entire team to address any work bottlenecks collectively, facilitating a swift resolution and ensuring a smooth workflow. Fewer bottlenecks Multitasking kills efficiency. For example, a typical software team might have four workflow states: To Do, In Progress, Code Review, and Done. Developers often prefer to write new code rather than spend time reviewing someone else's work. Visual metrics When the team can see data, it's easier to spot bottlenecks in the process (and remove them).
Manifesto for Agile Software Development The product roadmap that boosts innovation I wish I could say I invented the following approach to product roadmapping. But the reality is that I’m not the first product manager who tried planning with quarterly and feature roadmaps before coming to the conclusion that there’s no room for product innovation here. I’m also not the first to realize that you need more space and flexibility to lead a product than a feature roadmap can give you. When I came around planning with the simple card-based roadmap known as theme-based roadmapping, it was because it just made sense. Theme-based roadmapping isn’t a methodology, so it doesn’t force you to follow any particular set of rules. It wasn’t invented by a company, so it doesn’t force you to work with any particular software or product. It’s simply an approach to product strategy that looks like this: And talks like this: “Hey, we don’t know what the future holds. But what’s there to love? Related: How to move from imitation to innovation What is a theme-based roadmap? Final thoughts
Le coût et la valeur des projets - G. TURRE Présentation complète Coût et valeur sont deux notions indissociables, l'un étant la contrepartie de l'autre dans toute décision d'action humaine. En effet, l'homme a toujours plus de désirs, donc plus de projets, que ses moyens ne lui permettent d'en mener. Le terme de valeur a été bien souvent confondu avec celui de coût, et celui-ci a été bien souvent réduit à une affaire de chiffres monétaires mesurant des prix de marché. Sommaire Dédicace Remerciements Introduction Partie I - Les concepts 1 Le contexte : le périmètre, les parties prenantes, les référentiels 2 L'objet - Le projet et le produit - L'oeuvre et l'ouvrage - L'actif stratégique 3 Le sens : le coût, le prix, la valeur et la rentabilité 4 La comptabilité 5 La causalité et les facteurs de coût Partie II - Les méthodes 6 La gestion économique d'exploitation 7 L'analyse financière et le financement des projets 8 La configuration et la structuration du contenu 9 L'estimation des coûts du projet et du produit 14 Les achats dans les projets
Kanban Methodology: What is it and how do you use it? · Airbrake Kanban (or 看板, literally meaning a sign in Japanese), is used today to signify a form of manufacturing in which all necessary components are managed through the use of a card that indicates missing components. The purpose of kanban is to control inventory throughout the supply chain, within a manufacturing setting, via a practice known as just-in-time (JIT) manufacturing. This ensures that the supply and demand of manufacturing components are perfectly balanced with one another, largely eliminating wasted materials and time. In modern software development, kanban (or the kanban methodology) expands on those same just-in-time concepts by ensuring that the level of required work at any given time roughly equates to the work capabilities of the team. What is Kanban? Just as with the kaizen model that we explored in a previous article, the kanban method was originally developed inside Toyota Motor Corporation, by an industrial engineer named Taiichi Ohno. Kanban Cards The Kanban Board
untitled Binnen de Scrum-filosofie werkt men met ‘sprints’ van 1 tot 4 weken. Recent is de filosofie ontstaan om in maximaal één week tot baanbrekende oplossingen te komen. Het boek Sprint van Jake Knapp is begin dit jaar uitgekomen en vertelt over de vijfdaagse Sprint die ze hanteren bij Google Ventures om vernieuwingsvragen te beantwoorden door middel van het ontwerpen van prototypes en ideeën uittesten met klanten. Uiteraard heeft dit sterke overlap met de populaire bewegingen van Agile thinking en de Lean Start-up. Zo’n vijfdaagse Sprint is tevens een aanpak om in een week ‘in het klein’ te werken aan ‘grote’ veranderingen of vernieuwingen binnen je team of organisatie. Dit artikel bestaat uit twee delen. Hiermee heb je de handvatten in huis om zelf een sprintweek in te zetten als aanjaagraket voor vernieuwing binnen je team of organisatie. Deel 1: De vijfdaagse Sprint-aanpak Alvorens je start is het slim om eerst de weg te effenen. Een sprint kun je inzetten bij drie uitdagende situaties:
8 Things To Use in “Jobs-To-Be-Done” Framework For Product Development Talk all you want to about the importance of strategy or operational efficiency, but the truth is that companies succeed because they offer a product or service that customers find irresistible. “Job-to-be-done” changed the way I am looking at the startup I am involved with. It forces you to look at other perspectives and for many people “jobs to be done” involves a mindset change. It forces you to look at our product the way customers do. Clayton Christensen described this concept in this paper he wrote with one of the best tech entrepreneurs and product marketers of all-time, Scott Cook of Intuit. The theory simply asks, “What job your product is hired to do?”. This is the power of the JTBD concept and technique: It helps the innovator understand that customers don’t buy products and services; they hire various solutions at various times to get a wide array of jobs done. 1. Christensen would assert that people buy any product to get a job done. 2. Example: 3. 4. 5. 6. 7. 8.
Kanban pour l'IT - L. MORISSEAU Extreme Programming Tutorial - Tutorialspoint Extreme programming (XP) is a software development methodology, which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles, to improve productivity and introduce checkpoints at which new customer requirements can be adopted. XP is a lightweight, efficient, low-risk, flexible, predictable, scientific, and fun way to develop a software. Extreme Programming was conceived and developed to address the specific needs of software development by small teams in the face of vague and changing requirements. Before you start proceeding with this tutorial, we are assuming that you are already aware about the basics of Agile methodologies and Scrum. Extreme programming (XP) is a software development methodology, which is intended to improve software quality and responsiveness to changing customer requirements.
untitled Vorige week kwam het eerste deel uit van dit artikel over de vijfdaagse Sprint-aanpak. Dit tweede deel gaat over corporatie Woonstad Rotterdam als praktijkvoorbeeld, waar het is gebruikt om in een week ‘in het klein’ te werken aan ‘grote’ veranderingen. Bij de afdeling Klant Contacten (KC) gebruikten ze de aanpak om in een week versnelling in te bouwen om bepaalde knelpunten aan te pakken. Daarbij hebben ze niet de aanpak als een rechtlijnig stappenplan gezien, maar de Sprint-filosofie erachter gebruikt en hun eigen aanpak daarvan gemaakt. De KC-week bij Woonstad Rotterdam De afdeling KC is de eerste lijn waar alle klantvragen binnen komen. ‘Onszelf kwaad maken om verbeterpotentieel versneld aan te pakken’ De sprintweek is gebruikt om vaart te maken met latent verbeterpotentieel tussen KC en andere afdelingen waarmee grote afhankelijkheden zijn in het primaire proces. Een van de deelnemers noemde het “het is een week om onszelf even kwaad te maken en laaghangend fruit aan te pakken”.
All About OKRs: How To Set Them, Achieve Them, And Track Them In Trello So, your team wants to go places? It turns out that the team at Buffer does as well. Through OKRs, they have been able to do just that. We know, we know, OK-what? To define them another way… An Objective helps answer the question, “Where do I want to go?” Big plans require big action, right? Hear from Buffer's VP of Marketing, Kevan Lee, as he breaks down how company strategy mixed with OKRs can lead you to some of your best results next quarter. OKRs: Objectives And Key Results—What Are They? Objectives and key results lead to better performance management by tracking your progress through goal-setting. Sounds easy, right? We have big plans at Buffer to build a social media tool that is as ubiquitous for social marketers as Google Analytics is for website owners. We also have big marketing plans to ship major projects (courses!) It’s tough to align our goals and stay on track with project management. Does this sound familiar? Here’s what objectives and key results look like in practice: 1. 2.
Gestion de projet agile - V.MESSAGER Des approches prédictives aux méthodes agiles Rassemblant plus de quinze années d'expérience en gestion de projet informatique, cet ouvrage, non sans rappeler les méthodologies traditionnelles - qui définissent à l'avance les besoins, les activités à réaliser, leur séquencement, les rôles et les livrables à produire -, introduit aux méthodes agiles, dont le succès s'affirme d'année en année. Ces dernières prennent le contre-pied des méthodes prédictives en évitant une définition trop précoce et figée des besoins ; elles ont montré une surprenante efficacité en pariant sur la souplesse des équipes. Un repère pour le chef de projet informatique Ce guide aidera les chefs de projet, chevronnés ou débutant dans le métier, à évaluer et améliorer leurs compétences en gestion de projet. Un livre incontournable pour les chefs de projet qui souhaitent évoluer vers les méthodes agiles !
What is Extreme Programming (XP)? Definition Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development team. XP is the most specific of the agile frameworks regarding appropriate engineering practices for software development. When Applicable The general characteristics where XP is appropriate were described by Don Wells on www.extremeprogramming.org: Dynamically changing software requirementsRisks caused by fixed time projects using new technologySmall, co-located extended development teamThe technology you are using allows for automated unit and functional tests Due to XP’s specificity when it comes to it’s full set of software engineering practices, there are several situations where you may not want to fully practice XP. While you can’t use the entire XP framework in many situations, that shouldn’t stop you from using as many of the practices as possible given your context. Values Communication Simplicity Feedback Courage