I spent the last 6 months looking at the DevOps setups of over 1800 engineering teams. I summarized my learnings in a 30 pages report. Packed with 💣💣s, hope people enjoy it. Check it out 👇
Somewhat eye opening day. Test driven development was cutting edge circa 1999. It is the basis of modern development. I can't imagine not using it. Hearing companies that don't use it, is like hearing companies go "have you heard of this new thing called Linux?" ... wtf?
Je serai de retour à @DevoxxFR pour parler #inclusion et #neuroatypie, avec 'Des Z’Individus et des Z’Interactions, ou l’inclusion des (neuro) atypiques dans les équipes'. Merci aux orgas 🙏
“Agile teams define success as delivering value, not conforming to a plan. In fact, truly Agile teams actively look for opportunities to increase value by changing their plans.”
https://t.co/USs6VnEhsM
An unexpected but welcome benefit of regularly consuming audiobooks is that over time you become a much better listener, which by itself is at least as valuable as whatever is in all those audiobooks.
[THREAD] - « Il n’y a pas de femmes dans le monde #Edtech »
❌ Faux.
🦁 Cherchez mieux.
Elles sont partout.
Elles fourmillent d’idées.
Elles réinventent les codes de la formation.
Retros are about fixing problems in process, not people. A person cannot be a problem if the system within which they work won’t allow it. Fix the system.
Psychological safety must be an organizational attribute to be effective. If safety exists only within the team, it’s impossible to address any problems that are not strictly within the team (i.e. most of them).
@tottinge Honestly; Agile is rarely more than "something those devs does" inside the "implementation" box in a waterfall. Which, of course, misses the whole point entirely.
Docs that describe *how* code works are a hallmark of badly written code. Docs that describe *why* are usually best expressed as comments near the relevant code. Architecture that models the domain only rarely needs “high level” docs that just describe the domain. Not much left.
If teams “can’t think of anything” during a retro, then make that the topic of your retro and fix the problem. I’ve never seen a team that couldn’t improve. In fact, the best teams seem to identify the most opportunities for improvement. They’re always on the lookout.
I hear the "if everyone’s responsible, no one is" chestnut a lot. I don’t buy it. In the most effective teams I’ve worked with, everyone cared about the entire system. 1/2
I made a big mistake when I called them "iterations". I should have just said, "weeks". Then the whole iteration length debate, where there are weird incentives encouraging too-long feedback cycles, would just be absurd.
eduScrum NEWSLETTER February 2022
What people worldwide have done in the various fields of education so far. So, there is a strong WHY :-)
All detailed info you find here: https://t.co/YGUOxHyJAX
Have a lovely February 2022!
Retrouvons-nous mercredi à 12h30 pour un #coaching gratuit en direct des problèmes que vous rencontrez dans la mise en œuvre de l'agilité #scrum
https://t.co/QCfpycJ9wO