Devops for Growth
112.1K views | +9 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 tag: 'Leadership'. Clear
Scooped by Mickael Ruau
October 14, 2021 8:06 AM
Scoop.it!

The Three Symptoms of Toxic Leadership and How to Get out of It

The Three Symptoms of Toxic Leadership and How to Get out of It | Devops for Growth | Scoop.it
None of us are born toxic leaders, but anyone can easily become one. In the past several years, workplaces have started to feel the effects of “toxic leadership.” Now is the time to educate everyone on the importance of speaking right, doing right, treating each other right in the workplace, and above all, being a non-toxic leader.
No comment yet.
Scooped by Mickael Ruau
July 26, 2021 1:52 AM
Scoop.it!

J’ai lu ça : influence et manipulation de Robert...

J’ai lu ça : influence et manipulation de Robert... | Devops for Growth | Scoop.it
J’ai lu ça : influence et manipulation de Robert Cialdini...
No comment yet.
Scooped by Mickael Ruau
July 19, 2021 1:06 AM
Scoop.it!

Want to Develop Your Team Superpowers?

Want to Develop Your Team Superpowers? | Devops for Growth | Scoop.it

Stop Neglecting the Basics: Take the Two Pills

Want to learn how to become more effective as a team, both in terms of joint efficiency and creativity?

Try the red pill (psychological safety) and the blue pill (common ground) as a team. Even more, make sure that every team member is accountable for nurturing these two requirements.

Both pills are needed to solve complex problems together in a time of Volatility, Uncertainty, Complexity and Ambiguity (VUCA model). Team innovation starts by building and nurturing a solid team alignment and a safe climate. Guess where? During these team meetings that are so criticized, and rightly so.


high_impact_tools_for_teams_psychological_safety_pill
The red pill increases your team ability to achieve

A large internal study conducted by Google highlighted that psychological safety is the main enabler of high-performance teamwork (Duhigg, 2016). Team members engage in a productive dialogue that fosters the learning behaviors required to understand the environment, the clients and solve problems together.

high_impact_tools_for_teams_common_ground_pill

The blue pill maximizes your team effort towards the mission

Team members remain constantly aligned on what needs to be achieved and how. Execution of tasks is more efficient and personal contributions integrate more successfully. Teams with higher common ground perform tasks 4 to 12 times faster than teams with no or insufficient common ground.(*)

No comment yet.
Scooped by Mickael Ruau
July 13, 2021 7:31 AM
Scoop.it!

Guts, Part Three: Having Backbone – Disagreeing and Committing | AWS Cloud Enterprise Strategy Blog

Guts, Part Three: Having Backbone – Disagreeing and Committing | AWS Cloud Enterprise Strategy Blog | Devops for Growth | Scoop.it

I’ve written about the guts to make a decision when the time is right, and the guts to demand that your vendors treat you like a valued customer. In this post I’d like to discuss taking a principled stand within the organization.

Mickael Ruau's insight:

 

At Amazon, you may know, we have a set of leadership principles that we take very seriously. I’m a big fan of the one that says “Have Backbone: Disagree and Commit.” It means that if you disagree with something, it’s your responsibility to argue. It’s meant to be applied even if it’s your boss’s idea. Disagreeing doesn’t mean acting like a jerk. It means making a cogent case, using data where possible to support your arguments. The second part of the principle, “Commit,” is important as well. At some point, you may have to give in, or compromise. If you do, then you’re committed to the decision. You can’t be passive-aggressive or later say “I told you so.” You own the final decision, even if it’s not what you originally wanted.

No comment yet.
Scooped by Mickael Ruau
June 5, 2021 11:14 AM
Scoop.it!

#49 Laisser parler son cœur - Un pas dans l'inconnu

#49 Laisser parler son cœur - Un pas dans l'inconnu | Devops for Growth | Scoop.it
les leçons entrepreneuriales et managériales de Barack Obama (partie 2)
No comment yet.
Scooped by Mickael Ruau
January 29, 2021 4:05 AM
Scoop.it!

Technical Leadership: Beyond Solving Problems with Pat Kua

Technical Leadership: Beyond Solving Problems with Pat Kua | Devops for Growth | Scoop.it
Engineering leadership coach Pat Kua joins me to discuss the the skills engineers need to be leaders beyond problem solving.
No comment yet.
Scooped by Mickael Ruau
August 7, 2020 11:15 AM
Scoop.it!

Retrospectives on Peopleware - IEEE Conference Publication

Retrospectives on Peopleware - IEEE Conference Publication | Devops for Growth | Scoop.it

