On @mfowler blog there is this interesting Article called "Feedback Flywheel": learning from #AI sessions, feeding insights back into shared artifacts.
I've been calling it the Work-Feedback Loop. Same principle, broader frame: a system learns only when work creates feedback that changes the next work.
If your team doesn't learn sprint to sprint, AI won't fix that. You'll just be faster at not learning.

https://martinfowler.com/articles/reduce-friction-ai/feedback-flywheel.html

https://no-bullshit-agile.de/die-work-feedback-loop.html

#WorkFeedbackLoop #AICoding #agile

Damit ich mehr Vorfreude empfinden kann: Wer ist am Montag bei

10 Jahre Agile Nacht Stuttgart
https://www.mitblick.de/agile-nacht-stuttgart/

Die Bühne haben mal wieder ausschließlich Männer gepachtet. Daher gilt dieser Aufruf insbesondere an die Fedinautinnen unter Euch. Freue mich indes aufs Vernetzen mit allen agilen Kreaturen (einschließlich derer, die es werden wollen) dieser Welt. Wo seid Ihr? ;-)

#AgileNachtStuttgart #agile #SCRUM #KANBAN #LegoSeriousPlay #LiberatingStructures #ArtOfHosting #Facilitation

»The Bottleneck Was Never Code« https://www.scrum.org/resources/blog/bottleneck-was-never-code #Agilist.in #Agile #Change #Lean #Kanban #Scrum

4Ls — ретроспектива для длинных этапов и обучающихся команд.

Liked, Learned, Lacked, Longed for — четыре угла рефлексии поверх привычных «плюс / минус». Формат раскрывается там, где Start-Stop-Continue кажется плоской: длинный этап, онбординг, первая ретро новой команды.

В статье — когда 4Ls работает лучше трёх колонок, как провести встречу за 60 минут и как не дать колонкам Learned и Longed for превратиться в формальность.

→ https://retropoint.ru/news/4ls-retrospective

#retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #retropoint #teamleasthings #команда #RetroPoint #LLLL #LikedLearnedLackedLongerfor

Organisational Dysfunction of the Day

Team leads

Context: Most teams in modern agile organisations may not formally have a manager in the same sense as before. Many still have someone they report to as an employee, dealing with yearly reviews, career development, and any job issues, but they are not formally involved in the daily work. It should therefore be possible to have leaderless teams, where all members are peers and have the same say in everything. No ranking. Still, many teams end up being appointed a team lead, often because the organisation wants one contact point and one person in charge of the work done. Many in this position try to deal with this dissonance by taking on a coaching type role, seeing themselves as a "servant leader," giving space to the team and protecting them from the outside. Some even try to switch, being directive sometimes, supportive at other times (aka situational leadership). Not only is this a tricky job to have, but it also creates so much confusion in the team about who really decides and is in charge.

OST explains: DP1-type organisations require personal leadership positions, as that is how control, coordination and alignment are managed. Agile tries to counter that for efficiency, having teams take more control of the work, in an attempt to shorten the feedback loop and the learning. This is similar to DP2, with self-organising teams, while adding team leaders is not and is an attempt to adapt them to the existing bureaucratic DP1 model. The problem with this is that DP1 and DP2 fit together like oil and water; they are fundamentally so different that no matter how good the adapters are, they will lead to confusion and operational problems. You can remove the need for this adapter by ditching DP1, having teams everywhere and letting them take responsibility for their own goals and the integration needed to work with other teams. Teams may decide to appoint a leader, though, for their own needs, either permanently or when needed, but it is not a formal position of power. It is a participative democracy through and through.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

»[Case Study] When a Security Rollout Became a Design Problem« https://agilealliance.org/case-study-when-a-security-rollout-became-a-design-problem/ #Agilist.in #Agile #Change #Lean #Kanban #Scrum

Real user story seen in the wild: as a system I want to connect to the database to get the data

#Agile

@itagile @StefanRoock I also love his case that some don’t want to talk about #agile any more. That’s why I wrote the Work-Feedback Loop. Read it and decide what you need to change! https://no-bullshit-agile.com/wfl/

“Scrum is a mini waterfall” - Andy Hunt.

Listen to him… you need more in place than Scrum if you develop software or you will fail…

