»Integrating AI into Scrum Teams: Insights with Claudio Lassala« http://drunkenpm.blogspot.com/2026/05/integrating-ai-into-scrum-teams.html #Agilist.in #Agile #Change #Lean #Kanban #Scrum

»The AI Engagement Lifecycle with Endava, Dava.X.AI, and Miro« http://drunkenpm.blogspot.com/2026/05/the-ai-engagement-lifecycle-with-endava.html #Agilist.in #Agile #Change #Lean #Kanban #Scrum

I have reworked my article against a #test / #qa column on boards and could add some more voices.
https://www.enteresc.net/why-a-test-column-on-boards-is-a-problem/

#scrum #kanban #agile

In Agile:

“Potentially shippable is defined by a state of confidence or readiness, and shipping is a business decision.”
— Scott M. Graffius

#Agile #Scrum #AgileProjectManagement #PotentiallyShippable #ProductIncrement #PSPI

Bin erstaunt und freue mich, dass trotz Podcast-Pause die erste Folge der neuen Season am oberen Ende der Downloads nach 3 Tagen im Vergleich zu älteren Folgen ist.

NBA Kompakt ist das neue Format: Ein Thema - 5 Minuten. Der komplette Plan steht. https://no-bullshit-agile.de/nba-kompakt-alle-folgen.html

NBAK01: Gute Software schnell liefern
https://no-bullshit-agile.de/nbak01-gute-software-schnell-liefern.html

#Podcast #Agile

Alt...

GUTE SOFTWARE SCHNELL LIEFERN

Heard a story in a podcast episode: A PO once planned every sprint until the end of the year based on velocity. Every single sprint.

That's not agile planning. That's a waterfall Gantt chart wearing a Scrum costume.

#agile #scrum

Alt...

VELOCITY IS NOT A CRYSTAL BALL

You can't mandate a mindset. You can only model it.

Be that one person who just does things differently: ships smaller, asks better questions, admits mistakes first. That's the flywheel. Not a workshop. Not a framework rollout.

Change spreads through behavior, not through slides.

#agile #leadership

Alt...

THE FLYWHEEL IS BEHAVIOR, NOT SLIDES

“Thriving in today's marketplace frequently depends on making a transformation to become more agile.” — Scott M. Graffius, Agile Transformation

Shop the book on Amazon: https://amzn.to/4dghWCw

#Agile #Scrum #AgileTransformation #Book #Quote

Продолжаем полировать RetroPoint — без громкого релиза, но с заметной разницей в ежедневной работе.

Что улучшили:
📱 Мобильный интерфейс — профиль (все разделы видны сразу), команды, кабинет 1‑2‑1, OKR и Planning Poker: формы влезают в экран, кнопки не «плывут».
🤝 1‑2‑1 — к приглашению на встречу можно добавить заметки (ссылка на созвон, контекст): они уйдут в письмо, календарь и повестку.
🔐 Вход — меньше ложных «вылетов» из аккаунта при переходах между разделами и после подтверждения email.

Мелочи, которые экономят нервы команде на удалёнке.

Подробности — в новости на сайте: https://retropoint.ru/news/mobile-ui-and-stable-login-may-2026

#RetroPoint #тимлид #1to1 #управлениекомандой #retrospective #ретроспектива #agile #scrum #kanban #teamlead #it #itleads #teamleadthings #команда #retroonline #просторетро #oneonone #one2one #pokerplanning

What has become out the of "sustainable pace" idea? No more deathmarch-projects, one after another?
I have the impression, with AI-Assistance in coding the fatigue becomes not a smaller problem, but a bigger problem. With reduced staff, extensive use of "AI-Coding-Agents" we will loose even more seniors to burnout and fatigue. #GenAI #LLM #Coding #Agile

Hiring an Agile Coach won't make your company agile. Neither will a mandate from the CEO. It can help though if you also remember the following.

Agility spreads through a small group of people who actually understand it and who are given the space to prove it works.

No role, no title, no framework will do that job for you.

