Devops for Growth
82.5K views | +43 today
Follow
 
Scooped by Mickael Ruau
onto Devops for Growth
Scoop.it!

Vidéo 1/8 : Introduction à la gestion de projet

Vidéo 1/8 : Introduction à la gestion de projet | Devops for Growth | Scoop.it

Avant de démarrer, posons les bases.

Définir un projetDifférencier un projet de l’opérationnelLes différentes étapes d’un projetLes critères de réussite d’un projet
Mickael Ruau's insight:
Formation Gestion de Projet

 

La formation vidéo online et gratuite en gestion de projetCliquez ici pour accéder aux vidéos
No comment yet.
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...
Scooped by Mickael Ruau
Scoop.it!

What is the Buyer Readiness State? - Different Stages Of Buyer Readiness

What is the Buyer Readiness State? - Different Stages Of Buyer Readiness | Devops for Growth | Scoop.it
Buyer readiness is used to refer to that particular state which denotes the willingness of any individual customer for buying a specific product & service.
Mickael Ruau's insight:

 

These stages are generally considered to be categories on the basis of psychological behavior rather than just the facts and the figures.  These categories thus depict the thought process of the customers and how he finally gets convinced enough to buy that product finally.

Now those six stages are

  1. Awareness of the existence of the product
  2. Knowledge related to the benefits of the particular product
  3. Initial factors of the interest of the customer in that product
  4. A preference that is given to that particular product over the others in the competitive market
  5. Conviction of that specific product in terms of its suitability and also its purchasing power
  6. Purchasing the product
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

3 Ways to Simply Describe Complex Technical Topics - DZone Agile

3 Ways to Simply Describe Complex Technical Topics - DZone Agile | Devops for Growth | Scoop.it
To be a skilled programmer, you need great coding skills. To be a great programmer, you need more than technical skills. You need to be able to work well with other teams and that requires clear communication.

But it is hard to communicate clearly when you are working on complex technical topics. How do you describe the incredibly complex problems you work on to people outside your team?

If you need to talk about your work to business teams, here are three ways to simply describe complex technical topics.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Modèles de Markov

Modèles de Markov | Devops for Growth | Scoop.it

On dit qu’un modèle possède la propriété de Markov si son état à un instant T dépend uniquement de son état à l’instant T-1. Si on peut observer les états dans lesquels se trouve le modèle à chaque instant, on parle de modèle de Markov observable. Sinon, on parle de modèle de Markov caché.

Dans cet article, nous allons illustrer ces modèles pour comprendre leur fonctionnement et leur utilité.
Mickael Ruau's insight:
 

Modèle de Markov observable

Considérons la situation qui suit :
Vous êtes enfermés chez vous un jour de pluie, et vous aimeriez déterminer le temps qu’il fera lors des cinq prochains jours.

Comme vous n’êtes pas météorologue, vous vous simplifiez la tâche en faisant l’hypothèse que la météo suit un modèle de Markov: le temps qu’il fait au jour J dépend uniquement du temps qu’il fait au jour J-1.

Pour simplifier encore plus, vous considérez qu’il y a seulement trois temps possibles: soleil, nuages ou pluie.

En se basant sur les observations des derniers mois, vous établissez le diagramme de transitions suivant :

 

 

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

TDD vs. BDD vs. ATDD - DZone Agile

TDD vs. BDD vs. ATDD - DZone Agile | Devops for Growth | Scoop.it
Know the key differences between major development methodologies like TDD, BDD, and ATDD that focus on the task of the developers and their creations.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Microservices — the Letter and the Spirit

Microservices — the Letter and the Spirit | Devops for Growth | Scoop.it

Key Takeaways

Microservices pattern doesn’t refer to the size of the services, decomposing your solution into ‘micro’ pieces is not the goal of the pattern, think of your solution as one whole then look at the requirements to guide you through what pieces to partition out. The article gives you an example of doing that.

Mickael Ruau's insight:

Central to the microservices pattern is the concept that services must be decoupled; the end goal of the pattern is to make a distributed solution easy to develop, operate and maintain which can be easier achieved when the services are decoupled.


Decoupling the services is twofold

 

1) Services don’t interact directly with each other, instead they use an integration service.

2) Services are versioned.

 

Using an integration service (e.g. service bus) frees your microservices from depending on each other, a failure of one service shouldn’t cause the other services to fail.

 

Versioning shouldn’t be an afterthought in microservices, implement it at day one. If Versioning seems an overkill you’re probably prematurely ‘microservicing’ your solution.

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

Growth and Competitive Strategy in 3 Circles

Growth and Competitive Strategy in 3 Circles | Devops for Growth | Scoop.it
The 3-Circle model was developed over the past several years, initially in strategic planning for a university graduate program and in an executive MBA course designed to integrate the concepts of marketing and competitive strategy. Over the course of time, the 3-Circle model has been successfully used by hundreds of organizations throughout the world in establishing and growing their market positions. Many of the case examples in this book demonstrating applications of the 3-Circle model applications are from executives who have attended executive education training at the University of Notre Dame.

The development of competitive strategy is difficult because there are a lot of moving parts, as well as hundreds of frameworks, that might potentially guide the effort. Executives appreciate how the 3-Circle model simplifies the integration of customer, firm, and competitor analysis to generate growth strategies. It also provides a common language and process for understanding and explaining competitive advantage and for identifying profitable growth strategy.
Mickael Ruau's insight:

Table of Contents

  • Chapter 1: The Challenges of Growth
  • Chapter 2: Introduction to 3-Circle Analysis
  • Chapter 3: Defining the Context
  • Chapter 4: The Meaning of Value
  • Chapter 5: Sorting Value
  • Chapter 6: Growth Strategy
  • Chapter 7: Implementation: An Inside View of the Organization
  • Chapter 8: Dynamic Aspects of Markets
  • Chapter 9: Summary: Growth Strategy in 10 Steps
  • References
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Java Is More Like English Than You Think - DZone Java

Java Is More Like English Than You Think - DZone Java | Devops for Growth | Scoop.it
As computer code is written by humans, languages must be easy on the brain. Similarities with human language may even predict something about their evolution.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Building High-Quality Software - DZone Performance

Building High-Quality Software - DZone Performance | Devops for Growth | Scoop.it
How do you define good quality software? How do you develop, measure, and ensure its quality? Read this post to learn the answer to these questions and more.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

DevSecOps: A Complete Guide - DZone Security

DevSecOps: A Complete Guide - DZone Security | Devops for Growth | Scoop.it
Why should you learn about the basics of DevSecOps even if you’re not a software developer? The short answer is to improve security at your business or company.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Designing Powerful Questions — Hands-on Agile 35

Designing Powerful Questions — Hands-on Agile 35 | Devops for Growth | Scoop.it
� Daniel Stillman: Designing Powerful Questions to help you Coach, Create, Connect and Lead — Hands-on Agile 35 — Age-of-Product.com.
No comment yet.
Rescooped by Mickael Ruau from Formation professionnelle - FTP
Scoop.it!

Nouvelles organisations du travail : le mode hybride, vecteur de la transformation de l’organisation du travail et des relations humaines

Nouvelles organisations du travail : le mode hybride, vecteur de la transformation de l’organisation du travail et des relations humaines | Devops for Growth | Scoop.it
Le télétravail pendant la crise Covid-19 a été globalement une bonne expérience qui a permis à chacun de se réinventer dans ses modes de travail, d’animation et d’utilisation des outils collaboratifs et de se projeter dans l’après. Cette période a été une révolution culturelle importante mais qui, pour être pérenne, doit pouvoir s’ancrer dans un cadre, certes plus flexible mais bien orchestré.

Via Canadian Vocational Association / Association canadienne de la formation professionnelle
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

La gestion de crise dans les projets IT