https://podcasts.apple.com/de/podcast/einfach-gel%C3%B6st/id1872365636

Thanks for the episode @itagile @StefanRoock

#agile #scrum

Dew Drop Weekly Newsletter 479 - Week Ending April 17, 2026

https://zc.vg/goz7d?m=0

#dewdrop #newsletter #javascript #azure #css #aspnetcore #aspire #xaml #appdev #windowsdev #cpp #dotnet #csharp #ai #mcp #agile #devops #dotnetmaui #podcasts #m365 #sqlserver #data #powershell #terminal

Manchmal frage ich mich, ob die meisten Dinge, die ich zum Thema #LateralesFühren gelernt habe, nicht einfach manipulativer Mist waren. #Führung #Agile

В RetroPoint запустили раздел «Команды» в профиле.

Теперь управление составом и доступом к доскам живёт в одном месте:
— список команд с карточкой и составом «N+1» (участники + лидер бренд-цветом);
— экран команды с вкладками «Участники», «Инвайты» и «Настройки»;
— приглашение по ссылке → отдельная страница приёма инвайта;
— подсказки по лимиту тарифа: сколько участников можно добавить и сколько уже занято.

Раньше владельцу кабинета приходилось держать состав и доступы «в голове» — теперь всё в одном интерфейсе, и для владельца, и для участников команды.

Открыть: https://retropoint.ru/profile/teams
Подробности: https://retropoint.ru/news/teams-block-launch

@rf@mastodon.ml @rf@mas.to @Russia@3zi.ru @russia@lemmy.ml

#retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #retropoint #teamleasthings #команда #RetroPoint #madsadglad

»Industrialism’s Dehumanization Trap« https://www.scrum.org/resources/blog/industrialisms-dehumanization-trap #Agilist.in #Agile #Change #Lean #Kanban #Scrum

»If nothing changes next Sprint, your Retrospective failed« https://www.scrum.org/resources/blog/if-nothing-changes-next-sprint-your-retrospective-failed #Agilist.in #Agile #Change #Lean #Kanban #Scrum

The Tester's Library by Gerald M. Weinberg is the featured bundle of ebooks 📚 on Leanpub!

Link: https://leanpub.com/b/thetesterslibrary

#testing #project_management #agile #software #leadership #systems_engineering #design #teamwork #software_architecture #computer_science #selfhelp #consulting #psychology #thriller #science_fiction

Когда сухое «что улучшить» не работает — попробуйте Mad, Sad, Glad!

Есть состояние команды, в котором классические ретро буксуют: после тяжёлого спринта, серии инцидентов или организационной перемены люди приходят на встречу молчаливые и усталые. Списки «что улучшить» получаются формальными, обсуждение не едет.

Mad, Sad, Glad — формат, который не идёт в решения с первой минуты. Сначала он разгружает команду, а уже потом вытаскивает темы для изменений.

Три колонки:
▫️ Mad — что раздражало: падающие тесты, ночные инциденты, смена приоритетов на лету. Правило: пишем про процессы и ситуации, не про людей.
▫️ Sad — что расстроило: успели меньше, чем планировали; ушёл коллега; идея не долетела до релиза. Тихие сожаления, не претензии.
▫️ Glad — чему радовались: победы, благодарности, человеческие мелочи. Колонку важно заполнить даже после самого тяжёлого спринта — она удерживает встречу от общего уныния.

Что делает формат рабочим — и что его ломает:
✅ Правила на входе (5 минут). Психологическая безопасность — не декорация, а рабочее условие.
✅ Индивидуальное заполнение в тишине: эмоциональные темы легко затирают голос интровертов.
✅ Явный переход «от эмоций к действиям» — без него формат превращается в чат поддержки.
❌ Обсуждение скатывается в персоналии.
❌ Пустая колонка Glad после жалоб.
❌ Делать Mad, Sad, Glad каждый спринт — заряд формата притупляется, 1 раз в 3–4 ретро достаточно.

В новом материале RetroPoint разобрали:
— когда Mad, Sad, Glad работает лучше других форматов;
— как провести встречу за 50 минут с таймингом по шагам;
— какие ловушки прячутся в психологической безопасности;
— чем формат отличается от What Went Well и Start, Stop, Continue;
— когда лучше выбрать что-то другое.

