DEVOPS
53.9K views | +1 today
Follow
 
Scooped by Mickael Ruau
onto DEVOPS
Scoop.it!

Speed Boat

Speed Boat | DEVOPS | Scoop.it
Speed Boat Dans la lignée des « Innovation Games » et la palette d’ apprentissage par le jeu … le Speed boat. Les buts du speed boat Read More...
gestion de projet
more...
No comment yet.
DEVOPS
DEVOPS, agilité, tests, déploiement, sécurité
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...
Scooped by Mickael Ruau
Scoop.it!

7 Free Tools to Help You Win Startup Weekend – Jon Church –

A list of the tools my team used to help us move quickly enough to develop a winning pitch and prototype in 54 hours. We won Techstars Startup Weekend 2017 in Gainesville, FL. Get everyone on your…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Le chaos engineering –

Le chaos engineering – | DEVOPS | Scoop.it

Cet article s’insère dans notre série « Chaos Engineering ».

Le contexte

Les architectures applicatives actuelles s’éloignent de plus en plus d’une structure en blocs monolithiques, pour s’orienter vers des architectures basées sur de la composition de services et structurées en systèmes distribués, notamment par l’utilisation des micro-services.

Les applications basées sur ces architectures proposent des fonctionnalités provenant de l’interaction de leurs composants, et de la bonne collaboration de l’ensemble des composants.

Les composants de ces architectures peuvent se compter par centaines, ce qui apporte des problématiques de gestion applicatives de plus en plus liées aux systèmes distribués, et acquièrent des propriétés similaires à celles des systèmes complexes.

Mickael Ruau's insight:

 

Un système complexe peut être défini de plusieurs façons d’après le prisme dont il est observé, nous considèrerons les quelques propriétés essentielles suivantes, utiles pour la suite:

  • il est composé d’un grand nombre d’éléments en interaction et ce, de manière simultanée
  • le comportement d’un système complexe est très difficile à modéliser, même en connaissant parfaitement chaque élément de ce système. Le comportement est émergent, car il est issu des différentes interactions entre les éléments le composant.
  • l’action d’un composant peut avoir un effet sur son propre état, sur l’état d’autres composants et sur l’état global du système par propagation
  • la connaissance d’une partie du système ne permet pas de déterminer l’état global du système

Les fonctionnalités proposées par une application sur l’interaction de composants à l’intérieur d’un système complexe seront donc systémiques, et dépendantes du bon fonctionnement et de la bonne coordination des différents composants.

Malheureusement, la moindre faille peut avoir des conséquences lourdes sur la bonne fonctionnalité de ces systèmes (voir propriétés ci-dessus), et il est très difficile, voire impossible de modéliser l’ensemble des conséquences pouvant émerger de la faille d’un composant (failles en cascade, goulot d’étranglement) et/ou de l’orchestration de différents composants (« retry storms »).

Les tests existants (unitaires, intégration, techniques) permettent de tester la bonne fonctionnalité de composants isolés, ou en intégration simple, mais restent très limités dans la possibilité de tester la robustesse d’un système complexe à l’échelle réelle car ils restent déterministes.

Utiliser un environnement autre que l’environnement réel peut aussi entraîner des biais qui fausseront les observations et la possibilité de les transposer dans la réalité.

On pré-supposera finalement que le fait d’observer le système réel n’a pas d’impact conséquent sur le comportement de ce système.

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Chaos Monkey — Wikipédia

Chaos Monkey - Wikipédia

Le concept de Chaos Monkey a été inventé en 2011 par Netflix pour tester la résilience de ses infrastructures informatiques. Le but de cet outil est de simuler des pannes en environnement réel et de vérifier que le système informatique continue à fonctionner.

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Sketchnotes: Why the Lean Startup Changes Everything

75% of startups fail. The Lean Startup method, based on experimentation, customer feedback, and iterative design can result in fewer failures leading to lowered risk for loosing resources. It’s the…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Lessons Learned: The one line split-test, or how to A/B all the time


