Nous avons traduit
« Organiser pour la Complexité » du BetaCodex Network
avec @SylvainPAM18 et @FranckDepierre
Traduction : Organiser pour la complexité
Mes tweets
- RT @jchyip: I wouldn't start with #TeamTopologies by starting with a team; I'd start with the overall situation and what we're trying to do… 2 days ago
- Super interview de @pablopernot toujours aussi interessant 1h30.com/2020/07/30/la-… 2 days ago
- RT @xwarzee: Check out this talk about the Agile Manifesto, Scrum, SAFe, Spotify, behaviors of people and "displined learning" to trim the… 3 days ago
- RT @jchyip: Intermittent (and I would say intentional) collaboration produces better solutions than constant (and I would say mindless) int… 3 days ago
- RT @jchyip: The design of the structure and flow of work should come before the design of teams... and then iterate. 3 days ago
- RT @allenholub: If you hire someone who refuses to work an a collaborative and agile way, forcing them to work in a way that they hate won'… 3 days ago
- RT @madsbrodt: When we work as developers, we're not paid to code. We're not paid to use different languages and frameworks. We're paid to… 3 days ago
- RT @ZenEssentials: "Since the past is unreal and the future is unreal, all your thoughts are about nothing." — Byron Katie | | □∧◯ 3 days ago
- RT @drunkcod: 10 yrs ago when "The Lean Startup" was released many then old Agilists sighed and said "Yes. That's what we ment". I wonder… 3 days ago
- RT @OlafLewitz: leadership conversations on YouTube: I interviewed Christopher Avery on how he started his journey towards Responsibility a… 3 days ago