Since its publication twenty years ago, "Peopleware Productive Projects and Teams" (Dorset House, 1987), by Tom DeMarco and Tim Lister, has enlightened software professionals and non-professionals alike. Peopleware introduced among other topics - "team gel", design patterns, the "Furniture Police" - to the software engineering community and suggested that "sociology matters more than technology or even money." This unique session with the pioneers of our profession is an opportunity to learn, reflect, and share experiences -- looking forward to the future. This compendium consists of brief bios and first person retrospectives on "Peopleware".
No comment yet.
Scooped by Mickael Ruau
August 7, 2020 11:13 AM
Scoop.it!

Note de lecture : Peopleware: Productive projects and teams (2nd edition), par Tom DeMarco & Timothy Lister –

Note de lecture : Peopleware: Productive projects and teams (2nd edition), par Tom DeMarco & Timothy Lister – | Devops for Growth | Scoop.it
Ce livre concerne le management, ou plutôt la gestion de projets mais dans le sens où la gestion d’un projet est d’avantage une question de faciliter la synergie de groupe que de méthodologies formelles. Qu’ont donc en commun les projets ayant abouti à des succès remarqués ? Une gestion du projet et des ressources particulièrement méticuleuse ? Parfois. La formation d’un groupe d’experts hautement qualifiés ? Pas toujours. L’utilisation d’un processus élaboré distribuant tâches rôles et responsabilités de façon rigoureuse et détaillée ? Rarement. Peopleware expose les traits communs de ces projets : la formation d’une équipe soudée, volontaire, complémentaire. Mais aussi la fierté d’appartenir à un groupe d’excellence, d’évoluer dans un environnement où la contribution individuelle et collective est reconnue.
Mickael Ruau's insight:

Ce texte n’est pas une théorie sur les relations humaines, mais une suite d’essais adressant des aspects particuliers du sujet et s’appuyant sur des exemples concrets issus de la longue expérience de consulting des deux auteurs. Même si ils n’en ont pas la forme, ces essais sont pratiquement des patterns, ce qui en fait un ouvrage en avance sur son temps, car publié en 1987 pour la première édition. D’avant-garde, ce livre l’est encore d’avantage car il pose tout les fondements des méthodes agiles tels que l’extreme programming ou le lean development, par exemple.

 

Le livre est découpé en 6 parties totalisant 34 chapitres (ou essais). Le total n’étant que de 226 pages vous comprendrez que chaque chapitre n’excède pas quelques pages, ce qui renforce encore leur analogie avec les patterns. Les thèmes abordés au long de ces 6 parties sont : gestion des ressources humaines, l’environnement du bureau, le choix des bonnes personnes, la croissance des équipes productives, l’épanouissement dans le travail et quelques sujets connexes regroupés en dernière partie.

No comment yet.
Scooped by Mickael Ruau
August 7, 2020 11:09 AM
Scoop.it!

Peopleware - Wikipedia

Peopleware

Peopleware is a term used to refer to one of the three core aspects of computer technology, the other two being hardware and software. Peopleware can refer to anything that has to do with the role of people in the development or use of computer software and hardware systems, including such issues as developer productivity, teamwork, group dynamics, the psychology of programming, project management, organizational factors, human interface design, and human-machine-interaction.

Mickael Ruau's insight:

Overview

The concept of peopleware in the software community covers a variety of aspects:[2]

  • Development of productive persons
  • Organizational culture
  • Organizational learning
  • Development of productive teams, and
  • Modeling of human competencies.

History

The neologism, first used by Peter G. Neumann in 1977[3] and independently coined by Meilir Page-Jones in 1980,[4] was popularized in the 1987 book Peopleware: Productive Projects and Teams by Tom DeMarco and Timothy Lister.[5]

The term Peopleware also became the title and subject matter of a long-running series of columns by Larry Constantine in Software Development magazine, later compiled in book form.[6]

No comment yet.
Scooped by Mickael Ruau
August 1, 2020 8:23 AM
Scoop.it!

Leading & Coaching | Mark Smith | TEDxMSVU

Mark says sport has taught him how to be a leader and coach. You can make a significant difference in the world when you find the primary drivers that allow you to coach and lead.

Mark is the Director of Coaching for Sport Nova Scotia and the Canadian Sport Center Atlantic. In 2015, he was the Chef de Mission of Team Nova Scotia at the Canada Winter Games.

As an athlete, Mark won 3 Pan American Games gold medals, 3 World Championships, 1 National Championship, 19 Provincial Championships, 3 State Championships, plus numerous individual awards.

