 Your new post is loading...
Your new post is loading...
|
Scooped by
Mickael Ruau
November 16, 2020 3:00 AM
|
Avez-vous déjà mis en place des tests sur un projet qui n'en avait aucun ? Du multi-tenant sur un produit mono-tenant ? Un outil d'analyse statique de code sur un projet bien avancé ? C'est (très) douloureux, n'est-ce pas ?
|
|
Scooped by
Mickael Ruau
February 4, 2019 7:24 AM
|
Pourquoi un cahier des charges peut mener à un echec ? Comment l'éviter ? Retour sur la définition d'un cahier des charges, les erreurs à éviter, etc.
|
|
Scooped by
Mickael Ruau
May 16, 2018 12:22 AM
|
Le cahier des charges traditionnel n’est plus adapté à l’exploitation d’une idée. Entre l’idée et le lancement d’un projet, il peut s’écouler des mois et à l’échelle digitale, c’est une éternité.
|
|
Scooped by
Mickael Ruau
January 9, 2018 2:52 AM
|
J’ai eu l’opportunité de proposer l’atelier « Questionner son cahier des charges » à Paris Web 2017. Pendant cet atelier, beaucoup de choses importantes ont été dites, on s’est marré, on a dessiné. Aujourd’hui, j’ai la chance de pouvoir revenir dessus dans cet article et même d’aller plus loin. Alors, pourquoi passer 1h30 à « questionner son cahier des charges » ?
|
|
Scooped by
Mickael Ruau
April 14, 2017 9:30 AM
|
Gap analysis describes differences between required and actual systems. You can use it to analyze both computer systems and other business functions. Functional gap analysis characterizes the differences between what a system can do and what it is supposed to do. Functional gap analysis looks at gaps in various types of functions and determines whether the gaps are critical or whether the users of the system can accommodate them. For non-critical gaps, the analysis provides solutions that involve changes to system configuration or to user practices.
|
|
Scooped by
Mickael Ruau
April 14, 2016 7:40 AM
|
Retour d'expérience autour d'une session de Sprint (anciennement Design Sprint) pour un sujet sur le quel je suis intrapreneur au sein d'OCTO : Virtuose.
|
|
Scooped by
Mickael Ruau
April 13, 2016 3:44 AM
|
Design Sprints at the BBC
|
|
Scooped by
Mickael Ruau
April 6, 2016 12:58 AM
|
My experience from running a Design Sprint for 90Min - a football platform product with over 30 million users per month and $40M in funding.
|
|
Scooped by
Mickael Ruau
April 5, 2016 4:03 AM
|
DTHSG.COMEstablished in 2005. Prototyping since back then.
|
|
Scooped by
Mickael Ruau
April 5, 2016 4:01 AM
|
In this presentation we explore the link between business need and customer need and how to innovate (and remove business problems or discover business opportu…
|
|
Scooped by
Mickael Ruau
April 3, 2016 1:32 AM
|
This post will teach you to run a Product Design Sprint, which can be performed as a stand-alone effort or as part of a larger Agile development process.
|
|
Scooped by
Mickael Ruau
July 17, 2015 3:17 AM
|
Lorsque les Users Stories sont trop volumineuses, les diviser peut vite devenir une mission impossible. Entre le point de vue technique du fractionnement de l’équipe et le point de vue fonctionnel du client, comment réussir à diviser une User Story intelligemment ? Essayez la méthode du Hamburger.
|
|
Scooped by
Mickael Ruau
June 1, 2015 4:27 AM
|
Requirements checklists are lists of critical considerations that a deliverable should address or typical defects to look for (duplicated information, missing information, unclear information etc.). Items on the checklist are items that are deemed critical either by competent authority (the individuals who need the deliverable to do their jobs) or by feedback from previous work efforts.
|
|
|
Scooped by
Mickael Ruau
February 20, 2019 1:43 AM
|
How to Use This Kit The Design Sprint Kit is an open-source resource for design leaders, product owners, developers or anyone who is learning about or running Design Sprints. Whether you are new to Design Sprints and gaining buy in for your first Sprint, or an experienced Sprint facilitator looking for new methods, this site will help you learn, plan, and contribute to the Design Sprint Methodology. Sprint Methodology Learn about Design Sprints Planning Overview Plan Your Next Design Sprint Methods & Recipes Contribute to the Kit
|
|
Scooped by
Mickael Ruau
July 16, 2018 4:43 AM
|
Présentation des UX Cards - cartes d'idéation basée sur une approche psychologique du design UX. Outil développé dans le cadre de la thèse de Carine Lallemand …
|
|
Scooped by
Mickael Ruau
January 30, 2018 1:40 AM
|
L'impact mapping permet à l'équipe d'aligner son activité avec les objectifs métiers en facilitant les décisions stratégiques. Découvrez cet outil !
|
|
Scooped by
Mickael Ruau
January 6, 2018 5:03 AM
|
Dans un projet ERP, la phase cahier des charges permet de formaliser ses besoins et mettre en avant ses spécificités pour garantir la réussite du projet.
|
|
Scooped by
Mickael Ruau
April 5, 2017 9:18 AM
|
|
|
Scooped by
Mickael Ruau
April 14, 2016 3:51 AM
|
Google Ventures' Jake Knapp lists the people and things you'll want on hand to start tackling a big design challenge.
|
|
Scooped by
Mickael Ruau
April 7, 2016 3:39 AM
|
Quick guide to the Design sprint. The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas wi…
|
|
Scooped by
Mickael Ruau
April 5, 2016 4:12 AM
|
Design Thinking Process (Re)define the problem Design never ends Needfinding & Synthesis Understand the users & the design space Ideate Brainstorm Prototype Bu…
|
|
Scooped by
Mickael Ruau
April 5, 2016 4:02 AM
|
This is a short talk and workshop (30' + 90') to give a first introduction to design thinking. Gives theory foundation, notes a few different approaches, and t…
|
|
Scooped by
Mickael Ruau
April 4, 2016 12:29 AM
|
What I want to show is how a resource-constrained startup was able to use a Design Sprint as an invaluable tool to get a lot of shit done in a short amount of time, in a vertical we lacked expertise: design. At Tutum, we recently ran a week long design sprint to completely re-design our…
|
|
Scooped by
Mickael Ruau
November 26, 2015 3:23 AM
|
Sessions B2B (Back to Basic) sur le Story Mapping et les User Story présentée au Scrum Day France 2015
|
|
Scooped by
Mickael Ruau
June 4, 2015 2:28 AM
|
Mistakes are unavoidable, and so the principle is to find each error close to the time at which it was introduced. The longer a defect stays in the software food chain, the more it contaminates work further down the chain. Since requirements and architecture are done first, those defects have the potential to contaminate more work and to be most expensive. Studies over the last 25 years have proven that it pays to remove defects early. Organizations have found that purging requirements and architecture errors before detailed construction begins reduces rework costs by 90-99%, compared to correcting those errors during system test or after release.
|
Scoop.it!