Split-testing is a core lean startup discipline, and it's one of those rare topics that comes up just as often in a technical context as in a business-oriented one when I'm talking to startups. In this post I hope to talk about how to do it well, in terms appropriate for both audiences.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Magic of Paper Prototyping –

In the world of digital design, we have a lot of different tools that make the process of prototyping really simple. But still pen and paper remain the most useful tools for UX designers. Paper…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The State of Sales & Marketing at the 50 Fastest-Growing B2B Companies

In order to make the qualitative portion of our research more tangible, we evaluated each company on the list in light of how they approached content, customer communication, path to purchase, and pricing. 

What we and the team at Drift.com discovered was surprising, to say the least.

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Visual Action Board (for Value Check, English Edition)

This board can make you to validate value hypothesis of your business model. You can plan an experiment and check the real action status as SCRUM project manag…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Mafia offer, l’offre irrésistible

Mafia offer, l’offre irrésistible | DEVOPS | Scoop.it
une offre irrésistible répond à plusieurs autres caractéristiques :

C’est une offre qui se démarque radicalement de celles de ses concurrents,
C’est une offre tellement en rupture avec les pratiques du secteur que les concurrents ne veulent ou ne peuvent pas l’imiter.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

A Google Design Sprint Gone Wrong (And What It Taught Me)

A Google Design Sprint Gone Wrong (And What It Taught Me) | DEVOPS | Scoop.it
Sprints are all the rage, but beware the snake-oil! This is what I learnt by taking part in a modified design sprint, run by people with incomplete understanding of the Google Ventures Design Sprint process. Jake Knapp describes Design Sprints as a greatest hits of productivity, decision making, innovation, creativity, and design — and I think that’s true. But I... Read More →
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Comment (peut-être) gagner un Startup weekend ?

Comment (peut-être) gagner un Startup weekend ? | DEVOPS | Scoop.it

Résumé Il y a quelques jours, j’ai participé à un Startup Week-end. J’étais parti pour aider une équipe mais finalement, j’ai présenté ma propre idée qui a été sélectionnée. 50 heures plus tard, le jury a désigné notre équipe comme grand gagnant !
Je vous donne la recette secrète : une organisation sans faille pour présenter ce que le jury attend (un idée validée par le marché, un prototype, un design, une ergonomie et une proposition de valeur liée à un modèle économique).

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The ultimate guide to winning startup weekend

As Startup Weekend season is upon us, I thought it was about time that we put together a guide to winning. Having won and mentored at 10+ startup weekends, we have seen the same mistakes over and over. The aim of this guide is to give every single team the best chance at coming away …
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The InfoQ eMag: Chaos Engineering

The InfoQ eMag: Chaos Engineering | DEVOPS | Scoop.it
This eMag will inspire you to dig deeper into your systems, question your mental models, and use chaos engineering to build confidence in your system’s behaviors under turbulent conditions.
Mickael Ruau's insight:

At Netflix, we’ve been embracing chaos engineering since Chaos Monkey was born in 2011. It has gone through several iterations and tools that eventually evolved into the Failure Injection Testing (FIT) platform and, ultimately, ChAP (a platform for safely automating and running chaos experiments in production) through the efforts of many amazing engineers. We’ve taken the opportunity to outline why this has been so beneficial for the business in a separate IEEE article titled “The Business Case for Chaos Engineering” and a free e-book from O’Reilly here.

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Sketchnotes [MVPs] – The Creative Founder : NightCap edition –

“Sketchnotes [MVPs]” is published by Ruitao Liang in The Creative Founder : NightCap edition
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Lean Startup : 6 étapes pour se lancer

Lean Startup : 6 étapes pour se lancer | DEVOPS | Scoop.it
Grâce à la méthode Lean Startup, transformez votre idée en succès! Voici les 6 étapes à suivre et les meilleurs outils pour vous lancer efficacement.
Mickael Ruau's insight:

Vous pouvez également booster votre notoriété en présentant votre service à des sites tels que : Maddyness, Les Pépites Tech ou encore Product Hunt.

 

Faites vous identifier de google. Travaillez votre référencement en identifiant les mots clés générateurs de trafic et en produisant du contenu pertinent, à forte valeur ajoutée.

 

