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

[1404.3056] Principles of Antifragile Software

The goal of this paper is to study and define the concept of "antifragile
software". For this, I start from Taleb's statement that antifragile systems
love errors, and discuss whether traditional software dependability fits into
this class. The answer is somewhat negative, although adaptive fault tolerance
is antifragile: the system learns something when an error happens, and always
imrpoves. Automatic runtime bug fixing is changing the code in response to
errors, fault injection in production means injecting errors in business
critical software. I claim that both correspond to antifragility. Finally, I
hypothesize that antifragile development processes are better at producing
antifragile software systems.
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!

Doing Scrum with Multiple Teams: Comparing Scaling Frameworks

Doing Scrum with Multiple Teams: Comparing Scaling Frameworks | DEVOPS | Scoop.it
Many companies have successfully scaled Agile, and by nature they have done it differently. To speed up your implementation there are several frameworks that can work as a staring point; LeSS, SAFe, and Scrum@Scale. In this article we help you choose by giving you a short description and exploring their similarities and differences.
Mickael Ruau's insight:

What LeSS, SAFe and Scrum@Scale have in common

All three frameworks start with cross-functional, self-organizing Scrum teams. The teams vertically slice requirements into the smallest possible increments that can be deployed independently. Teams are also expected to focus on technical excellence such as doing continuous integration and automated regression testing. At the end of every sprint the teams should have a potentially deployable product. The three frameworks also encourage you to use Lean principles to optimize your flow.

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

Unprofitable Products: How to Manage Products that Lose Money

Unprofitable Products: How to Manage Products that Lose Money | DEVOPS | Scoop.it
We explore how to manage unprofitable products and why companies like Amazon, Uber, Spotify are hailed as innovative disruptors despite losing money.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Heroes are Expensive - Extinguishing the Firefighting Culture

Heroes are Expensive - Extinguishing the Firefighting Culture | DEVOPS | Scoop.it
Sue Johnston discusses avoiding a “hero” culture, and the need to create realistic expectations based on the patterns of effective teamwork.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Collaborative Daily Scrum - An Alternate to 3 Questions Based Daily Scrum

Collaborative Daily Scrum - An Alternate to 3 Questions Based Daily Scrum | DEVOPS | Scoop.it
A lot of Scrum teams use 3 questions based daily scrum. On surface it looks good but it comes with some inherent problems:
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

How Uber, Facebook, and Netflix Do SSH

How Uber, Facebook, and Netflix Do SSH | DEVOPS | Scoop.it
How are some big, well-known companies approaching SSH? We took a look at three who are setting an example for others to follow.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Code reviews are not (primarily) for finding bugs - Azure DevOps | Microsoft Docs

Code reviews are not (primarily) for finding bugs - Azure DevOps | Microsoft Docs | DEVOPS | Scoop.it
Peer code reviews are a standard practice in software engineering. Open source workflows especially are designed to enforce a successful peer review before the merge of a change into the main codebase. Who reviews code and accepts or blocks the change from becoming a part of the codebase is crucially important.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Play the Customer Development Game

Agile teams are great at building what you want - but how do you know what your customers need? This game-based workshop shows you how to discover the right pr…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Human talks - Ratez vos revues de code en 5 leçons

Session donnée le 13/10/2015 à Human Talks Paris, proposant plusieurs conseils pour mieux réussir ses revues de code en pair.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Développement guidé par la résolution des problèmes

Beaucoup d’entre nous limitent la résolution de problème à la simple élimination du “Muda”. Après un an et demi de pratiques diverses et variées, au sein d'une…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Practical Styles of Pair Programming — Xebia Blog

Without exception in all teams I’ve developed software in people have expressed their aversion against pair programming. It’s not that developers don’t want to try, or that they don’t believe it will help. On the contrary, they are usually very enthusiastic about trying it and give it more than a fair chance. After a few days they sit alone behind their keyboard coding like zombies with headphones. What’s going on? Is pair programming too hard? Doesn’t it pay off? In this post I’ll try to explain what I think is happening, and I will give you some clear pointers to avoid the traps. At the end I will go into distributed teams and what part of the game changes there.

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

Clean Code III - Software Craftsmanship

You will learn why naming is really difficult if done right, why coding and style guidelines are crucial, code structuring, exception handling and why other el…
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Complexity, context and collaboration from manufacturing software to …

Manufacturing practices abound at Agile conferences but is software something that comes of a production line (albeit in small batch sizes)? Should we instead think of software development as a service? Can we combine unarticulated customer needs with novel technology to shift the business forward rather than simply respond to demand? Should we see applications as emergent properties of complex interactions between people and software objects over time? What sort of ecosystem (rather than architecture) is needed for such an approach? Using the popular Cynefin framework as a starting point, its creator will explore these questions.

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

Psychological Safety in Post-Mortems