La gestion de crise dans les projets IT | Devops for Growth | Scoop.it
Un œil externe, non pollué par l’environnement actuel, vaut tous les meilleurs conseils. Il apportera une vision théorique de la conduite d’un projet it, s’adaptera au contexte de votre entreprise et de votre problème, et saura vous proposer des solutions de contournement. Un bon compromis vaut mieux qu’un mauvais conseil. Il faut prendre de la hauteur, appréhender la situation dans son ensemble avec des analyses croisées issues d’expertises de différentes natures, pour avoir une vision qualitative Il est indispensable d’obtenir l’adhésion de vos équipes, de restaurer la confiance et les amener à adopter une démarche constructive en se basant sur une technique de questionnement qui permet à vos collaborateurs d’adopter une attitude favorable à la sortie de crise. Enfin il est essentiel de ne pas cacher une situation de crise et bien communiquer auprès de ses équipes, aussi bien les raisons de cet échec que les mesures prises pour en sortir. On apprend aussi de ses erreurs.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Design Patterns for Serverless Systems

Design Patterns for Serverless Systems | Devops for Growth | Scoop.it
Key Takeaways

We can define different categories of design patterns, including OOP design patterns, organizational patterns, and so on.
A number of design patterns are specifically suited to the serverless paradigm.
The Pipes and Filters design pattern can be used to decouple a serveless system into simple functional units interconnected in a chain.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

7 Software Development Models: How to Choose the Right One? - DZone Web Dev

7 Software Development Models: How to Choose the Right One? - DZone Web Dev | Devops for Growth | Scoop.it
Let's define the software development life cycle, make an overview of the 7 most used models, and find out their differences and benefits in projec
Mickael Ruau's insight:

 

The DevOps model has its unique principles that promote automation and team collaboration. Therefore, the primary focus of the model is the enhancement of collaboration between teams that are driven by sequential feedback. The DevOps model resembles the Agile methodology, but differs due to the collaboration focus between technical team members and managers, while Agile focuses on client involvement.

What does DevOps carry out?

  • Continuous Integration and Delivery
  • Microservices
  • Infrastructure as Code
  • Monitoring and Logging
  • Communication and Collaboration
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Is SOLID Still Relevant in Modern Software Architecture?

Is SOLID Still Relevant in Modern Software Architecture? | Devops for Growth | Scoop.it
Daniel Orner published a recent article arguing that SOLID principles are still the foundation for modern software architecture. According to Daniel, while the practice of software development has changed in the past 20 years, SOLID principles are still the basis of good design. The author explains how they also apply to functional programming and microservices architecture, with examples.

SOLID is a mnemonic and acronym for five software design principles enumerated in 2000 by Robert C. Martin. According to the article’s author, these "SOLID principles are a time-tested rubric for creating good software" and can be adapted to modern software engineering practices.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Plan de contingence : prévoir les risques de turbulences - CRHA

Plan de contingence : prévoir les risques de turbulences - CRHA | Devops for Growth | Scoop.it


Cet exercice de réflexion, de mise en situation et de préparation demande d’être mené en amont et non pas au cœur d’un crise. Évidemment, il est impossible de prévoir chacune des sources de crise ainsi que les situations possibles en découlant. Cependant, un plan de contingence permet d’avoir une longueur d’avance. Plus précisément, cela amène une rapidité d’action dès le départ ainsi qu’un état de contrôle chez les dirigeants qui se traduit par un sentiment de confiance auprès des équipes.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Agile Christmas ? C'est reparti !

Agile Christmas ? C'est reparti ! | Devops for Growth | Scoop.it
Agile Christmas est LE calendrier de l'avent agile ! Découvrez chaque jour un cadeau agile fait à la communauté. Retour sur l'édition 2020.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Tout savoir sur le Nouveau Design Sprint! 5, 4 ou 2 jours ? DifferentFactory