Enfin, prenez le temps de soigner vos 300 premiers clients, ce sont eux qui vous rapporteront le plus. N’hésitez pas à les contacter, laisser toutes vos coordonnées email et tel perso pour les soigner au mieux et être toujours disponible.

 

Voici quelques sources d’inspirations pour compléter cette partie notoriété et acquisition : 

  • GrowthHacking (FR), pour trouver des conseils marketing (réseaux sociaux, landing page, emailing, etc)
  • GrowthHackers (EN), pour lire des articles pertinents sur le growth hacking
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Lessons Learned: Validated learning about customers

Lessons Learned: Validated learning about customers | DEVOPS | Scoop.it

Would you rather have $30,000 or $1 million in revenues for your startup? Sounds like a no-brainer, but I’d like to try and convince you that it’s not. All things being equal, of course, you’d rather have more revenue rather than less. But all things are never equal. In an early-stage startup especially, revenue is not an important goal in and of itself.

This may sound crazy, coming as it does from an advocate of charging customers for your product from day one. I have counseled innumerable entrepreneurs to change their focus to revenue, and many companies who refuse this advice get themselves into trouble by running out of iterations. And yet revenue alone is not a sufficient goal. Focusing on it exclusively can lead to failure as surely as ignoring it altogether.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Lessons Learned: The Entrepreneur’s Guide to Customer Development


Brant Cooper and Patrick Vlaskovits have written a new book, The Entrepreneur’s Guide to Customer Development, which builds upon the foundational work of The Four Steps to the Epiphany, while improving accessibility, updating the ideas, and making it more actionable. I believe it is the best introduction to Customer Development you can buy.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Business Model Map - English Edition

Business Model Map is a cross-over diagram among Blue Ocean Strategy, Service Design, Lean Startup and BM Canvas. The backbone of business model map is 'Busine…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

eMag: Lean Startup

eMag: Lean Startup | DEVOPS | Scoop.it
Download the Lean Startup eMag to discover ways to determine customer needs and decide which products to develop or services to provide, helping you to deliver business value to your customers.

Free download
Mickael Ruau's insight:

Contents of the Lean Startup eMag include:

  • Sell Before You Build “Before you write any code, make sure you have a failing test.” This was revolutionary when first pitched in the late 90’s. Many successful entrepreneurs have practiced a similar idea: “Before you build a product/service, make sure you have paying customers.” Naresh Jain explains his approach of finding effective MVPs to validate his Educational Product and why Agile Methods simply fail to do so.
  • Minimum Viable Products for Enterprises Enterprise software startups use a minimum viable product (MVP) to learn about customers with limited effort and money. How can organizations deploy lean startup principles to develop a viable product for their stakeholders?
  • Building Scalable Products that Customers Love Per Jonsson discusses Lean Startup in the context of real world examples, and helpful tools for startups - Feedback Loop, Customer Development and the Lean Canvas.
  • Interview with Brian Murray from Yammer about Lean Startup and using Minimum Viable Products Brian Murray explains how Yammer uses Minimum Viable Products to test their business customer hypotheses, and why they focus so much attention on the architecture of their products.
  • Managing Experimentation in a Continuously Deployed Environment Wil Stuckey explains how Etsy manages to deploy nearly ~10,000 changes in one year, and how they run A/B experiments in the midst of continual code change.
  • Communicate Business Value to Your Stakeholders Learn why and how to communicate benefits rather than features - and what it will mean for you, your team and your organization.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Inside Azure Search: Chaos Engineering | Blog | Microsoft Azure

Inside Azure Search: Chaos Engineering | Blog | Microsoft Azure | DEVOPS | Scoop.it
As systems scale, we expect nodes to fail ungracefully in random and unexpected ways, networks to experience sudden partitions, and messages to be dropped at any time. Azure Search uses chaos engineering to help solve this problem.
Mickael Ruau's insight:

Chaos Engineering in Action