#agile #leadership

Alt...

Agile Coach won't save you

Every company claims to have a "culture of learning from mistakes."

Then something goes wrong and the first question is: "Who did this?"

You don't have a failure culture. You have a blame culture with better marketing.

#agile #leadership

Alt...

FAILURE CULTURE WITH BETTER MARKETING

If you work at an agency and call yourself "Product Owner" — you're not one. You're a proxy.

The real PO is the client. They own the vision, the market, the risk. You sort tickets.

Scrum defined this role for product companies, not for agencies. Stop pretending it fits. I made that error myself and it felt wrong the whole time.

#agile #scrum

Alt...

PRODUCT OWNER YOURE A PROXY

Stop trying to reach consensus in your team. You'll get silence, dominant voices, or fake agreement.

Try consent instead: "Does anyone have a serious objection?" No objection = we move forward. You can always revisit.

Faster decisions. More voices heard. Less theater.

#agile #leadership

Alt...

CONSENSUS IS A TRAP

„Wir bauen erstmal alles fertig, dann zeigen wir es dem Kunden."

Drei Monate Annahmen aufeinander gestapelt. Kein Feedback. Kein Lernen. Nur die Hoffnung, dass es passt.

Agiles Arbeiten heißt: Gute Software schnell liefern. Nicht perfekt. Nicht alles. Aber auf die Straße gebracht, damit du lernst, ob es funktioniert.

#agile #softwareengineering

Alt...

Erst bauen, dann hoffen

Dew Drop Weekly Newsletter 483 - Week Ending May 15, 2026

https://zc.vg/67UPi?m=0

#dewdrop #newsletter #aspnetcore #javascript #css #azure #xaml #windowsdev #cpp #csharp #dotnet #efcore #ai #mcp #devops #agile #IoT #appdev #podcasts #m365 #sqlserver #data #powershell #devtools

The plan is, the plan will change

End of the road

A precise plan produces an intricate list of tasks, often estimated to the day or half day, that will fall apart as soon as it is introduced to the real world, because no precise plan I have seen ever has a task for “the framework I’m using doesn’t support a command that updates 2 Business Objects” or “Investigate a fix for that NHibernate GROUP BY bug”. It cannot be precise about the known unknowns, unless you accept that in knowing them, the plan becomes void. Furthermore, it cannot include the unknown unknowns, because then they wouldn’t be unknown. If you minimise the detail in those areas, estimates will expand to cover the risk. Unknowns should be big and scary. It’s better to say it’s 1000 miles to walk from Glasgow to Dunnet Head and revise your estimate down as you see detail of the roads, than start by saying it’s 100 miles because you didn’t see the mountains and lochs in the way.

Estimates for project management

“Ah,” says the reader, “but aren’t you misrepresenting the value of estimates and planning? We don’t care that the plan is going to change, so long as the Project Manager can work out how much it has changed, so that they can feed that into change control”.

It sounds fair, if the variation is caused by a customer who understands the plan and accepts the variation. If the customer expects us to know the details of every library we choose better than they do, or expects us to work with Supplier X no matter what format they use, it’s a harder call to make.

When I compress a plan to be the best guess set of tasks-to-complete, estimated down to the hour, I end up vacuum-packing and squeezing out the contingency directly into the project, and leaving myself, as the lead, no room to manoeuvre when we inevitably have to deal with something that isn’t on that list.

Estimates for risk

This is different from the general project contingency that every Project Manager adds to ensure there is breathing space in the estimates. Developer contingency anchors in the risk surrounding the tasks, and has to be estimated at a technical level, and has to carry itself alongside the tasks that present the risk. If there is no opportunity to address the risk during the appropriate development cycle, and possibly to fail and restart the task in extreme cases, then the feedback loop will be longer, and any problems will be harder to fix, and the delivery itself will be put at risk.

