Devops for Growth
112.1K 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 tag: 'Flow'. Clear
Scooped by Mickael Ruau
July 15, 2020 1:19 AM
Scoop.it!

Kanban Guides

Kanban Guides | Devops for Growth | Scoop.it
Kanban the Flow Strategy™ provides the basic structure for Kanban, which the reader can augment using models such as Evidence Based Management, Cynefin Sense-Making, Theory of Constraints, and scaling/descaling.
We have our quirks, and we consider some things as optional that maybe you thought were mandatory.

Download the Guide for Kanban – the Flow Strategy™ here.
No comment yet.
Scooped by Mickael Ruau
June 12, 2020 5:54 AM
Scoop.it!

Quarterly Cycle - Extreme Programming Practice

Amongst the twelve primary practices of XP comes Quarterly Cycle. Quarterly Cycle along with the other practices helps in assuring a real flow for …
No comment yet.
Scooped by Mickael Ruau
April 30, 2020 2:44 AM
Scoop.it!

No Meetings Allowed: It’s ‘Thinking Thursday’

No Meetings Allowed: It’s ‘Thinking Thursday’ | Devops for Growth | Scoop.it
Edmunds.com puts a weekly moratorium on meetings and reserves Thursdays for reflection and creativity.
No comment yet.
Scooped by Mickael Ruau
April 20, 2020 12:42 PM
Scoop.it!

Path to Productivity: No Meeting Thursday | Jim Plush: Blog

Path to Productivity: No Meeting Thursday | Jim Plush: Blog | Devops for Growth | Scoop.it

More than half the engineers I interview cite “too many meetings” and “not feeling productive” as one of the key drivers as to why they’re looking to leave their current company.

No comment yet.
Scooped by Mickael Ruau
March 4, 2020 2:22 AM
Scoop.it!

Comment gérer les interruptions des équipes de développeurs ?

Comment gérer les interruptions des équipes de développeurs ? | Devops for Growth | Scoop.it
Il est très fréquent que les équipes de développement soient très souvent interrompues dans leur travail : un chef de projet qui a une idée d’ajout dans le logiciel, une personne de l’équipe commerciale qui a une question, un client qui passe un coup de téléphone direct à un développeur qu’il connait…
Mickael Ruau's insight:
Le DRIS (Développeur qui Réagit aux Interruptions de la Semaine)

Voici un extrait (largement édité) de notre wiki interne qui décrit non seulement les rôles et responsabilités du DRIS, mais aussi comment interagir avec lui : ce n’est pas une recette miracle, cela demande de la discipline de toute part (rediriger vers les DRIS lorsqu’on ne l’est pas, bien se préparer avant de venir voir le DRIS…).

L’idée principale est d’avoir un point d’entrée unique par équipe pour toutes les interruptions externes. Ce n’est pas une idée totalement neuve, cela fait maintenant 10 ans que je l’utilise sous diverses formes dans toutes les entreprises par lesquelles je suis passé et qui survivent à mon départ. Mes anciens collègues qui ont eux aussi changé d’entreprise ont transposé cette idée partout où ils sont passés.

Comme son nom l’indique, le DRIS :

  • est un Développeur
  • c’est lui qui Réagit
  • à toutes les Interruptions
  • le rôle est tournant et change chaque Semaine

Rôle(s) du DRIS

Le DRIS répond aux interruptions pendant sa semaine de responsabilité. Le but est de n’avoir qu’un seul point d’entrée dans l’équipe pour minimiser les interruptions.

Ses rôles et responsabilités sont les suivants :

  • gérer les urgences de production (sécurité, bugs de production, disponibilité et maintien de l’environnement de production, etc.)
  • être proactif sur la production
  • s’occuper des mises en production
  • répondre aux interruptions (questions), préserver le flow de son équipe
  • transmettre sa façon de faire

Le DRIS met tout en oeuvre pour accomplir sa mission dans le but de préserver l’équipe. Cependant, avec ce rôle, il a également le pouvoir d’interrompre toute ou une partie de l’équipe en cas de problème insoluble ou d’urgence de production. C’est un pouvoir qu’il doit utiliser avec mesure et discernement (puisque vous le savez, un grand pouvoir implique une grande responsabilité).

No comment yet.
Rescooped by Mickael Ruau from Getting Things Done
February 5, 2020 2:34 AM
Scoop.it!

Cognitive Switching Is Killing Your Productivity