As an international level coach, he has won two Pan Am gold medals and has had multiple podium finishes at the World Championships. In July of 2015 he led Canada’s women’s national team to a Pan American Games gold medal in Toronto.

Mark is the winningest coach in national teams history with 280 over international victories.

Mark is a member of the Nova Scotia Sport Heritage Hall of Fame, the Canadian Softball Hall of Fame, and the International Softball Congress Hall of Fame. He is married to former Olympian Ann Dodge and has a daughter Jasmine. Mark and his family reside in Falmouth, Nova Scotia.

This talk was given at a TEDx event using the TED conference format but independently organized by a local community. Learn more at http://ted.com/tedx
No comment yet.
Scooped by Mickael Ruau
July 31, 2020 2:37 AM
Scoop.it!

Why Facts Don’t Change Our Minds

Why Facts Don’t Change Our Minds | Devops for Growth | Scoop.it

Facts Don't Change Our Minds. Friendship Does.

Convincing someone to change their mind is really the process of convincing them to change their tribe. If they abandon their beliefs, they run the risk of losing social ties. You can’t expect someone to change their mind if you take away their community too. You have to give them somewhere to go. Nobody wants their worldview torn apart if loneliness is the outcome.

The way to change people’s minds is to become friends with them, to integrate them into your tribe, to bring them into your circle. Now, they can change their beliefs without the risk of being abandoned socially.

The British philosopher Alain de Botton suggests that we simply share meals with those who disagree with us
Mickael Ruau's insight:

Let's call this phenomenon Clear's Law of Recurrence: The number of people who believe an idea is directly proportional to the number of times it has been repeated during the last year—even if the idea is false.

Each time you attack a bad idea, you are feeding the very monster you are trying to destroy. As one Twitter employee wrote, “Every time you retweet or quote tweet someone you’re angry with, it helps them. It disseminates their BS. Hell for the ideas you deplore is silence. Have the discipline to give it to them.”

Your time is better spent championing good ideas than tearing down bad ones. Don't waste time explaining why bad ideas are bad. You are simply fanning the flame of ignorance and stupidity.

The best thing that can happen to a bad idea is that it is forgotten. The best thing that can happen to a good idea is that it is shared. It makes me think of Tyler Cowen's quote, “Spend as little time as possible talking about how other people are wrong.”

Feed the good ideas and let bad ideas die of starvation.

No comment yet.
Scooped by Mickael Ruau
July 23, 2020 5:04 AM
Scoop.it!

The Golden Circle is, in fact, a spiral | by Justo Guerin | UX Collective

The Golden Circle is, in fact, a spiral | by Justo Guerin | UX Collective | Devops for Growth | Scoop.it
So everyone knows the Golden Circle by Simon Sinek, right? What if I told you that it isn’t a circle but a spiral. Yes, you’re looking at it from above. Since I first watched his Ted Talk a few years…
No comment yet.
Scooped by Mickael Ruau
July 22, 2020 5:12 AM
Scoop.it!

Leadership et Dynamique de groupe dans une transformation (agile, mais pas que)

Leadership et Dynamique de groupe dans une transformation (agile, mais pas que) | Devops for Growth | Scoop.it
Disclamer Si vous n'avez pas vu ma conférence sur la structuration du temps et la dynamique de groupe en analyse transactionnelle à l'échelle à Agile France et à la Xebicon (ou encore en meet-up) cette année, vous risquez d'être éventuellement perdus. J'ai déposé le support de cette présentation dans un précédent article. Cela vous permettra…
No comment yet.
Scooped by Mickael Ruau
September 28, 2021 8:16 AM
Scoop.it!

Five Leadership Lessons I Learned - DZone DevOps

Five Leadership Lessons I Learned - DZone DevOps | Devops for Growth | Scoop.it
After a year spent interviewing some of the biggest names in tech, here are the 5 best leadership lessons I've learned as host of the Dev Interrupted podcast.
No comment yet.
Scooped by Mickael Ruau
July 23, 2021 4:57 AM
Scoop.it!

Quatre styles de prise de décision et quand les utiliser — Wiki Agile du @GroupeCESI

Quatre styles de prise de décision et quand les utiliser — Wiki Agile du @GroupeCESI | Devops for Growth | Scoop.it
No comment yet.
Scooped by Mickael Ruau
July 16, 2021 1:03 AM
Scoop.it!

Celebrate Failures as Much as The Successes

Celebrate Failures as Much as The Successes | Devops for Growth | Scoop.it
To build a portfolio of innovation projects you can't just reward successful projects. Its just as important to celebrate the failures as much as the wins.
No comment yet.
Scooped by Mickael Ruau
June 10, 2021 3:28 AM
Scoop.it!