Psychological Safety in Post-Mortems | DEVOPS | Scoop.it
Emotions often come to the fore when there is an incident; psychological safety in blameless post-mortems is essential for the learning process to happen. The post-mortem session must be fairly moderated, preferably by an outsider, giving everyone a turn to speak without criticism. Don’t start the analysis of the incident before there is a clear and common understanding of what actually happened.
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Project Management 101: The Complete Guide to Agile, Kanban, Scrum and Beyond - The Ultimate Guide to Project Management

Project Management 101: The Complete Guide to Agile, Kanban, Scrum and Beyond - The Ultimate Guide to Project Management | DEVOPS | Scoop.it
Read or Download Project Management 101: The Complete Guide to Agile, Kanban, Scrum and Beyond from our The Ultimate Guide to Project Management e-book for FREE and start learning today!
Mickael Ruau's insight:

 

Popular Project Management Systems

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

Writing Your First Postmortem

In part 2, I’m going to dive into the wonderful world of root causes, probably the most important – and most difficult – element in conducting a postmortem.

Mickael Ruau's insight:

 

Here’s a summary of what each section in the template postmortem is about, including short examples:

  • Title – Name of the postmortem, e.g. “Deployer API Outage Postmortem”
  • Date – When the incident happened, e.g. “2016-09-05”
  • Authors – List of people who wrote the postmortem (GitHub handles work fine)
  • Status – Current status of the postmortem, e.g. “Complete, action items in progress”
  • Summary – A one-sentence summary of the incident, usually something like “Service X was down for N minutes due to Y”
  • Impact – The incident’s impact on customers and, if known, revenue or reputation, e.g. “Users were unable to do X while service Y was unavailable from 09:29 to 10:00 UTC”
  • Root Causes – A list of causes that have contributed to the incident (I’ll cover root causes in part 2 of this article)
  • Trigger – What triggered the outage? e.g. “Merging pull request X which started the rollout of broken software Y”
  • Resolution – The action(s) that mitigated and resolved the outage, e.g. “Disabling feature X helped to mitigate the problem. Rolling back to version Y resolved it.”
  • Detection – How the problem was noticed, e.g. “Pingdom detected that service X was down and paged on-call via PagerDuty”
  • Actions Items – A list of actions taken (with links to GitHub issues) to mitigate or resolve the incident, and to prevent it from recurring
  • Lessons Learned – What went well? What went wrong? And what was sheer luck?
  • Timeline – A detailed timeline of the events related to the incident
  • Supporting Information – Additional graphs, screenshots, command output, etc.

Postmortems are a collaborative effort thriving on feedback. Make sure to share first drafts internally with your team. Once the review is complete, share the postmortem with as many people as possible.

Always keep in mind: Failure isn’t a disaster, it’s a learning opportunity for the whole company.

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

Let the Elephants Leave the Room: Tips for Making Development Life Le…

As developers, we often complain about the efficiency problems we face while working. We work hard but produce so little that our whole development life turns …
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Mon équipe, Moi et le Pair Programming à temps complet

Ne pas avoir son propre ordinateur mais partager le même ordinateur avec son binôme : voilà ce qui explique le pair-programming à temps complet.

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

/etc/notes — A personal blod about software engineering

/etc/notes — A personal blod about software engineering | DEVOPS | Scoop.it
Read Part 1: link
Properties of good SLI metrics In this section, we will talk about how to choose good metrics(SLI). First of all, let’s think about our target. We need to make our users are happy. Good SLI should have some characteristics:
predictable relationship with user happiness shows service is working as users expect to expressed as: good events / valid events aggregated over a long time horizon How do you think why the upper metric is bad?
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Les Aventures d'Alice - la Révolte des Tests

Alice rêve de tests à ajouter dans son application quand elle aperçoit le Lapin blanc soucieux de qualité. Partie à sa poursuite, elle se trouve propulsée dans un monde ressemblant étrangement à son code, et commence à faire apparaître de nombreux tests unitaires. Pourtant, le Lapin blanc est encore insatisfait ; lesdits tests se rebellent, deviennent incontrôlables et ne veulent plus vérifier ce qu'elle veut. Comment Alice va-t-elle réussir à reprendre la main sur les tests et les faire fonctionner correctement ?

 

À travers les aventures d'Alice, je vais vous présenter les pièges courants du testing qui découragent souvent les débutants, mais également les bonnes pratiques et des outils pour obtenir des tests fonctionnels et efficaces.

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

Tdd 2 : opinions, alternatives et compléments

opinions, alternatives et compléments au Test Driven Development
more...
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Table of Contents

Table of Contents | DEVOPS | Scoop.it

This is an alphabetical index of the cards in the Xebia Essentials deck.

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

Pair programming anti patterns

Pair programming offers an extensive list of benefits. While it still remains a controversial practice, many teams have adopted pair programming

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

Innovation Funnel for R&D Projects and Ideas - Ahmad Bilal

o Internal Technology or Products Roadmap: This is the internal technology or product roadmap of the organisation. In which areas organisation wants to develop its future competitive technologies…
Mickael Ruau's insight:

Innovation Funnel for R&D Projects Concepts Development:

 
Figure: Innovation Funnel for R&D Projects concept development
more...
No comment yet.