Cognitive Switching Is Killing Your Productivity | Devops for Growth | Scoop.it
Why grouping your next actions by contexts is important to work effectively.
Via Emeric Nectoux
No comment yet.
Scooped by Mickael Ruau
November 4, 2019 3:04 AM
Scoop.it!

Communication asynchrone : la vraie raison pour laquelle les travailleurs sont plus productifs, qu'ils soient télétravailleurs ou non, selon un rapport

Communication asynchrone : la vraie raison pour laquelle les travailleurs sont plus productifs, qu'ils soient télétravailleurs ou non, selon un rapport | Devops for Growth | Scoop.it

Que votre équipe ait adopté le travail sur site pour profiter de certains avantages comme une forte intégration physique des salariés au groupe, ou que vous ayez opté pour le télétravail pour plus de flexibilité des ressources humaines ou pour éviter les distractions du bureau – nécessaire pour les tâches comme l’écriture de code –, un facteur important de la productivité des équipes serait la forme de communication adoptée.

No comment yet.
Scooped by Mickael Ruau
September 13, 2019 1:46 AM
Scoop.it!

The Conceptualization of Team Flow: The Journal of Psychology: Vol 152, No 6

The Conceptualization of Team Flow: The Journal of Psychology: Vol 152, No 6 | Devops for Growth | Scoop.it
ABSTRACTDespite the noted potential for team flow to enhance a team's effectiveness, productivity, performance, and capabilities, studies on the construct in the workplace context are scarce. Mos
No comment yet.
Scooped by Mickael Ruau
September 9, 2019 2:54 AM
Scoop.it!

Getting Developers into the Team Flow State | Compuware Topaz

Getting Developers into the Team Flow State | Compuware Topaz | Devops for Growth | Scoop.it
Learn how your teams can achieve team flow, a state of ultimate concentration and innovation, to reach maximum creativity and productivity.
No comment yet.
Scooped by Mickael Ruau
September 3, 2019 9:41 AM
Scoop.it!

La Voix du Coach - Samuel Retière

La Voix du Coach - Samuel Retière | Devops for Growth | Scoop.it
Dans la série "la Voix du Coach", InfoQ FR échange avec Samuel Retière : "Quand on m'a proposé de parler dans la voix du coach, je me suis demandé ce que j'allais bien pouvoir apporter de plus que les autres coachs passés avant moi. Il paraît que je suis différent des autres car interne (Société Générale) et que je peux donc avoir un regard divergent".
No comment yet.
Scooped by Mickael Ruau
May 17, 2019 3:52 AM
Scoop.it!

Actionable Agile Metrics for Predictability by Daniel S. Vacanti, Re-read Saturday Week 3:  The Basic Metrics of Flow

Actionable Agile Metrics for Predictability by Daniel S. Vacanti, Re-read Saturday Week 3:  The Basic Metrics of Flow | Devops for Growth | Scoop.it

Today we tackle Chapter 2 of Daniel S. Vacanti’s Actionable Agile Metrics for Predictability. Chapter 2 is titled The Basic Metrics of Flow. The concept of flow is critical to predictability. Buy your copy today and read along!

The basic metrics of flow (noted in Chapter 1) are:

Work in progress
Cycle time
Throughput

No comment yet.
Scooped by Mickael Ruau
April 30, 2019 11:11 AM
Scoop.it!

FLIGBY Skills Tool Box - Conflict Management

FLIGBY Skills Tool Box - Conflict Management | Devops for Growth | Scoop.it
Prof. Mihaly Csikszentmihalyi, author of the global best-seller book Good Business, conducted deep interviews with several leaders of internationally successful, and sustainable organizations. He found that these successfully created Flow-promoting Organizations and implemented the Flow-Leadership style. Together with him, our team at Aleas Sims/FLIGBY has identified a core of  29 management and leadership skills.   In cooperation with…
No comment yet.
Scooped by Mickael Ruau
April 25, 2019 10:37 AM
Scoop.it!

A Manifesto for Creating Extraordinary Teams

A Manifesto for Creating Extraordinary Teams | Devops for Growth | Scoop.it
A New Science is showing us how staying in-the-flow may be the most important part of building extraordinary teams.
Mickael Ruau's insight:

While you may not be fighting fires, and your stress may be considerably less (or not!), you are trying to build an exceptional team and there's a lot the GSD can teach you about how to achieve flow with your team.

 
  1. Lead by example. Demonstrate your commitment to service through servant leadership. In the words of the Georgia Smoke Diver Chief Elder, be a "leader of equals." Think about this one. Are you there for your team? Are you constantly aware of the messages your actions are delivering? Like it or not you are the role model for the culture you're creating.
 
  1. Communicate your vision and a sense of purpose. Every morning the GSD reads its mission out loud to all instructors and students. You might think that's a bit excessive, after all once you've heard it two or three times what's the point? Simple, we are most driven to achieve when our work is aligned with the need for purpose and meaning. You can never remind people enough of how important that purpose is; it's their compass setting for every decision they make.
  1. Establish and maintain an infrastructure that supports the work of the organization. Poor systems will pull an individual out of his or her flow state in a heartbeat. Provide your team with tools to get the job done and then let them figure out how to do it. Unfortunately, many leaders seem to think their job is the exact opposite; tell people exactly how to do their work and then let them figure out where to find the tools.
  1. Create trust with rituals and storytelling. Prior to all student drills GSD instructors tells a story of how the drill was developed as a result of someone losing his or her life in the line of duty. Yeah, heavy stuff! How do you inspire through story telling? If you're thinking, "but my company isn't involved in life and death scenarios." I'll let you in on something; knowledge workers spend more of their life working than any other single activity--including sleep. This is their life, so acknowledge it!
  1. Honor individual creativity. If a GSD instructor has an idea, he can immediately capture it and turn it into Operations and Plans. The GSD Board reviews and often implements it immediately. However, even if it's rejected, the leadership acknowledges the creativity by explaining why it cannot be implemented. What happens to ideas in your organization? Are people fearful of submitting new ideas because they simple expect them to be shot down? Or do new ideas have to run a gauntlet course to be heard?
 
  1. Use positive motivation. One of the GSD teams is called the Mo Squad. These are instructors whose sole responsibility is to motivate students. What would your work environment look like if you had people whose sole purpose it was to give encouragement to others?
  1. Learn what gives people joy and give them the opportunities to do it. Ask people what they love about their work. Then, listen. Most of us try to identify a person's weaknesses in an attempt to help in areas where he or she is weak. Try instead providing training that magnifies his or her strengths. People find flow in the tasks and activities where they are strongest.
No comment yet.
Scooped by Mickael Ruau
June 25, 2020 2:47 AM
Scoop.it!

Manage flow, not people!

Manage flow, not people! | Devops for Growth | Scoop.it
Flow is King. Agility is a side-effect.
No comment yet.
Scooped by Mickael Ruau
May 4, 2020 2:42 AM
Scoop.it!

The Advantages of "No Meeting" Days

The Advantages of "No Meeting" Days | Devops for Growth | Scoop.it
Sometimes meetings can get in the way of quality work. This is why trying, "no meeting" days can help boost productivity and attention levels in meetings.
No comment yet.
Scooped by Mickael Ruau
April 30, 2020 2:43 AM
Scoop.it!

“Flow Thursdays” – A Day of Liberation With No Standing Meetings - DZone Agile

“Flow Thursdays” – A Day of Liberation With No Standing Meetings - DZone Agile | Devops for Growth | Scoop.it
The number one blocker of productivity in the workplace is distractions, and standing meetings can easily be an unnecessary blocker for your team.
No comment yet.
Scooped by Mickael Ruau
March 11, 2020 3:15 AM
Scoop.it!

How to do a Retrospective using Flow Metrics - The Liberators

After having read Dan Vacanti’s book on Actionable Agile Metrics for Predictability I decided to put my learnings into practice and teamed up with a Scrum Master of a team that recently started…
No comment yet.
Scooped by Mickael Ruau
March 3, 2020 12:40 AM
Scoop.it!

Slicing heuristics - Techniques for improving value generation, speed…

Talk at LAST Conference 2019
Mickael Ruau's insight:

Local flow is “good”, but not enough

No comment yet.
Scooped by Mickael Ruau
November 22, 2019 2:35 AM
Scoop.it!

Successfully balancing technical debt and new features – staying in the “flow-zone” or how to get back in there | Agile Upgrade

Successfully balancing technical debt and new features – staying in the “flow-zone” or how to get back in there | Agile Upgrade | Devops for Growth | Scoop.it