To illustrate how this works, here’s a recent example of a failure that was driven from extreme chaos to low chaos using this model. Extreme chaos: Initial discovery.  A service emitted an unexpected low-priority alert.  Upon further investigation, it ended up being a downstream error signifying that at least one required background task was not running.  Initial classification put this error at extreme chaos – it left the cluster in an unknown state and didn’t alert correctly. High chaos: Mitigation.  At this point, we were not able to automate the failure since we were not aware of the root cause.  Instead, we worked to drive the failure down to a level of high chaos.  We identified a manual fix that worked, but impacted availability for services without replicas.  We tuned our alerting to the correct level so that the engineer on call could perform this manual fix any time the error occurred again.  Two unlucky engineers were woken up to do so by high priority alerts before the failure was fixed. Automation.  Once we were sure that our customer services were safe, we focused our efforts on reproducing the error.  The root cause ended up being unexpected stalls when making external calls that were impacting unrelated components.  Finding this required the addition of fault injection to cause artificial latency in the component making the calls. Low chaos: Fix and verification.  After the root cause was identified, the fix was straightforward.  We decoupled the component experiencing latency in calls from the rest of the system so that any stalls would only affect that component.  Some redundancy was introduced into this component so that its operation was no longer impacted by latency, or even isolated stalls, only prolonged and repeated stalls (a much rarer occurrence). We were able to use the automated chaos operation to prove that the original failure was now handled smoothly without any problems.  The failure that used to wake up on-call engineers to perform a potentially availability-impacting fix could now be downgraded to a low chaos failure that our system could recover from with no noise at all. At this point, the automated failure could be handed off to the Search Chaos Monkey to run regularly as a low chaos operation and continually verify our system’s ability to handle this once-serious error.  

Chaos Engineering and the Cloud

At Azure Search, chaos engineering has proven to be a very useful model to follow when developing a reliable and fault tolerant cloud service.  Our Search Chaos Monkey has been instrumental in providing a deterministic framework for finding exceptional failures and driving them to resolution as low-impact errors with planned, automated solutions.

more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Définition de la Servuction en Marketing des Services

Définition de la Servuction en Marketing des Services | DEVOPS | Scoop.it
« La Servuction, c’est la manière dont un prestataire manage son entreprise et surtout son client afin de délivrer son Service avec la meilleure Qualité possible, tout en respectant ses objectifs économiques. »
Mickael Ruau's insight:

La différence entre Servuction et Production est managériale

En Production (industrielle), l’entreprise a pour vocation de mettre en œuvre un système de fabrication interne qui permette la mise à disposition de produits avec la Qualité voulue pour répondre à un marché. Si une opération de fabrication dysfonctionne – une machine en panne, un ouvrier qui ne maîtrise pas le poste, … – alors la Qualité n’est pas au rendez-vous.

Dans la fabrication d’une voiture, le client-consommateur n’est pas partie prenante : ses qualités intrinsèques, sa personnalité, son investissement, n’influencent pas la qualité du véhicule produit. La Qualité, le contrôle de gestion, en bref, le système de Management d’un système de Production est indépendant du client (même s’il vise à répondre à ses désirs) : il ne gère que des ressources internes.

En Servuction, tout se complique : s’il faut également gérer les ressources internes, le client a aussi un rôle à jouer dans la « fabrication du service ». Et cela peut entraîner de nombreux déboires si le client, en tant que « ouvrier du service », est mal managé.

Les déboires classiques du management se retrouvent alors dans la relation avec le Client :

  • Il peut ne pas avoir conscience de son rôle
  • Les règles du jeu peuvent ne pas lui avoir été verbalisées
  • Il peut être incompétent
  • Il peut être mal suivi (pour ne pas dire « mal contrôlé »)
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Design Sprints side-by-side service design sprints vs google venture …

Have presented this Design Sprint comparison on 2015 at the Business Analysis Track at Developer's Conference http://www.thedevelopersconference.com.br/tdc/20
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Getting Effective Session Outcomes

As one of the keynote speakers, Tom Chi shares his radical approach to prototyping which is based on key techniques used to build Google Glass, Self-Drivin
more...
No comment yet.