Motivation And Modern Leadership; Surprising Agile Lessons From 1967

Motivation And Modern Leadership; Surprising Agile Lessons From 1967 | Devops for Growth | Scoop.it
Scrum Inc.’s Robert Wood recently received of an article from 1967. He found forward-thinking Agile concepts around teams, motivation, and modern leadership.
No comment yet.
Scooped by Mickael Ruau
March 15, 2021 10:21 AM
Scoop.it!

Agile Leadership Matrix - DZone Agile

Agile Leadership Matrix - DZone Agile | Devops for Growth | Scoop.it
As transformation/change agents, we are aware that any organization's transformation takes time and requires huge patience and resilience on the part of ...
No comment yet.
Scooped by Mickael Ruau
October 27, 2020 1:30 AM
Scoop.it!

Open Leadership Training Series

This Open Leadership Training Series teaches you best practices in “working open” – a way of working where:

everyone is invited to collaborate on something amazing,
and any new product or knowledge is shared widely and freely.

This is for anyone starting up or leading open projects– project leads, collaborators, or small groups of co-leaders responsible for project success and growth.

Mickael Ruau's insight:

README
1. Intro to Open Leadership
2. Opening Your Project
3. Building Communities
4. Get Your Project Online
5. GitHub for Collaboration
6. Open Communications
7. Running Awesome Events
8. Open Project Maintenance
9. Open Leadership Outro
Glossary

See the Code on GitHub
Open Leadership Training Series
Best Practices Working Open

No comment yet.
Scooped by Mickael Ruau
August 7, 2020 11:14 AM
Scoop.it!

Peopleware: Productive Projects and Teams Book Review | Pluralsight

Peopleware: Productive Projects and Teams Book Review | Pluralsight | Devops for Growth | Scoop.it
The modern workplace disregards the fact that engineers feel best creating quality work, which often requires the right space and opportunities to think about the solution they're working on.

Many companies push for faster development cycles, impossibly tight deadlines and a management approach that treats people like they're easily replaceable parts. It's not an easy task to reverse this reality for your team, but this book is the blueprint you need.

Peopleware is divided into six parts:

Managing the Human Resource
The Office Environment
The Right People
Growing Productive Teams
Fertile Soil
It's Supposed to Be Fun to Work Here
Mickael Ruau's insight:

The Most Important Things You'll Learn from Peopleware: Productive Products and Teams

  • Stop looking at team problems from a technological standpoint. A sociological approach is necessary for knowledge workers.
  • Create a working environment capable of fostering concentration. Open floor plans and cubicle farms make it next to impossible for software engineers to achieve "flow," which is a state of focus that permits them to think. Give them the right space and privacy to create quality work. This process is not one size fits all. Watch how your team works to find an ideal configuration.
  • You can't fix every single problem that's impacting your team's productivity, but you can tackle issues one at a time with an eye for the long-term.
  • More hours worked does not equal a greater quantity or quality of work. Avoid overtime as much as possible, outside of crunch situations. Accept that less productive time, termed “under time”, will happen throughout the project.
  • Your hiring process should include a development portfolio and input from current team members.
  • Strive to achieve goal alignment between team members, as this helps you create a working unit capable of more than the sum of its parts.
  • Your team members know there's more to life than work, and you face high turnover if you don't give them the balance they need.
  • A culture of quality is necessary to keep your team happy with the work they do. Realistic project timelines and pushing back against moving upper management goalposts is an essential part of creating this environment.

If you only remember one line from Peopleware

“The manager’s function is not to make people work, but to make it possible for people to work.”

No comment yet.
Scooped by Mickael Ruau
August 7, 2020 11:10 AM
Scoop.it!

Peopleware

Peopleware | Devops for Growth | Scoop.it
.

Je vais faire court : si vous êtes ou voulez devenir manager IT, quel que soit le domaine, c’est un incontournable. Dedans une grosse dose de bon sens délivrée en courts chapitres de quelques pages, un vrai plaisir à lire. Ça parle RH, vie de bureaux, relations interpersonnelles, construction d’équipe, mise en place d’organisations inscrites dans des cercles vertueux…
Mickael Ruau's insight:

Morceaux choisis :

  • Il faut arrêter de croire que nos métiers sont centrés autour des technologies. Les chercheurs qui font les découvertes fondamentales de nos domaines sont ceux qui travaillent effectivement sur les technologies. Nous, nous ne sommes que les utilisateurs des technologies qu’eux développent. Et à ce titre nos métiers sont donc plus centrés autour des relations humaines qu’autre chose. (p5 )
  • Les statistiques sur la lecture sont particulièrement décourageantes. Le développeur moyen ne possède aucun livre sur son domaine d’expertise, et n’en a même jamais lu un. (p11, Vous en êtes où du DWH Toolkit? ;))
  • La qualité, bien au-delà d’un simple prérequis de l’utilisateur, est une mesure de haute productivité. (p21, cf le Lean)
  • La fonction d’un manager n’est pas de faire que les gens travaillent, mais de faire qu’il soit possible qu’ils travaillent. (p34, on ne doit pas motiver, mais plutôt limiter la démotivation…)
  • Loi de Gilb : tout ce qui doit être quantifié peut être mesuré d’une manière qui est meilleure que de ne pas le mesurer du tout. (p58, on parle qualité, satisfaction… à prendre en compte dans les ROI et décisions stratégiques en plus du numéraire)
  • Par exemple : le « E-Factor » = Nb heure de travail ininterrompu / Nb heure de présence physique. (p64, à utiliser pour vérifier qu’un environnement n’est pas trop toxique au travail)
  • L’effet pervers d’un taux de turnover élevé (cycle des démissions/recrutements) et qu’il s’auto-entretient. Les collaborateurs partent vite donc il n’y a pas d’intérêt pour l’entreprise à investir sur eux. Mais s’il n’y a pas d’investissement, les collaborateurs démissionnent rapidement. (p120)
  • Le but de la constitution d’une équipe n’est pas d’atteindre un objectif, mais de définir et travailler vers un objectif commun. (p136)
  • La short-liste des techniques pour détruire une équipe : management défensif, bureaucratie, séparation physique, fragmentation du temps de travail sur des projets multiples, réduction de la qualité du produit, fausses deadlines, micro-management. (p144, avec du détail sur chacun des points)
  • La liste étendue des techniques pour détruire une équipe : primes annuelles sur objectifs, management par objectif, récompenses individuelles, et plus globalement tout ce qui tourne autour de la mesure et la gratification des performances. (p157, toujours avec le détail sur place)
  • A l’inverse, la liste des activités qui contribuent à l’équipe: faire de la qualité un culte, permettre à tous de comprendre le pourquoi de chaque décision, construire un sens de l’élitisme, encourager l’hétérogénéité, préserver et protéger les équipes qui gagnent, apporter une vision stratégique mais laisser le champ libre au niveau tactique (p168, toujours avec le détail sur place)
  • Les bonnes méthodes pour atteindre une convergence sur les pratiques sont : les formations, les outils d’automatisation, les revues par ses pairs. (p180)
  • Le péché ultime du management c’est de faire perdre son temps à quelqu’un. (p193)
  • Le changement ne peut se produire que si les collaborateurs se sentent en sécurité. (p208)
  • Une organisation peut apprendre de 2 façons : elle instille des nouvelles compétences et approches à ses membres, ou elle se redessine pour opérer d’une manière différente. (p212)
  • Dans tous les cas, la maturation d’une organisation est limitée par sa capacité à conserver ses membres. (p212)
No comment yet.
Scooped by Mickael Ruau
August 5, 2020 6:06 AM
Scoop.it!

Fiedler contingency model - Wikipedia

Fiedler contingency model

The contingency model by business and management psychologist Fred Fiedler is a contingency theory concerned with the effectiveness of a leader in an organization. The most common situational theory was developed by Fred Fiedler. Fiedler believed that an individual's leadership style is the result of their experiences throughout the lifespan, and therefore extremely difficult to change.

No comment yet.
Scooped by Mickael Ruau
August 1, 2020 7:59 AM
Scoop.it!

Conversations That Inspire: Coaching Learning, Leadership and Change

Coaching can inspire and motivate people to learn, change, and be effective leaders, among other roles in life. Although most attempts are “coaching for compliance” (coaching someone to your wishes or expectations), decades of behavioral and neuroscience research show us that “coaching with compassion” (coaching someone to their dreams and desires) is more effective.
No comment yet.
Scooped by Mickael Ruau
July 29, 2020 11:31 AM
Scoop.it!

Heroes of Leadership (BetaCodex14)

The BetaCodex Network´s 14th white paper. Published February 2013. Revised and with three additional heroes added, in January 2015.
No comment yet.
Scooped by Mickael Ruau
July 22, 2020 5:40 AM
Scoop.it!

Reading the map – Keep to the North! –

Reading the map – Keep to the North! – | Devops for Growth | Scoop.it
Over the past few weeks, I introduced you to a sense-making model developed by Dave Snowden. His Cynefin framework can serve as a map to give you some orientation in challenging situations of decis…
No comment yet.