👉 Статья: https://retropoint.ru/news/mad-sad-glad-retrospective

Запустить доску по этому шаблону можно прямо со страницы техники — три колонки уже настроены.

@rf@mastodon.ml @rf@mas.to @Russia@3zi.ru @russia@lemmy.ml

#retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #retropoint #teamleasthings #команда #RetroPoint #madsadglad

Designing Large-Scale Software for Reuse With an Automotive Company

An #Agile Dev Success Story: A European automotive OEM had to upgrade its infotainment system to support multiple Android versions — and make the software extensible across product lines.
https://www.aptiv.com/en/insights/article/designing-large-scale-software-for-reuse-with-an-automotive-company

»Scaled Agile, Inc. Names Two New SAFe® Fellows« https://scaledagile.com/blog/scaled-agile-inc-names-two-new-safe-fellows/ #Agilist.in #Agile #Change #Lean #Kanban #Scrum

On your boards: do stories change status, do subtasks change status, and do stories only change when subtasks are done? Or some other combination? Why?

#agile #jira #scrum #kanban #flow

Organisational Dysfunction of the Day

Quiet quitting

Context: During the COVID-19 pandemic, many things were exacerbated in the population, including how people feel about work. A major trend in America was referred to as the Great Resignation, in which many cited the quality of work as a reason for leaving. Another trend that surfaced about the same time was Quiet Quitting, where employees who are fulfilling their job requirements, but not taking initiative, working overtime or volunteering for extra projects or responsibilities. In short, people are not engaged at work, something the Gallup's State of the Global Workplace report confirms, saying that only 20% of are engaged and 16% are actively disengaged. So not only are sick leaves and absenteeism a problem; when people are at work, just a small minority are actually enjoying it.

OST explains: The reason for these dreadful numbers drops right out of OST and all the research it builds on since the 1950s. Given that the extrinsic motivators for work are satisfactory, such as security, work hours, and pay, the defining reasons for people enjoying work are how well their intrinsic motivators are being fulfilled. A minimal set of six psychological job requirements is the basis and they measure how well a job design works, be it the processes, the technology, the organisation, or the colleagues. If people score well on things like ownership, learning on the job, variety, support and respect, meaningfulness, and career path, they will not only enjoy work, be engaged and produce better results; they will also get a better quality of life.

#OpenSystemsTheory #SocioTechnical #OrgDesign #agile

»Psychological Safety in AI Driven Teams« https://www.scrum.org/resources/blog/psychological-safety-ai-driven-teams #Agilist.in #Agile #Change #Lean #Kanban #Scrum

In this #InfoQ #podcast, Sam Bhagwat, co-founder & CEO of Mastra, shares insights on building and sustaining #opensource communities, the emerging discipline of #AI engineering and evals, and why cross-functional Tiger Teams are key to shipping agentic applications.

🎧 Listen now: https://bit.ly/4tQpH7w

📄 #transcript included

#Teamwork #DistributedTeams #Agile

»Daily Sprints and the Impact of AI« https://www.scrum.org/resources/blog/daily-sprints-and-impact-ai #Agilist.in #Agile #Change #Lean #Kanban #Scrum

“Self-managed” is just a polite way of saying “manage yourself harder.”

In #agile, autonomy without boundaries becomes self-exploitation. The boss didn’t disappear — it moved inside you.

#AgileCheese calls it out: you optimize, monitor, and pressure yourself, all in the name of ownership.

#AI perfects this. More speed, more expectations, no excuses.

Real freedom starts when you decide when not to. That’s where #cheese begins. 🧀🔥

Is #Cylenivo a tool for you to consider? I blogged about it.

https://no-bullshit-agile.com/cylenivo-a-tool-not-a-cockpit.html

#Agile #CycleTime #LeadTime #Flow #Jira #Kanban #Scrum

Organisational Dysfunction of the Day

Individualism

