schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Frage an alle, die „agil arbeiten": Wann habt ihr das Agile Manifest das letzte Mal gelesen?
Nicht gehört. Gelesen.
Vier Werte. Eine halbe Seite. 25 Jahre alt. Und die meisten kennen den Scrum Guide besser.
Kein Wunder, dass wir Rituale ohne Seele haben.
Das Manifest reicht. Alles andere sind Implementierungsdetails.
https://no-bullshit-agile.de/nbak02-agiles-manifest-immer-noch-die-basis.html
RE: https://hachyderm.io/@trondhjort/116617159142908240
Entwickelnde Personen MÜSSEN Kontakt mit den nutzenden Personen haben.
Sonst entsteht Verschwendung auf verschiedensten Ebenen.
Scrum Master, die "das Entwicklungsteam" von der "Außenwelt" abschirmen, haben ihren Job nicht verstanden.
Wirklich nicht.
#agile boostedOrganisational Dysfunction of the Day
The customer we never met
Context: Context: The team is building a product. They have a backlog, a product owner, and a roadmap. A user story describes what users need. Personas represent who those users are. Analytics track what people do. Every few months, there is a user research report from the UX team. The team works hard, ships regularly, and hits their sprint goals. They have never spoken directly to a customer, though. The product owner does that, and the UX researcher. But the engineers, the people making hundreds of small decisions every day that shape the product, have not. They are building for an abstraction. A persona on a wall, a ticket in Jira, a data point in a dashboard.
OST explains: An open system maintains its health by actively engaging with its environment. For a product team, the primary environment is the people using what they build. The DP1 bureaucracy is a closed system and mediates that relationship through roles: the product owner translates customer needs into requirements, the UX researcher translates behaviour into insights, and the engineer receives the output of both translations. Each translation loses something. The judgment, the context, the friction, the moment when a real person says something that changes how you understand the problem entirely. In DP2, the group owns the whole task, which includes understanding who it is for. Teams with direct customer access make qualitatively different decisions than teams working from second-hand accounts. Not because engineers are better researchers, but because unmediated contact with the environment is not a nice-to-have. For an open system, it is the condition for staying alive.
Organisational Dysfunction of the Day
The customer we never met
Context: Context: The team is building a product. They have a backlog, a product owner, and a roadmap. A user story describes what users need. Personas represent who those users are. Analytics track what people do. Every few months, there is a user research report from the UX team. The team works hard, ships regularly, and hits their sprint goals. They have never spoken directly to a customer, though. The product owner does that, and the UX researcher. But the engineers, the people making hundreds of small decisions every day that shape the product, have not. They are building for an abstraction. A persona on a wall, a ticket in Jira, a data point in a dashboard.
OST explains: An open system maintains its health by actively engaging with its environment. For a product team, the primary environment is the people using what they build. The DP1 bureaucracy is a closed system and mediates that relationship through roles: the product owner translates customer needs into requirements, the UX researcher translates behaviour into insights, and the engineer receives the output of both translations. Each translation loses something. The judgment, the context, the friction, the moment when a real person says something that changes how you understand the problem entirely. In DP2, the group owns the whole task, which includes understanding who it is for. Teams with direct customer access make qualitatively different decisions than teams working from second-hand accounts. Not because engineers are better researchers, but because unmediated contact with the environment is not a nice-to-have. For an open system, it is the condition for staying alive.
A CPO told me: "I don't care if your standup takes 10 or 20 minutes. I care if you learn from what went wrong."
Meanwhile, middle management is obsessing over story points, sprint velocity, and whether the Daily started on time.
The C-Level wants outcomes. Your process police wants compliance.
Stop reporting rituals. Start reporting what you learned and what you'll do differently.
Ansible for DevOps by Jeff Geerling is on sale on Leanpub! Its suggested price is $9.99; get it for $6.99 with this coupon: https://leanpub.com/ansible-for-devops/c/LeanPublishingDaily20260518 #agile #software #startups #ansible #devops #cloud_computing
A Day in the Life of a Product Owner - Scrum.org Blog (Mary Iqbal)
Your CTO put #DORA metrics on a company dashboard. Now teams are competing on deploy frequency.
They're shipping garbage faster.
DORA metrics are a mirror for your team, not a scoreboard for management. The moment you turn them into KPIs or compare Team A to Team B, you've killed their purpose.
Good numbers don't mean good software. They mean you have something worth investigating.
Gedanken zur Agilität:
"Boilerplate Code" wird in der Softwareentwicklung repetitiver Code genannt, der wenig eigene Logik mitbringt.
Ich frage mich, ob wir mit den "Scrum Ceremonies" nicht ziemlich viel organisatorischen "Boilerplate" generieren, und daher bei vielen Betroffenen auch mittlerweile eher Ablehnung auslösen. Was vor 20 Jahren noch notwendig war, was sich heute mit viel breiterem agilen Grundverständnis wirklich obsolet geworden ist. #agile #scrum #agileCoach #Agility
Want to level up your engineering career? Adopt a Product Thinking mindset!
Learn how product management principles can help your engineering team deliver more impactful results, build empathy for users, and take greater ownership of what you build.
🎬 Watch the #InfoQ video by Stéphane Di Cesare & Cat Morris ⇨ https://bit.ly/4eUWnZp
📄 #transcript included
Your team shipped 47 tickets last sprint.
How many of them made your customer money? Or saved them money? Or reduced risk?
If you can't answer that, you're not delivering value. You're delivering activity.
Agility isn't about throughput. It's about asking one question before every iteration: "What's the next thing that creates real value?"
Stop counting tickets. Start counting impact.
“The zero function is the joker of the homogeneous world.” 🃏
In mathematics, it always fits, satisfies every homogeneous system, and silently survives every #transformation.
#AgileCheese adopts the same principle for #agile organizations: when #complexity explodes, become the zero function first. Remove commitments, reset assumptions, reduce to nothing.
From zero, every direction is still possible. That is the power of #cheese. 🧀🚀 #NullFunction #HomogeneousAgility
Just a friendly reminder on my blog this week that Terror is not a helpful strategy for conducting business.
https://www.edyouragilecoach.com/why-copying-corporate-terror-fails/
🏴☠️ 🐻
Your company didn't fail at agile. It failed at understanding why it needed agile in the first place.
You implemented SAFe, followed the Scrum Guide to the letter, and added reporting layers on top.
Congratulations, you built waterfall with standups.
Agile isn't a framework you install. It's the ability to learn, adapt, and deliver value in small steps when you don't know the path yet.
Dear #agile community on #Mastodon: I need honest, brutal feedback.
I wrote the Work-Feedback Loop: a thinking model to diagnose where agile work actually breaks down. Not a framework. A diagnostic tool.
It's a long read. Big ask, I know.
Tell me where the thinking is weak, unclear, or wrong. And if you think it has merit, share it with people who'd challenge it further.
https://no-bullshit-agile.com/wfl/
Boosts very welcome.
As funny as the picture is - it's a serious problem to consider: AI only makes one part of the Work-Feedback Loop faster: Work. But if feedback can't keep up you need to throttle down! There is a ceiling and it's us humans. Never overpace or you will be in trouble. Not today but in the near future when you need to hunt bugs in code you don't understand. And that will be very expensive!
Remember a government RFP some time ago. 60+ pages of contradictory requirements, a fixed-price contract, and zero budget transparency.
The cherry on top? "The goal is agile project management."
You can't put "agile" in a waterfall document and call it a transformation.
Lean Agile Predictability Bundle by Daniel S. Vacanti is the featured bundle of ebooks 📚 on Leanpub!
Link: https://leanpub.com/b/leanagilepredictabilitybundle
#business_and_management #agile #leadership_agile #agile_business_leadership #lean #leadership #project_management #product_management
В RetroPoint — две новые штуки про стратегические ретроспективы 🎯
SWOT-ретроспектива — четыре квадранта (сильные/слабые стороны внутри, возможности/угрозы снаружи) как формат командной встречи. Когда обычное спринт-ретро узко, а нужен срез шире — на квартал или продукт целиком. Разобрали, как удержать команду от «жалоб на рынок» и какие действия рождаются на выходе: 👉 https://retropoint.ru/news/swot-retrospective
Связка SWOT с циклом OKR в один клик 🔗 Со страницы цикла теперь создаётся SWOT-доска по кнопке «Создать SWOT-ретро» — с готовой шапкой цикла над колонками: прогресс, статус, focus-цели. Симметрично уже знакомому Sprint Goal ретро для одного KR: 👉 https://retropoint.ru/news/swot-okr-cycle-link
Удобно перед стартом нового квартала: увидеть «положение» и сразу формулировать Objectives 💡
#RetroPoint #тимлид #1to1 #управлениекомандой #retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #teamleadthings #команда #retroonline #просторетро #oneonone #one2one #pokerplanning #ретро #agile #scrum #realtime #swot #okr
Realtime без тормозов на ретро 🚀
Несколько команд заметили: когда на публичной доске одновременно активны многие участники, страница может тормозить, а часть запросов — падать с ошибкой 😬
Мы разобрались и уже поправили это на production ✅
В чём была проблема: обновления доски идут через realtime (SSE). При пиковой нагрузке сервер слишком долго держал служебные соединения с базой — и новые запросы (открытие доски, вход гостя по паролю) начинали сбоить.
Что сделали 🛠️ — переработали SSE: push по-прежнему мгновенный, база не «висит» на каждом подключении
— увеличили запас API на production
— подкрутили поллинг для гостей
Проверили нагрузкой 📊 Прогнали бенчмарки на реальном prod — типичное ретро и десятки параллельных SSE-подключений проходят без ошибок.
Для обычного спринт-ретро на 15–30 человек — с запасом 💪
Подробности: https://retropoint.ru/news/workspace-realtime-stability-may-2026
Спасибо тем, кто написал прямо во время встречи — это помогло быстро найти баг 🙏
#RetroPoint #тимлид #1to1 #управлениекомандой #retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #teamleadthings #команда #retroonline #просторетро #oneonone #one2one #pokerplanning #ретро #agile #scrum #realtime
I just asked an LLM who runs my website. It confidently invented four different people. When I corrected it, it didn't learn, it just hallucinated a new name.
High activity. Zero learning. The feedback loop never closed. That is the actionism I am warning about in the Work-Feedback Loop and it gets stronger with AI.