Tout savoir sur le Nouveau Design Sprint! 5, 4 ou 2 jours ? DifferentFactory | Devops for Growth | Scoop.it
Quel est le nouveau Design Sprint 3.0 ? Choisir entre Design Sprint en 5 jours, le Sprint 3.0 en 4 J, ou le Mini Sprint 2 J ? Do & Don't pour Réussir
No comment yet.
Rescooped by Mickael Ruau from LEAP EntrepreneurshiԀPassion - lasting enterprise action practices
Scoop.it!

TBTB

TBTB | Devops for Growth | Scoop.it
TOOLBOXTOOLBOX

A curated list of the best business, design, and organisational change toolboxes built by some of the most influential companies, institutions and thinkers.

SUBMIT A TOOLBOX TEAM

Via Oliver Durrer swissleap.com
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Sober Look at Microservices - DZone Microservices

Sober Look at Microservices - DZone Microservices | Devops for Growth | Scoop.it
Curious observation: this is not always possible to do a transition from single to multiple deployable artifacts, or “break the monolith”. Not necessarily because “monolith” is poorly designed or implemented (this also happens, but it’s another story). The actual reason is that internal architecture might be not service-based. For example, Hexagonal Architecture is hard or impossible to refactor into service-based architecture. Another possible cause — for business reasons, it might be impossible to split domains into services. After all, applications are created to solve business problems, not vice versa.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

What Are Microservices and The Event Aggregator Pattern? - DZone Cloud

What Are Microservices and The Event Aggregator Pattern? - DZone Cloud | Devops for Growth | Scoop.it
Learn about the Event Aggregator pattern for organizing event communication in a microservices architecture with an example.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Situational Leadership® Helps you Create a Safe Working Environment

Situational Leadership® Helps you Create a Safe Working Environment | Devops for Growth | Scoop.it
How do you create a safe working environment? The "secret" lies within the the four competencies of The Situational Leadership® Model!
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

In Defense of Clean Code - DZone Web Dev

In Defense of Clean Code - DZone Web Dev | Devops for Growth | Scoop.it
100+ pieces of timeless advice from Uncle Bob. Clean Code by Robert C. Martin is the most recommended programming book of all time. There’s a good reason why.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Pourriez-vous auditer mon projet svp ? –

Pourriez-vous auditer mon projet svp ? – | Devops for Growth | Scoop.it


Dans mon rôle de PM, si les auditeurs me demandent mes attentes de l’audit, je mets en évidence 2 points majeurs :

Obtenir des recommandations de valeur pour améliorer le projet
Équité envers les membres de l’équipe.

L’étape suivante est l’achèvement de l’audit et de la production des recommandations. Inévitablement, il y en aura certaines avec lesquelles vous êtes d’accord ou que vous pouvez comprendre. Il y aura d’autres qui seront plus difficiles à accepter. Dans tous les cas, il est absolument critique de rester positif et ouvert. Passer en mode défensif n’aiderait en rien. De plus, gardez à l’esprit que les recommandations des consultants et auditeurs sont une chose; le choix des recommandations sur lesquelles la direction décidera d’agir est une autre affaire (bien plus critique pour vous et votre projet).

Dès que vous comprenez quelles actions correctives ou d’amélioration sont retenues, partagez celles-ci avec l’équipe projet de manière positive. Il est fréquent que le rapport complet des auditeurs ne soit pas diffusé. Seuls les points principaux des rapports sont présentés. Ceux qui engagent l’équipe sur des actions productives.

En conclusion, je suggère que, si votre projet n’est pas encore audité, vous considériez quels domaines pourraient être améliorés par un conseil externe et sollicitiez un audit sur ceux-ci : Demandez de l’aide avant que quelqu’un au-dessus de vous ne décide que vous avez besoin d’être aidés.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Scrum Guide 2020 - moins prescriptif (ep 1)

Scrum Guide 2020 - moins prescriptif (ep 1) | Devops for Growth | Scoop.it

Comme vous le savez, Jeff Sutherland et Ken Schwaber nous ont proposé une nouvelle version du Scrum Guide en novembre 2020. Mais que propose...

No comment yet.