If the plan is complete, it has to accept variability, and greater vagueness. I can expect that a web service request will involve 1 authentication call and 1 search request, but if I see there is a risk with a reasonable chance of being realised, that I will need more calls, and to write a custom web service handler, I need the plan to accommodate that risk, and as a Technical Lead, the breakdown and the estimates are the place I can control that risk. If my estimates include the risk, which I cannot be as precise about, then I am in a much better position to say that half my estimates will be too low, and half will be too high, rather than defaulting to the optimist whose estimates have an 80% chance of being too low.

The less contingency I put in, replaced by details, the more likely it is that the plan will drift rightwards. When it does, I need to re-estimate, and I want to know where my fixed points are, the details that I’ve worked out and can’t be changed, whether that’s the deadline, a specific web service, or the work already in progress. The road less known is the road less estimated, and that where the scope is dynamic, where work can be moved, re-estimated, broken down, and negotiated.

Further watching

Why is Scrum So Hard?

I don’t trust change

Everything changes

I don’t trust change. I know change is what we do, it’s why people need new software to do things they couldn’t do before, to sweep away the cobwebs and start everything anew. To change. For the better.

The better what? Faster, more efficient, more user friendly. “Just better”. “An improvement”. “The new shiny”. “Make it cool”.

Great, can you write me a requirement for that, or some acceptance criteria?

“We’ll know it when we see it.”

But how will we know?

“It doesn’t matter. We’ll know.”

And when you come back and say it doesn’t have enough “zing” or “pizazz” or isn’t “cool” or “new” enough?

“Well then, it shows you didn’t listen to us.”

A change for the better?

If you want to change, you should know why. What will the users notice? What pain will it take away? What will it allow you to do that you couldn’t do before?

Those are questions I can pick away at, questions with an answer where I can measure something tangible. I can change the time it takes to do something, I can change a system to do something new, and I can show you exactly what the change looks like.

A change without a diff is a break.

If you don’t know why you’re making a change, the chances are, you’re making the wrong change, and you won’t know when the change is done. Make a small improvement, or a big one, but know why. If you can’t articulate the difference between the present reality and the desired future, all I can tell you is that the change will break. It might be beneficial, it might not, but there will be no way to trace from now to the future, and no way to know if anything has improved.

The best change may be no change

We love writing software, coming up with new ideas, new approaches. We want the new shiny. But that doesn’t mean it will do us, or our customers, any good. Angular.js makes it much easier to write web apps a certain way, but is that the type of web app that most suits your customer, and do they really need a web app at all? Is a web page easier for them?

And maybe what needs to change isn’t the software. Maybe there is a process that people have forgotten that will fix the problems, maybe they’re solving the wrong problem.

Software isn’t always the answer, and neither is change.

When to embrace change.

Change when things cause you pain. Subversion makes branching and merging painful. If that’s a problem for you, try git or mercurial. Manipulating the DOM from a callback is painful. If that’s a problem for you, try Angular or another framework. If they’re not causing you pain, chances are something else is, go change that first.

Change when there’s a functionality gap. When you’re chasing a new regulations, new APIs, new competitors, or new customers. And make sure that functionality does something to help close that gap. You might have a few ideas, so pretotype and prototype them first, make the change as small as possible, and build on it, because a small change is easier to throw away, physically and psychologically.

Embrace change.

But don’t trust it, until you know where you want the change to take you, and you have a way to check you’re on the right path.

responding to change over following a plan

Failure to plan is planning to fail.

Things change. I might not trust change, but I accept it and allow for it. But there’s always a direction, a star to follow.

Plans provide a common direction and steps to get there. Agile just means the steps aren’t always the right ones, and the goal may change, but you should always have a goal and next steps.

Question the plan, agree on a new plan and agree to follow it. It’s worse than not having a plan because if you don’t follow the agreed goal, especially in silence, you are actively hostile to the success of the team.

Some deadlines don’t change. If you’re in retail, you’d better be ready for Christmas. If you’re a business, you’d better be ready for the end of the tax year.

Keep your plan visible, and keep your plan flexible. It will change, but without a plan and a reason for the work, you’ll never know what you should be saying no to.