Context: Often, there is a large disproportion in how much people are celebrated for their achievements and when blame is placed for accountability when something goes wrong. This feels natural in most parts of the world, as we want to take care of the people and make them feel as good as possible so that they'll feel well and stick around. Being human, as we say. Even toward the people who clearly take on the accountability, and are even paid good money to do so, often leading to few or no consequences. We value the individual when celebrations are due, when heroes are praised, but hide them when there is not. Typically, hero cultures are also a power play, as the ones praised become stretch goals for the rest, showing what lengths they have to go to feel respected and truly valued.

OST explains: This focus on the individual is almost anathema in OST, not because the individual is not valued, but it realises that the group is the basic unit of life, be it your family, your friends or your colleagues. It's founded on the belief that people have both the need for autonomy and homonomy; be able to self-govern and fit in with the group. Actually, valuing individuality as an acontextual thing hides a vital paradox, as it inevitably isolates people as the problem because there is nothing else to blame. It even goes beyond blaming the victim; it creates them. By instead focusing on the group, and having it take responsibility and accountability, it can take both the praise AND the blame. The individual is protected in the group, and it can jointly grow and learn from successes and failures. As it takes them to their shared goals.

 #OpenSystemsTheory #SocioTechnical #OrgDesign #agile

Ist #Cylenivo was für dich? Ich habe dazu mal was gebloggt.

https://no-bullshit-agile.de/cylenivo-ein-werkzeug-kein-cockpit.html

#Agile #CycleTime #LeadTime #Flow #Kanban #Scrum

🟢🔴🔵 Start, Stop, Continue — ретроспектива за 45 минут

Самый короткий путь от «как всё прошло» к «что мы сделаем по‑другому». Всего три колонки:
• Start — что начать делать
• Stop — что мешает и пора прекратить
• Continue — что работает и бережём

Формат ловко обходит два типичных провала ретро: разговор не скатывается в «сплошной негатив», и команда не тонет в деталях. За 45 минут выходите с 2–3 конкретными договорённостями и владельцами.

В новой статье разобрали: кому подходит, как провести по таймингу, каких ловушек избегать и чем SSC отличается от What Went Well, 4Ls и Mad/Sad/Glad.

👉 Читать: https://retropoint.ru/news/start-stop-continue-retrospective

А в RetroPoint доску по этому шаблону можно создать в один клик.

@rf@mastodon.ml @rf@mas.to @Russia@3zi.ru @russia@lemmy.ml

#retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #retropoint #teamleasthings #команда #RetroPoint

»Advice on Leadership« https://bobgalen.substack.com/p/advice-on-leadership #Agilist.in #Agile #Change #Lean #Kanban #Scrum

Great engineering organisations reward prevention, not heroics.

The best teams celebrate:

• fewer incidents
• fewer emergencies
• fewer late nights

Quiet reliability beats dramatic rescues.
#Software #Dev #Agile #Smells #Heroics

Invensis Learning included an excerpt from my Agile Transformation book in their "Who is a Scrum Master? Here’s Everything You Need to Know" article on LinkedIn 👉 https://linkedin.com/pulse/who-scrum-master-heres-everything-you-need-know-invensis-learning/. Appreciated!

#Agile #Scrum #AgileTransformation

»Kate's Career Switch Story From Business Analyst To Scrum Master« https://www.scrum.org/resources/blog/kates-career-switch-story-business-analyst-scrum-master #Agilist.in #Agile #Change #Lean #Kanban #Scrum

Books to grow your tech career? There's a video on that — and it includes “Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions.”

#Tech #TechCareer #Agile #AgileCareer #TechBooks #AgileScrumGuide

https://youtu.be/8NY769uKOpI?t=924

🔗 Book on Amazon: https://amzn.to/41KB7OZ

Interesting view on agile development and how LLMs are changing it.

https://lewiscampbell.tech/blog/260414.html

I specifically liked this:

«One unambiguously positive development that's followed is that software professionals are writing specs again. [...] Agile told us "Working software over comprehensive documentation". Spec-Driven Development is telling us "Comprehensive documentation creates working software"»

#softwareDevelopment #agile

This isn't your typical Agile transformation book

"A sharp, funny satire that sneaks legit Agile lessons into the hilarious story." —Review on Goodreads

Get "Agile Protocol" on Amazon and Audible 👉 https://amzn.to/4bVpiJI

#Agile #AgileTransformation #AgileCoach #Kindle #eBook