Devops for Growth
107.7K views | +2 today
Follow
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tags: 'devops', 'ebook'. Clear
Scooped by Mickael Ruau
Scoop.it!

Réussir sa démarche DevOps

Réussir sa démarche DevOps | Devops for Growth | Scoop.it
Le DevOps est le meilleur moyen de développer, de livrer et de maintenir des applications. Les entreprises qui adoptent le DevOps sont plus rapides et suivent l’évolution des demandes des clients. Toutefois, la création d’une culture agile, réactive, orientée données, ainsi que les processus qui la soutiennent, est plus facile à dire qu’à faire.
Mickael Ruau's insight:
  • La façon dont les données machine peuvent optimiser vos processus DevOps ;
  • Les quatre capacités clés dont doivent disposer les équipes DevOps pour gagner en vitesse et améliorer la satisfaction des clients ;
  • Des exemples d’indicateurs afin de mesurer vos processus DevOps.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

eMag InfoQ FR - DevOps : du Rex aux Outils

eMag InfoQ FR - DevOps : du Rex aux Outils | Devops for Growth | Scoop.it
Dans ce premier eMag, nous parlerons DevOps : un retour d'expérience de Déploiement Continu avec intérêts et difficultés rencontrés, ainsi qu'une perspective complémentaire autour de l'Intégration Continue, suivi d'un éclairage sur le tuning de performance et ses caractéristiques dans l'environnement actuel. Et pour finir, la gestion des logs avec une critique de LogStash Book.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Mini-book: Organization Dynamics with —

This mini-book contains 6 articles by the authors of Team Topologies - Matthew Skelton and Manuel Pais - that cover key aspects of modern organization dynamics. In this mini-book How to break apart a monolith without destroying your team Forget monoliths vs. microservices. Cognitive load is w
Mickael Ruau's insight:
In this mini-book
  • How to break apart a monolith without destroying your team

  • Forget monoliths vs. microservices. Cognitive load is what matters

  • Why teams fail with Kubernetes — and what to do about it

  • How to find the right DevOps tools for your team

  • Why you should hire DevOps enablers, not experts

  • Are poor team interactions killing your DevOps transformation?

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

Free DevOps eBook (The Handbook For Beginners)

Free DevOps eBook (The Handbook For Beginners) | Devops for Growth | Scoop.it
This free DevOps handbook covers the DevOps process from the beginning to the end. It's the prefect eBook to help beginners get started. Learn wh
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

A beginner's guide to GitOps and how it works

A beginner's guide to GitOps and how it works | Devops for Growth | Scoop.it
Learn more about GitOps and how it offers infrastructure automation using DevOps best practices.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Software Engineering at Google: Practices, Tools, Values, and Culture

Software Engineering at Google: Practices, Tools, Values, and Culture | Devops for Growth | Scoop.it
The book Software Engineering at Google provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.
Mickael Ruau's insight:

Key Takeaways

  • We wrote “Software Engineering at Google” for people at all levels of experience, from students to engineering policy makers. We’ve tried hard to not say “This is the one true way to do it,” because we recognize that our scale and resources are wholly different than other organizations.
  • Software engineering is not (just) programming, it’s programming over time. We’re focused mostly on how to keep things sustainable over time, and how to coordinate and collaborate with other people. There is very little code in the book, but it’s still very much about software.
  • Google is imperfect, both technically and organizationally. You can see that in our handling of technical issues like maintenance of external packages, and also in our cultural issues around equity and diversity. 
  • Code review is not primarily about defect-detection, it’s more useful as a communication exercise. It provides a great opportunity for education, and establishing a shared understanding.
  • Choice is often the enemy of efficiency in technical domains. Our version control and dependency management policies work mostly by removing options from our engineers. If you don’t have a choice, you don’t have a problem.
 

The book Software Engineering at Google curated by Titus Winters, Tom Manshreck and Hyrum Wright provides insights into the practices and tools used at Google to develop and maintain software with respect to time, scale, and the tradeoffs that all engineers make in development. It also explores the engineering values and the culture that’s based on them, emphasizing the main differences between programming and software engineering.

InfoQ readers can download a sample of the book Book Software Engineering at Google.

InfoQ interviewed Titus Winters, Tom Manshreck and Hyrum Wright, about software engineering at Google.

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

Comprendre les apports d’Accelerate dans l’évolution de nos systèmes | OCTO Talks !

Comprendre les apports d’Accelerate dans l’évolution de nos systèmes | OCTO Talks ! | Devops for Growth | Scoop.it

Pour aborder cet article, une connaissance préalable des principaux éléments que contient Accelerate est recommandée. Si vous n’êtes pas encore sensibilisé au sujet, vous trouverez une introduction et la vidéo d’une matinale sur le sujet dans cet article. Pour un bref rappel, Accelerate est un livre. C’est une forme de compte rendu d’une étude qui cherche à définir ce qui permet aux organisations d’atteindre leurs objectifs avec le plus d’efficience. C’est le résultat de l’analyse de 4 années de State of DevOps. Cette étude met en évidence quatres indicateurs permettant de prédire la capacité des organisations à atteindre leurs objectifs. Plus précisément, les organisations les plus performantes, selon ces indicateurs, atteignent deux fois plus souvent leurs objectifs que les organisations les moins performantes. Dans le cadre de la même étude, un certain nombre de capacités (méthodes, techniques, caractéristiques) souvent déjà bien connues sont énumérées. La particularité ici est que l’étude prédit que leur usage permet d’améliorer le niveau des indicateurs. Mais qu’est-ce qu’Accelerate par rapport à un système d’information ? Quelle est la portée de cette étude dans nos systèmes ? Dans cet article, nous aborderons le sujet de façon abstraite, libre de toute spécificité des systèmes techniques. 

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

DevOps Mythbusting | Puppet

DevOps Mythbusting | Puppet | Devops for Growth | Scoop.it
Puppet automates away the challenges, complexity, and risk of securing and running global hybrid and cloud-native infrastructure, so you can focus on delivering the next great thing.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Free eBooks for SysAdmins and DevOps –

Free eBooks for SysAdmins and DevOps – | Devops for Growth | Scoop.it
This wiki doc lists free eBooks that are of interest to SysAdmins and DevOps. When you add an eBook, please use the same format as the other books, and make sure that you insert it into the correct section. Newer books should be at the top of the section. Author Recent Posts Michael PietroforteMichael Pietroforte is the founder and editor […]
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Embrace DevOps: Your guide to the DevOps lifestyle | eBook Download

Embrace DevOps: Your guide to the DevOps lifestyle | eBook Download | Devops for Growth | Scoop.it
Learn how Lean principles, a diverse workforce, and a good roadmap all help to build better products with greater speed.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

The Phoenix Project — Summary - Lopamudra Misra

The phoenix project Gene Kim, Kevin Behr and George Spafford was in my reading list for a quite long time. Finally was able to read and I must say was not able not keep it away until the end. While…
Mickael Ruau's insight:

Apart from the 3 ways, the book talks about the 4 categories of work

  • Planned Work — these are typically business projects or new features
  • Internal Projects — server migrations, software updates and so on
  • Changes — usually driven by feedback on already completed work
  • Unplanned Work — support escalations and emergency outages
No comment yet.