Alt...

A grass path. A clear direction to follow with well maintained grass surrounded by wilder grass

Do you feel like Pablo Escobar waiting for developers to learn threat modeling? The waiting time is over!! #appsec #owasp #llm #agentic #ai #security #cloud #devops #frontend #webdev #threatmodeling #agile #games

Do you feel like Pablo Escobar waiting for developers to learn threat modeling?

The waiting time is over!!

The new OWASP Cornucopia 25th anniversary edition contains both the OWASP Cornucopia Companion and the Website App Edition. The new edition comes with 6 companion suits covering new topics:
Agentic AI (AAI), Automated Threats (BOT), Cloud (CLD), Frontend (FRE), Large Language Models (LLM), and DevOps (DVO).

#appsec #owasp #llm #agentic #ai #security #cloud #devops #frontend #agile #games

Yes! It’s time to party!!

It was an honor to participate at the OWASP Virtual Conference commemorating the 25th anniversary. Here is the video: https://youtu.be/KmjUM0EF_24?is=4-0fir-KT02lAr6A

The OWASP Foundation is celebrating 25 incredible years of open source security. That’s why OWASP Cornucopia is launching its 25th anniversary edition. Read all about it here:  https://dev.to/owasp/introducing-a-owasp-game-for-threat-modeling-agentic-ai-cloud-devops-frontend-llm-automation-5984

#OWASP25thAnniversary #OWASP #AppSec #security #threatmodeling #games #agile #lean #llm #agentic #devops #cloud #fromtend

The OWASP Foundation is celebrating 25 incredible years of open source security. That’s why OWASP Cornucopia is launching its 25th anniversary edition. Read all about it here:  dev.to/owasp/introd... #AppSec #security #threatmodeling #games #agile #lean #llm #agentic #devops #cloud #fromtend

Introducing a OWASP Game for t...

Yes! It’s time to party!! It was an honor to participate at the OWASP Virtual Conference commemorating the 25th anniversary. Here is the video: youtu.be/KmjUM0EF_24?... #OWASP25thAnniversary #OWASP #AppSec #security #threatmodeling #games #agile #lean #llm #agentic #devops #cloud #fromtend

OWASP Cornucopia - Stop Lectur...

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/LeanPublishingDaily20260511 #agile #software #startups #ansible #devops #cloud_computing

Silence in a meeting is not agreement. It's fear wearing a mask.

If your team "agrees" in 5 minutes, nobody actually shared what they think. You didn't make a decision but one person did, and the rest let it happen.

#agile #leadership

Alt...

SILENCE IS NOT AGREEMENT

AI makes your team produce code faster. It does not make your team learn faster.

We tried it. Code generation looks fast until someone has to review, understand, and fix what the AI wrote. As so many already said: The bottleneck was never typing speed. I can confirm...

What OpenAI and Anthropic sell you is marketing. They have to.

#ai #agile

Alt...

FASTER CODE IS NOT FASTER LEARNING

RE: https://norden.social/@AgilePreacher/116572274676273996

Das klingt vielversprechend.

Hamburger Agile Bubble, wo seid ihr?

#Hamburg #Agile #Agilität #ProductOwner #Scrum #ScrumOfScrum #AgileJob

Kleiner Test - ich überlege, ob ich die Podcast Folgen von NBAK auch hier direkt auf #Mastodon veröffentliche... Gut?

Shownotes sind dann auf der Webseite: https://no-bullshit-agile.de/nbak01-gute-software-schnell-liefern.html

#Podcast #Mastodon #Agile

Alt...

NBAK01: Gute Software schnell liefern

„Warum agil?" – falsche Frage.

Die richtige: Kannst du gute Software schnell liefern?

Drei Wörter. Entpacke sie und du hast alles:
• „Gut" = wertvoll, nicht perfekt
• „Schnell" = kurze Zyklen, nicht Hektik
• „Liefern" = in Produktion, nicht „fast fertig"