I spent 4 days in Disentis, Switzerland discussing the latest developments in Agile, Continuous delivery, Kanban and Lean with Leif Sørensen (partner in a medium sized company focusing on continuous delivery called Praqma), Jan Hvid Sørensen (developer working on his own StartUp) and Klaus Bucka-Lassen (Senior Agile Executive Coach).

One of the problems we ended up spending time working on was how to effectively manage the need for long term optimization of the technical platforms and continuous delivery tools and processes against the more short term focus on features and end-user value.

No comment yet.
Scooped by Mickael Ruau
September 24, 2019 10:35 AM
Scoop.it!

Swarming in Scrum

Swarming in Scrum | Devops for Growth | Scoop.it
Swarming is the act of all development team members working on only one requirement at a time during the sprint. Although not a principle specific to scrum, it is such an effective way for teams to execute their sprint backlog that it warrants some more discussion. Again, one of the main benefits of scrum is …
Mickael Ruau's insight:

Recently, Microsoft conducted a study on the effects of multitasking. The results were that multitasking just doesn’t work. On average, it takes 15 minutes to get your brain back to the level it was at before you answered that phone call or email. Studies have also shown that an interruption as short as 4.4 seconds will triple the number or errors made on subsequent tasks requiring sequencing. Reducing multitasking in your development team will get you a sound head start on achieving the 30–40 percent increased product-to-market time.

 

Thrashing is when developers jump back and forth between projects, requirements, and tasks — context switching. Thrashing increases the time required to complete tasks by 30 percent. If you don’t have enough people to take on the workload as dedicated, swarming developers, you definitely don’t have time to thrash them.

No comment yet.
Scooped by Mickael Ruau
September 10, 2019 12:49 AM
Scoop.it!

Team flow: how to make productivity contagious

Team flow: how to make productivity contagious | Devops for Growth | Scoop.it

It’s generally agreed upon that the employees who are the happiest and the most productive have one thing in common: they frequently achieve flow. Flow is when we are so focused and involved in our work, we lose track of time. Sometimes we even forget to take breaks—that’s how “in the zone” we are. Flow is when we’re accessing our best ideas, seeing creative solutions to problems, and getting a lot done. We’re probably also enjoying ourselves!

No comment yet.
Scooped by Mickael Ruau
September 6, 2019 4:46 AM
Scoop.it!

Archive ouverte HAL - Le Team Flow : expérience optimale de coopération

Archive ouverte HAL - Le Team Flow : expérience optimale de coopération | Devops for Growth | Scoop.it
Le Team Flow : expérience optimale de coopération La théorie du flow décrit l'état mental de bien-être, promoteur de performance, qu'est susceptible de vivre un individu lorsqu'il est totalement immergé dans la réalisation d'une activité. Alors que les recherches sur ce construit sont nombreuses, les études s'attachant à analyser les formes sociales du flow sont quasi inexistantes. Cette communication vise à revenir sur les recherches que nous avons menées ces dernières années et qui constituent les premières études sur l'état de coopération optimale ou « team flow ». Réalisés dans le contexte des jeux vidéo coopératifs, ces travaux pionniers ont permis de mieux cerner la nature et le fonctionnement de ce concept méconnu aux larges perspectives applicatives (management, projets coopératifs, sports, e-sports…).
No comment yet.
Scooped by Mickael Ruau
May 1, 2019 6:24 AM
Scoop.it!

Flow Efficiency: A Kanban Metric Introduction

Flow Efficiency: A Kanban Metric Introduction | Devops for Growth | Scoop.it

Calculating your flow efficiency

Measuring flow efficiency can be done for a single request, but its much more likely that you want to measure the flow efficiency of your process over all requests completed in a specific time period. So, for the items completed in that time period, you’ll need the following information.

Overall Lead time (work + wait time)
Active Work time (do not include time spent waiting)

You then calculate the flow efficiency by dividing the active work time by the overall lead time. Multiply the result of that equation by 100% and the result is your flow efficiency for the given time window.

flow efficiency formula
No comment yet.
Scooped by Mickael Ruau
April 29, 2019 11:06 AM
Scoop.it!

Flow-based Leadership - Working in an environment like this is fun

Flow-based Leadership - Working in an environment like this is fun | Devops for Growth | Scoop.it
Flow-based Leadership makes the organization innovative, creative, and profitable. Have you ever worked with a team of people who are all in flow? Great teams are committed and connected. Purpose binds them together. You will do whatever it takes to accomplish your goals.
No comment yet.