Example Mapping - quelques exemples
•
4 likes•3,453 views
Présenté lors de la "Agile Testing Night" du 25 septembre 2017 en tant que représentant du groupe Meetup "Agile Testing Partis". - Introduction au sujet, motivation de l'intérêt - Présentation de l'outil - Exemples
Report
Share
Report
Share
Recommended
Introduction aux spécifications exécutables (dit aussi atdd, bdd)
Comment s'assurer que tout le monde parle la même langue dans l'équipe ? Et ainsi éviter les retours de recette ?
Utiliser des spécifications exécutables, ou ses cousins le ATDD (Acceptance Test Driven Development) et le BDD (Behavior Driven Development), est un élément de réponse particulièrement pertinent. Cette méthode est également un point d'entrée puissant vers une stratégie d'automatisation des tests.
Dans cette présentation vous découvrirez les tenants et les aboutissants de cette méthode, et repartirez les poches remplies de conseils de mise en place.
Elephant Carpaccio
Here are some tips for breaking down work in an agile way:
- Focus on delivering value to users. Each story and task should provide some value.
- Iterate frequently. Stories and tasks should be small enough that you can complete and release them within a sprint or two.
- Get early feedback. Small slices allow testing work sooner and adjusting based on feedback.
- Prioritize flexibility. Small slices give you options to reorder or drop work as priorities change.
- Estimate costs accurately. Tasks should take 1-5 days; if longer, may need refactoring. Consider spikes for technical challenges.
- Refactor when repetitive. If work is very similar, look for ways to simplify through ref
Life cycle of user story: Outside-in agile product management & testing, or...
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
How to Break the Requirements into User Stories
The document discusses how to break down large requirements into smaller, independent user stories for agile software development. It recommends following the INVEST principles to create user stories that are independent, negotiable, valuable, estimable, small, and testable. Some patterns for splitting large stories are also described, such as breaking stories into workflow steps, major efforts, business rule variations, and operations. The goal is to create functional pieces that deliver business value iteratively in a manageable way.
Agile methodology
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Example Mapping in the Wild
We all know that user stories are a placeholder for a conversation. Example mapping, developed by Matt Wynne, is a way to structure that conversation in a way that is short, focused and feels really productive.
In this case study Ceri Shaw shares how she and her team have applied example mapping to their work at FreeAgent, how it has improved planning meetings and meant that they can be much more confident they're developing the right thing. She also covers some of the times it hasn't worked so well.
"How to write better User Stories" por @jrhuerta
This document discusses improving user stories by following best practices like the INVEST acronym. It explains that user stories address common requirements gathering pitfalls by focusing on delivering value to end users, using their language, and enabling prioritization and incremental development. The document provides guidelines for writing "good" user stories, including having context, value, and acceptance criteria, as well as being independent, negotiable, estimable, small in size, and testable. It also identifies potential "user story smells" to avoid.
Writing User Stories (04/2012)
The document discusses software requirements and communication between business and development teams. It states that requirements are a communication problem and both sides must work together. It warns that if either side dominates, the business loses value. It provides examples of problems that can occur if developers or the business side dominate requirements and decision making. The document advocates for spreading decision making across the project timeline rather than one large set of decisions. It discusses using user stories and examples to help capture requirements in a way that is understandable to both business and development.
Recommended
Introduction aux spécifications exécutables (dit aussi atdd, bdd)
Comment s'assurer que tout le monde parle la même langue dans l'équipe ? Et ainsi éviter les retours de recette ?
Utiliser des spécifications exécutables, ou ses cousins le ATDD (Acceptance Test Driven Development) et le BDD (Behavior Driven Development), est un élément de réponse particulièrement pertinent. Cette méthode est également un point d'entrée puissant vers une stratégie d'automatisation des tests.
Dans cette présentation vous découvrirez les tenants et les aboutissants de cette méthode, et repartirez les poches remplies de conseils de mise en place.
Elephant Carpaccio
Here are some tips for breaking down work in an agile way:
- Focus on delivering value to users. Each story and task should provide some value.
- Iterate frequently. Stories and tasks should be small enough that you can complete and release them within a sprint or two.
- Get early feedback. Small slices allow testing work sooner and adjusting based on feedback.
- Prioritize flexibility. Small slices give you options to reorder or drop work as priorities change.
- Estimate costs accurately. Tasks should take 1-5 days; if longer, may need refactoring. Consider spikes for technical challenges.
- Refactor when repetitive. If work is very similar, look for ways to simplify through ref
Life cycle of user story: Outside-in agile product management & testing, or...
It has always been my pleasure and fun to facilitate workshops for PM (product management) community at and outside Cisco, although this was first time I did a BDD workshop with PMs alone. And I realized today how PayPal has been a really great venue for SVPMA annual product camp "unconference" for 1k+ PMs with 550 waitlisted this year! I look forward to this event every year now...huge success!
Abstract:
As Product Owners and Managers are driving innovation thru' those fuzzy ideas in terms of scenarios, testers have always been thinking about those in form of test cases which take form of acceptance criteria for those scenarios. When you talk about those scenarios to your teams or even peers, you see those diverging ideas converging to something concrete.
That's how BDD helps you shape that idea. That fuzzy scenario, when validated thru' an engineering "spike", can be useful for product management MRD/PRD/use-case-models/stories...whatever it is that you want to use to drive product development.
And this is where Agile Tester role begins! So instead of doing top-down or bottoms-up product management & testing, try this outside-in approach. Go for it!
My workshop on BDD is about what I term as "Outside-in agile product management". To understand what I really mean by that, here is my slideshare presentation used rarely when teaching from the back of the class during this hyper-interactive workshop.
How to Break the Requirements into User Stories
The document discusses how to break down large requirements into smaller, independent user stories for agile software development. It recommends following the INVEST principles to create user stories that are independent, negotiable, valuable, estimable, small, and testable. Some patterns for splitting large stories are also described, such as breaking stories into workflow steps, major efforts, business rule variations, and operations. The goal is to create functional pieces that deliver business value iteratively in a manageable way.
Agile methodology
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Example Mapping in the Wild
We all know that user stories are a placeholder for a conversation. Example mapping, developed by Matt Wynne, is a way to structure that conversation in a way that is short, focused and feels really productive.
In this case study Ceri Shaw shares how she and her team have applied example mapping to their work at FreeAgent, how it has improved planning meetings and meant that they can be much more confident they're developing the right thing. She also covers some of the times it hasn't worked so well.
"How to write better User Stories" por @jrhuerta
This document discusses improving user stories by following best practices like the INVEST acronym. It explains that user stories address common requirements gathering pitfalls by focusing on delivering value to end users, using their language, and enabling prioritization and incremental development. The document provides guidelines for writing "good" user stories, including having context, value, and acceptance criteria, as well as being independent, negotiable, estimable, small in size, and testable. It also identifies potential "user story smells" to avoid.
Writing User Stories (04/2012)
The document discusses software requirements and communication between business and development teams. It states that requirements are a communication problem and both sides must work together. It warns that if either side dominates, the business loses value. It provides examples of problems that can occur if developers or the business side dominate requirements and decision making. The document advocates for spreading decision making across the project timeline rather than one large set of decisions. It discusses using user stories and examples to help capture requirements in a way that is understandable to both business and development.
Product Backlog Management
The document provides an overview of agile product backlog management using the Scrum framework. It discusses key aspects of Scrum including the product owner, sprint backlog, product backlog, daily stand-ups, sprint reviews and retrospectives. The document also compares Scrum to the waterfall method and discusses benefits of Scrum such as faster time to market, higher quality and satisfying customers through iterative delivery of working software.
Agile Metrics V6
The document discusses various metrics that can be used to measure progress on agile software development projects. It describes metrics like running tested features, earned business value, velocity, burn charts, and cumulative flow diagrams. It explains how these metrics can provide information on outcomes, identify areas for improvement, and influence team behavior in agile projects.
scrum
This document provides an overview of scrum, an agile project management framework. It defines key scrum roles like the product owner, scrum master, and scrum team. It also outlines the scrum process which involves sprint planning meetings, daily stand-up meetings, and working in 2-4 week sprints to develop incremental deliverables. The document notes major companies that use scrum and the advantages of increased flexibility, quality, and clear project status, while also acknowledging potential disadvantages like lack of a final plan and challenges in change management.
User Stories
The document discusses various product management artifacts used in Agile development such as user stories, product vision, product roadmap, product backlog, and sprint backlog. It describes how the product roadmap informs the prioritized product backlog, which contains short user stories that guide development work tracked in sprint backlogs on a sprint-by-sprint basis. Effective use of these artifacts helps ensure alignment between product strategy and development activities.
The Scrum Guide 2020.pptx
This document provides an overview of the Scrum framework for developing software. Some key points:
- Scrum is an empirical, lightweight framework that helps teams generate value through adaptive solutions to complex problems. It is based on empiricism, lean thinking, and values transparency, inspection, and adaptation.
- Scrum uses events like sprints, daily stand-ups, sprint reviews and retrospectives to inspect and adapt its processes. Sprints are time-boxed periods for delivering increments of work toward a sprint goal.
- Scrum teams are cross-functional and consist of developers, a product owner, and scrum master. The product owner manages the product backlog and maximizes value. The scrum
Splitting Stories with the Hamburger Method - A Simple 5 Step Process
The document discusses Adzic's Hamburger Method for vertically splitting user stories into smaller stories. It provides an overview of the method, which involves identifying layers or types of tasks needed to complete the story, then identifying options for each task from least to greatest value. The first "bite" or user story combines the least valuable option from each task. Subsequent bites build on prior bites by enhancing them. The document includes an example application of the method and a quiz.
Présentation de l’agilité
Présentation de l'Agilité, conférence au Cara le 5 septembre 2017, à Lyon.
Introduction aux Scrum, Kanban, Lean Startup, Définition des Rôles Scrum Product Owner, Scrum Master, des cérémonies Daily Meeting, Démonstration, Product Backlog, Sprint, Coach, User Stories, Sprint Backlog, Increment, Sprint review, retrospective, sprint planning
Agile Methodology in Software Development
The document discusses various agile methodologies and frameworks, with a focus on Scrum. It defines Scrum as an agile process that allows teams to focus on delivering the highest business value in the shortest time through rapid inspection of working software every 2-4 weeks. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and self-organizing Development Teams. Sprints involve planning, daily stand-ups, demos, and retrospectives to continuously improve.
DevOps Monitoring and Alerting
Khairul Zebua gave a presentation on DevOps, monitoring, and alerting tools. The presentation covered the benefits of adopting DevOps such as continuous delivery, less complexity, faster problem resolution, and increased innovation. It discussed using tools like Ansible, Consul, Prometheus, and Grafana to build monitoring systems and alerting. The presentation encouraged connecting with Khairul Zebua on LinkedIn and GitHub for further discussion.
Creating Agile Product Roadmaps Everyone Understands
You'll learn:
- How to create a roadmap for current, near-term, and future projects
- How to communicate priorities clearly with your team
- How to present your roadmap to executives
User Story Workshop
The document contains instructions for drawing a summer meadow scene with specific elements like flowers, grass, cows, birds, and a sun. It begins with more open requirements to draw blue and red flowers with cows and birds under a sun. Then it provides closed, detailed requirements specifying the number and characteristics of each element to include in the drawing. The document discusses the difference between open and closed requirements.
Sprint Review and Planning Template
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Agile transformation kick off presentation v 1.0
This document outlines an agile transformation approach for a business unit (BU) with 142 people across 5 sites, 4 subsystems, and 6 functions. It involves adopting the Scaled Agile Framework (SAFe) over 8-9 months. Key activities include diagnostics, training staff in agile methods, forming cross-functional teams, implementing new roles, and coaching the BU to become self-sustaining in agile practices with bi-weekly sprints and quarterly releases. Challenges included changing the culture, integrating tools, and defining new responsibilities across the organization.
DevOps
-DevOps Principles
-DevOps Goals
-Advantages and Disadvantages
-DevOps and Agile
-DevOps Tools
-Why DevOps?
Agile Overview
The document provides an overview of Agile development and Scrum methodology. It discusses key Agile concepts like the Agile Manifesto, Scrum roles and artifacts, timeboxing, and metrics like velocity and burndowns. It also addresses adopting Agile, working with requirements and QA, and challenges of offshore development in an Agile model.
Continuous Integration
Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.
Effective User Stories
The document discusses user stories for software requirements. It provides tips for writing good user stories, such as starting with user goals, writing smaller stories for soon-to-be-implemented functionality, keeping the user interface out of stories initially, and having the customer rather than developer write stories. It also identifies "smelly" user stories, such as those that are too small, interdependent, include too many details, or are written too far in advance.
Scrum
Scrum is an agile software development framework that emphasizes communication, collaboration, and flexibility. It was invented in 1993 to provide a more adaptive approach to project management compared to traditional waterfall models. Scrum uses short development cycles called sprints, daily stand-up meetings, and defined roles like Product Owner and Scrum Master to help self-organizing teams work together to deliver working software incrementally.
Lean inception: como alinhar pessoas e construir o produto certo
Lean Inception é a combinação eficaz do Design Thinking e do Lean StartUp para decidir o Produto Mínimo Viável, em Inglês Minimum Viable Product (MVP). É um workshop dividido em várias etapas e atividades que irão direcionar a equipe na construção do produto ideal. A construção de qualquer projeto sempre começa com uma Lean Inception.
Resolve Incidents Faster: Transforming Your Incident Management Process
Incident response teams are evolving, thanks to DevOps, agile, and today’s demand for always-on services. But, what’s the best way to respond when you’re faced with a complex mix of systems, software, and teams? Is there a way to respond faster, collaborate better, and continuously improve your incident management process?
Join Simon Kubica, Product Manager for Opsgenie, as he uncovers best practices that’ll streamline every stage of your response effort. See how Atlassian, Amazon and Google enable collaboration between support, operations and development, and learn how to leverage automation and conduct effective postmortems. Plus, Simon will show live demos on how you can implement these tips in Opsgenie, Statuspage, and Jira Service Desk.
Sortir de l'ère des héros - l'excellence comme clé d'une organisation résiliente
Votre projet marche, mais c’est le chaos. Comment arrêter de dépendre de ces “héros” sur qui tout repose ?
Comprenez comment l'excellence est fondamentale pour permettre aux "héros" de prendre des vacances et à l'organisation d'être plus résiliente.
Awareness session: Agile -- by Jean-Pierre Lambert
What is "agile"? These are the slides of my awareness session to agile.
- From plan driven to value driven
- Agile = Product Vision + Technical Excellence + Adapted Processes
- Software Craftsmanship
- Mindset : Heart of Agile, Modern Agile
- Project Mindset vs. Product Mindset
- Scrum
- Kanban
- Team typologies : Component Team, Feature Team, Squad, Impact Team, Product Team
More Related Content
What's hot
Product Backlog Management
The document provides an overview of agile product backlog management using the Scrum framework. It discusses key aspects of Scrum including the product owner, sprint backlog, product backlog, daily stand-ups, sprint reviews and retrospectives. The document also compares Scrum to the waterfall method and discusses benefits of Scrum such as faster time to market, higher quality and satisfying customers through iterative delivery of working software.
Agile Metrics V6
The document discusses various metrics that can be used to measure progress on agile software development projects. It describes metrics like running tested features, earned business value, velocity, burn charts, and cumulative flow diagrams. It explains how these metrics can provide information on outcomes, identify areas for improvement, and influence team behavior in agile projects.
scrum
This document provides an overview of scrum, an agile project management framework. It defines key scrum roles like the product owner, scrum master, and scrum team. It also outlines the scrum process which involves sprint planning meetings, daily stand-up meetings, and working in 2-4 week sprints to develop incremental deliverables. The document notes major companies that use scrum and the advantages of increased flexibility, quality, and clear project status, while also acknowledging potential disadvantages like lack of a final plan and challenges in change management.
User Stories
The document discusses various product management artifacts used in Agile development such as user stories, product vision, product roadmap, product backlog, and sprint backlog. It describes how the product roadmap informs the prioritized product backlog, which contains short user stories that guide development work tracked in sprint backlogs on a sprint-by-sprint basis. Effective use of these artifacts helps ensure alignment between product strategy and development activities.
The Scrum Guide 2020.pptx
This document provides an overview of the Scrum framework for developing software. Some key points:
- Scrum is an empirical, lightweight framework that helps teams generate value through adaptive solutions to complex problems. It is based on empiricism, lean thinking, and values transparency, inspection, and adaptation.
- Scrum uses events like sprints, daily stand-ups, sprint reviews and retrospectives to inspect and adapt its processes. Sprints are time-boxed periods for delivering increments of work toward a sprint goal.
- Scrum teams are cross-functional and consist of developers, a product owner, and scrum master. The product owner manages the product backlog and maximizes value. The scrum
Splitting Stories with the Hamburger Method - A Simple 5 Step Process
The document discusses Adzic's Hamburger Method for vertically splitting user stories into smaller stories. It provides an overview of the method, which involves identifying layers or types of tasks needed to complete the story, then identifying options for each task from least to greatest value. The first "bite" or user story combines the least valuable option from each task. Subsequent bites build on prior bites by enhancing them. The document includes an example application of the method and a quiz.
Présentation de l’agilité
Présentation de l'Agilité, conférence au Cara le 5 septembre 2017, à Lyon.
Introduction aux Scrum, Kanban, Lean Startup, Définition des Rôles Scrum Product Owner, Scrum Master, des cérémonies Daily Meeting, Démonstration, Product Backlog, Sprint, Coach, User Stories, Sprint Backlog, Increment, Sprint review, retrospective, sprint planning
Agile Methodology in Software Development
The document discusses various agile methodologies and frameworks, with a focus on Scrum. It defines Scrum as an agile process that allows teams to focus on delivering the highest business value in the shortest time through rapid inspection of working software every 2-4 weeks. Key Scrum roles include the Product Owner who prioritizes features, the Scrum Master who facilitates the process, and self-organizing Development Teams. Sprints involve planning, daily stand-ups, demos, and retrospectives to continuously improve.
DevOps Monitoring and Alerting
Khairul Zebua gave a presentation on DevOps, monitoring, and alerting tools. The presentation covered the benefits of adopting DevOps such as continuous delivery, less complexity, faster problem resolution, and increased innovation. It discussed using tools like Ansible, Consul, Prometheus, and Grafana to build monitoring systems and alerting. The presentation encouraged connecting with Khairul Zebua on LinkedIn and GitHub for further discussion.
Creating Agile Product Roadmaps Everyone Understands
You'll learn:
- How to create a roadmap for current, near-term, and future projects
- How to communicate priorities clearly with your team
- How to present your roadmap to executives
User Story Workshop
The document contains instructions for drawing a summer meadow scene with specific elements like flowers, grass, cows, birds, and a sun. It begins with more open requirements to draw blue and red flowers with cows and birds under a sun. Then it provides closed, detailed requirements specifying the number and characteristics of each element to include in the drawing. The document discusses the difference between open and closed requirements.
Sprint Review and Planning Template
The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Agile transformation kick off presentation v 1.0
This document outlines an agile transformation approach for a business unit (BU) with 142 people across 5 sites, 4 subsystems, and 6 functions. It involves adopting the Scaled Agile Framework (SAFe) over 8-9 months. Key activities include diagnostics, training staff in agile methods, forming cross-functional teams, implementing new roles, and coaching the BU to become self-sustaining in agile practices with bi-weekly sprints and quarterly releases. Challenges included changing the culture, integrating tools, and defining new responsibilities across the organization.
DevOps
-DevOps Principles
-DevOps Goals
-Advantages and Disadvantages
-DevOps and Agile
-DevOps Tools
-Why DevOps?
Agile Overview
The document provides an overview of Agile development and Scrum methodology. It discusses key Agile concepts like the Agile Manifesto, Scrum roles and artifacts, timeboxing, and metrics like velocity and burndowns. It also addresses adopting Agile, working with requirements and QA, and challenges of offshore development in an Agile model.
Continuous Integration
Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.
Effective User Stories
The document discusses user stories for software requirements. It provides tips for writing good user stories, such as starting with user goals, writing smaller stories for soon-to-be-implemented functionality, keeping the user interface out of stories initially, and having the customer rather than developer write stories. It also identifies "smelly" user stories, such as those that are too small, interdependent, include too many details, or are written too far in advance.
Scrum
Scrum is an agile software development framework that emphasizes communication, collaboration, and flexibility. It was invented in 1993 to provide a more adaptive approach to project management compared to traditional waterfall models. Scrum uses short development cycles called sprints, daily stand-up meetings, and defined roles like Product Owner and Scrum Master to help self-organizing teams work together to deliver working software incrementally.
Lean inception: como alinhar pessoas e construir o produto certo
Lean Inception é a combinação eficaz do Design Thinking e do Lean StartUp para decidir o Produto Mínimo Viável, em Inglês Minimum Viable Product (MVP). É um workshop dividido em várias etapas e atividades que irão direcionar a equipe na construção do produto ideal. A construção de qualquer projeto sempre começa com uma Lean Inception.
Resolve Incidents Faster: Transforming Your Incident Management Process
Incident response teams are evolving, thanks to DevOps, agile, and today’s demand for always-on services. But, what’s the best way to respond when you’re faced with a complex mix of systems, software, and teams? Is there a way to respond faster, collaborate better, and continuously improve your incident management process?
Join Simon Kubica, Product Manager for Opsgenie, as he uncovers best practices that’ll streamline every stage of your response effort. See how Atlassian, Amazon and Google enable collaboration between support, operations and development, and learn how to leverage automation and conduct effective postmortems. Plus, Simon will show live demos on how you can implement these tips in Opsgenie, Statuspage, and Jira Service Desk.
What's hot (20)
Splitting Stories with the Hamburger Method - A Simple 5 Step Process
Splitting Stories with the Hamburger Method - A Simple 5 Step Process
Creating Agile Product Roadmaps Everyone Understands
Creating Agile Product Roadmaps Everyone Understands
Lean inception: como alinhar pessoas e construir o produto certo
Lean inception: como alinhar pessoas e construir o produto certo
Resolve Incidents Faster: Transforming Your Incident Management Process
Resolve Incidents Faster: Transforming Your Incident Management Process
More from Jean-Pierre Lambert
Sortir de l'ère des héros - l'excellence comme clé d'une organisation résiliente
Votre projet marche, mais c’est le chaos. Comment arrêter de dépendre de ces “héros” sur qui tout repose ?
Comprenez comment l'excellence est fondamentale pour permettre aux "héros" de prendre des vacances et à l'organisation d'être plus résiliente.
Awareness session: Agile -- by Jean-Pierre Lambert
What is "agile"? These are the slides of my awareness session to agile.
- From plan driven to value driven
- Agile = Product Vision + Technical Excellence + Adapted Processes
- Software Craftsmanship
- Mindset : Heart of Agile, Modern Agile
- Project Mindset vs. Product Mindset
- Scrum
- Kanban
- Team typologies : Component Team, Feature Team, Squad, Impact Team, Product Team
Formation stratégie de test - créer un produit de qualité
Sensibilisation à la qualité et aux tests permettant de comprendre ce qui fait une bonne stratégie de test et d'en définir une :
- La qualité c'est quoi ?
- Les tests ça sert à quoi ? Quels sont les types de test ?
- Pourquoi les tests doivent être impliqués au plus tôt ?
- Un outil pour piloter l'effort de test : la matrice ACC
[V2] La collaboration, signe d'une véritable agilité
Comment reconnaître une équipe vraiment agile ? À son niveau de collaboration : une équipe est vraiment agile dès lors qu’elle est en collaboration forte et permanente.
Mais qu'est-ce que cela veut dire en pratique ?
Qu'il s'agisse de ce niveau grisant de collaboration ou bien de sa complète et navrante absence, je vous propose de rejouer diverses scènes pour les illustrer.
Nous détaillerons également les pratiques qui découlent d'un tel niveau de collaboration, ou qui permettent de les pousser à l'extrême.
-----
Cette conférence a été donnée en keynote à l'occasion d'Agile Tour Montpellier 2019.
[V1] La collaboration, signe d'une véritable agilité
Comment reconnaître une équipe vraiment agile ? À son niveau de collaboration : une équipe est vraiment agile dès lors qu’elle est en collaboration forte et permanente.
Mais qu'est-ce que cela veut dire en pratique ?
Qu'il s'agisse de ce niveau grisant de collaboration ou bien de sa complète et navrante absence, je vous propose de rejouer diverses scènes pour les illustrer.
Nous détaillerons également les pratiques qui découlent d'un tel niveau de collaboration, ou qui permettent de les pousser à l'extrême.
-----
Cette conférence a été donnée en keynote à l'occasion d'Agile Grenoble 2019.
[V2] Une semaine dans ma peau de testeur agile
Le testeur, ou le QA, on voit très bien ce qu'il fait avant le passage à l'agilité : il teste... Plus précisément, il valide les changements, il vérifie la non-régression, et puis il fait aussi d'autres trucs à côté.
Par contre que fait-il maintenant qu'on travaille en agile ? Ce n'est évident pour personne, d'autant plus qu'on l'a intégré dans l'équipe agile. Comment peut-il bien faire tout ce qu'il faisait avant mais désormais en juste une itération ? Et puis on n'arrête pas de parler d'automatisation des tests, a-t-on vraiment encore besoin de testeur ?
Pourquoi ne pas répondre à ces questions en suivant un testeur agile pendant une semaine ? Pendant une semaine, vous allez voir à quoi ressemble le quotidien d'un testeur agile, voir ce qu'il fait de ses journées, voir toute la valeur qu'il ajoute à l'équipe sans se positionner pour autant en garant de la prod.
Je suis un agiliste auto-didacte et j'ai d'ailleurs un avis très mitigé sur les certifications. Loin de tout dogmatisme, attendez-vous à voir avant tout du retour d'expérience, du vécu. Le tout sur le ton de l'humour et du troll !
Vous verrez que le rôle de testeur agile est plein de subtilités. Contrairement à ce qu'on pourrait imaginer il a énormément de travail et la plupart des équipes gagneraient à un avoir un !
-----
Cette conférence a été donnée à l'occasion d'Agile Tour Toulouse 2019, Agile Tour Nantes 2019, Agile Tour Bordeaux 2019, La Paris Test Conf 2019, Agile Tour Rennes 2019, Agile Grenoble 2019, Agile Tour Montpellier 2019.
[V1] Une semaine dans ma peau de testeur agile
Le testeur, ou le QA, on voit très bien ce qu'il fait avant le passage à l'agilité : il teste... Plus précisément, il valide les changements, il vérifie la non-régression, et puis il fait aussi d'autres trucs à côté.
Par contre que fait-il maintenant qu'on travaille en agile ? Ce n'est évident pour personne, d'autant plus qu'on l'a intégré dans l'équipe agile. Comment peut-il bien faire tout ce qu'il faisait avant mais désormais en juste une itération ? Et puis on n'arrête pas de parler d'automatisation des tests, a-t-on vraiment encore besoin de testeur ?
Pourquoi ne pas répondre à ces questions en suivant un testeur agile pendant une semaine ? Pendant une semaine, vous allez voir à quoi ressemble le quotidien d'un testeur agile, voir ce qu'il fait de ses journées, voir toute la valeur qu'il ajoute à l'équipe sans se positionner pour autant en garant de la prod.
Je suis un agiliste auto-didacte et j'ai d'ailleurs un avis très mitigé sur les certifications. Loin de tout dogmatisme, attendez-vous à voir avant tout du retour d'expérience, du vécu. Le tout sur le ton de l'humour et du troll !
Vous verrez que le rôle de testeur agile est plein de subtilités. Contrairement à ce qu'on pourrait imaginer il a énormément de travail et la plupart des équipes gagneraient à un avoir un !
-----
Cette conférence a été donnée à l'occasion d'Agile Tour Lille 2019.
Les différents types de Scrum Master
Quels sont les différents "types" de Scrum Master ? Quels sont les atouts et défauts de chacun d'entre eux ?
Les différents types de Product Owner
Quels sont les différents "types" de Product Owner ? Quels sont les atouts et défauts de chacun d'entre eux ?
"Agile sucks" -- or does it?
Talk given at DevBreak'19, video available at https://youtu.be/bT0i0z6SW8o
-----
Agile has become mainstream and is the new standard. But is it really any better than "traditional" software project management? Many developers think it's the same thing rehashed, or that agile is even worse.
Why do they think so? Are they right?
In this talk we will run through all-too-familliar situations of everyday life in IT with a common denominator: those companies are nothing quite like agile but are still calling themselves agile. Brace yourself, because it seems that there is no limit to the amount of nonsense that some companies create!
If you are still not convinced that agile is awesome, please come and discover all the things that your company got completely wrong!
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
Support à imprimer pour faciliter les exercices en équipe : "Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping !"
Lien vers le support de présentation : https://www.slideshare.net/JeanPierreLambert1/atelier-boostez-vos-backlog-groomingrefinement-avec-lexample-mapping-support-de-prsentation-132324807
Cette œuvre de Jean-Pierre Lambert est mise à disposition selon les termes de la licence Creative Commons Attribution 4.0 International. https://creativecommons.org/licenses/by/4.0/
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
Support de présentation : "Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping !"
Le support à imprimer pour faciliter l'atelier : https://www.slideshare.net/JeanPierreLambert1/atelier-boostez-vos-backlog-groomingrefinement-avec-lexample-mapping-support-imprimer
Cette œuvre de Jean-Pierre Lambert est mise à disposition selon les termes de la licence Creative Commons Attribution 4.0 International. https://creativecommons.org/licenses/by/4.0/
MiXiT 2018 - Retour d'expérience France Télévisions - Passer de faire de l'Ag...
Cette conférence a déjà été présenté à Agile en Seine 2017 : https://www.slideshare.net/JeanPierreLambert1/agile-en-seine-2017-retour-dexprience-france-tlvisions-passer-de-faire-de-lagile-tre-agile
Pour l'occasion, nous avons rajouté quelques éléments supplémentaires : tirons parti de 6 mois de recul supplémentaires pour juger de l'efficacité des changements opérés !
Une semaine dans ma peau de Scrum Master
C'est quoi déjà un Scrum Master ? Que fait-il de ses journées ? Est-ce qu'il nous en faut un ? Qu'est-ce qu'il nous apporterait ?
Pourquoi ne pas répondre à ces questions en me suivant pendant une semaine ? Pendant une semaine, vous allez voir à quoi ressemble le quotidien d'un Scrum Master, voir ce qu'il fait de ses journées, voir à quoi il sert réellement.
Je suis Scrum Master auto-didacte et j'ai d'ailleurs un avis très mitigé sur les certifications. Loin de tout dogmatisme, attendez-vous à voir avant tout du retour d'expérience, du vécu. Le tout sur le ton de l'humour et du troll !
Vous verrez que le Scrum Master a fort à faire au-delà de “s’assurer que les rituels Scrum ont lieu” ! Dans une organisation qui n'est pas Agile, ou qui en a pris les pratiques mais pas le mindset, le Scrum Master est la clef qui permet aux équipes de s'épanouir malgré tout.
Qu’il s’agisse d’une bureaucratie rampante qui transforme le moindre achat en parcours du combattant, ou bien d’un management qui ne sait piloter que par les ordres et la recherche de coupable, il est quasi-impossible pour une équipe de passer à l’Agilité sans bouclier que sera le Scrum Master.
Le Scrum Master, c’est aussi celui qui protège l’équipe d’elle-même, en l’aidant à se donner des règles et à les respecter, pour atteindre la rigueur extrême qu’exige l’Agilité. Tout en les menant vers une toujours plus grande autonomie, et non pas en leur disant comment faire.
Une semaine dans ma peau de Scrum Master - V0 - Meetup Renault Digital
Premier brouillon à destination d'un Meetup chez Renault Digital de ma session Agile Tour Paris 2017 : "Une semaine dans ma peau de Scrum Master"
Agile En Seine 2017 - Retour d'expérience France Télévisions - Passer de fair...
Revivez avec nous la grande aventure Agile de l’équipe Player à France Télévisions !
Au début de notre histoire, on pourrait la qualifier d’équipe comme les autres, qui tente de faire de l’Agile.
Au fil des chapitres, les changements vont s’opérer pour bel et bien bien devenir et être Agile !
Vidéo disponible sur InfoQ : https://www.infoq.com/fr/presentations/player-france-televisions-passer-de-faire-de-l-agile-a-etre-agile
C'est quoi le Software Craftsmanship ?
Suite à ma lecture de "The Software Craftsman" de Sandro Mancuso, je présente ce qu'est le Software Craftsmanship.
Présentation visible sur YouTube : https://youtu.be/RW0-QIJttBM
Sortir de l’ère des héros - HumanTalks Paris Mars 2017
Votre projet marche, mais c'est le chaos. Comment arrêter de dépendre de ces "héros" sur qui tout repose ?
Présentation vidéo : https://youtu.be/aClcNdOqtsE
More from Jean-Pierre Lambert (18)
Sortir de l'ère des héros - l'excellence comme clé d'une organisation résiliente
Sortir de l'ère des héros - l'excellence comme clé d'une organisation résiliente
Awareness session: Agile -- by Jean-Pierre Lambert
Awareness session: Agile -- by Jean-Pierre Lambert
Formation stratégie de test - créer un produit de qualité
Formation stratégie de test - créer un produit de qualité
[V2] La collaboration, signe d'une véritable agilité
[V2] La collaboration, signe d'une véritable agilité
[V1] La collaboration, signe d'une véritable agilité
[V1] La collaboration, signe d'une véritable agilité
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
Atelier : boostez vos Backlog Grooming/Refinement avec l'Example Mapping ! --...
MiXiT 2018 - Retour d'expérience France Télévisions - Passer de faire de l'Ag...
MiXiT 2018 - Retour d'expérience France Télévisions - Passer de faire de l'Ag...
Une semaine dans ma peau de Scrum Master - V0 - Meetup Renault Digital
Une semaine dans ma peau de Scrum Master - V0 - Meetup Renault Digital
Agile En Seine 2017 - Retour d'expérience France Télévisions - Passer de fair...
Agile En Seine 2017 - Retour d'expérience France Télévisions - Passer de fair...
Sortir de l’ère des héros - HumanTalks Paris Mars 2017
Sortir de l’ère des héros - HumanTalks Paris Mars 2017
Recently uploaded
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Building RAG with self-deployed Milvus vector database and Snowpark Container...
This talk will give hands-on advice on building RAG applications with an open-source Milvus database deployed as a docker container. We will also introduce the integration of Milvus with Snowpark Container Services.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
20 Comprehensive Checklist of Designing and Developing a Website
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentationsRecently uploaded (20)
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
Building RAG with self-deployed Milvus vector database and Snowpark Container...
Building RAG with self-deployed Milvus vector database and Snowpark Container...
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Example Mapping - quelques exemples
- 3. …? !
- 4. Spécifications exécutables ? Spec by Example, Behavior-Driven Development
- 6. Mise en pratique : Example Mapping Un atelier pour mettre en place la démarche
- 7. Example Map Blog de Cucumber – Example Mapping Introduction http://bit.ly/example-map