Der ganze Rest? Work und Feedback. Punkt.

Neues Format: NBA Kompakt – ein Thema, fünf Minuten, klare Meinung.

https://no-bullshit-agile.de/nbak01-gute-software-schnell-liefern.html

#Agile #Softwareentwicklung #NoBullshitAgile #Podcast

You ran an "agile kickoff workshop." The client nodded along. Three months later: "So when will everything be done?"

That's not a client problem. That's yours. One workshop doesn't create understanding. Continuous alignment does. Stop blaming the customer for not "getting agile."

#agile #projectmanagement #leadership #teamwork

Conway’s Law warns that software reflects the team’s communication. As AI makes generating "perfect" specs easy, we risk killing the vital human discussions that ensure alignment. Is speed worth a fragmented product? Explore the risks of the AI-spec illusion: https://brodzinski.com/2026/04/conways-law-ai-product-development.html #ProductManagement #Agile

Was ist eigentlich aus der Erkenntnis geworden, dass Menschen in Teams bessere Problemlösungen finden als Einzelkämpfer? Die LLM-gestützte Softwareentwicklung feiert ja gerade ab, das Menschen alleine Software zusammenklöppeln können - ohne Erfahrung und ohne Team. Aber kommen dabei wirklich gute Lösungen raus, wenn die zusätzlichen Perspektiven unterschiedlicher Erfahrungen fehlen?
#agile #softwareengineering #team #genai #LLM

10 recommended books on Agile

https://doi.org/10.13140/RG.2.2.27816.64002

#Agile #Scrum #ProjectManagement #Books #AgileBooks #10AgileBooks

»Case Study: How Joy and Kaizen Helped Drive 16x Sales Growth« https://agilealliance.org/case-study-how-joy-and-kaizen-helped-drive-16x-sales-growth/ #Agilist.in #Agile #Change #Lean #Kanban #Scrum

»The Calm Before the Storm« https://bobgalen.substack.com/p/the-calm-before-the-storm #Agilist.in #Agile #Change #Lean #Kanban #Scrum

"We're agile, we don't need a plan."

Wrong. Agile means planning *more*, not less. Every sprint, every standup, every retro - that's all planning.

What you actually mean: "I don't want to be held accountable for a plan." That's not agile. That's chaos.

#agile #projectmanagement #scrum #kanban #leadership

Kann sein, dass ich da was vorhabe... stay tuned...

#agile #podcast #nba #nbak

Alt...

NBAK - NBA Kompakt

Games are an excellent way to ensure the team grows and learns together; this is why OWASP Cornucopia helps teams scale application processes like threat modeling and requirement analysis. So, play OWASP Cornucopia! #llm #agentic #ai #security #agile #games

"Doing Scrum" doesn't make you agile. Neither does Jira, a daily standup, or calling someone "Product Owner."

Agility is a mindset, not a toolbox. If you don't understand why you're doing it, the framework won't save you.

Most teams fail at agile not because they picked the wrong method but because they never understood the foundation.

#agile #scrum #kanban #leadership #agilecoaching

The edition comes with 6 companion suits covering new topics:
Agentic AI (AAI), Automated Threats (BOT), Cloud (CLD), Frontend (FRE), Large Language Models (LLM), and DevOps (DVO).

Play it at copi.owasp.org , buy it at CyberSec Games: https://cybersecgames.com/pages/owasp-cornucopia-threat-modeling-collection , or download from our latest release: https://github.com/OWASP/cornucopia/releases/tag/v3.0.0

#appsec #owasp #llm #agentic #ai #security #cloud #devops #threatmodeling #agile #games

Games are an excellent way to ensure the team grows and learns together; this is why OWASP Cornucopia helps teams scale application processes like threat modeling and requirement analysis.

So, play OWASP Cornucopia!

The new OWASP Cornucopia 25th anniversary edition contains the OWASP Cornucopia Companion and the Website App Edition.

#appsec #owasp #llm #agentic #ai #security #cloud #devops #threatmodeling #agile #games