GOTO Conferences’ Post

Can AI help you achieve the coveted flow state? Shannon Mason of Tempo Software explains how AI can help with agile development. By Loraine Lawson

Can AI help you achieve the coveted flow state? Shannon Mason of Tempo Software explains how AI can help with agile development. By Loraine Lawson

The vibecoding workshop with Gene Kim and Steve Yegge was a blast! My key takeaways: - Programming by hand will be niche activity - The teams need to adapt: both how they work and their structure - Development is shifting left towards business; and the dev loops / lead time is at the all time low! 💣 It’s amazing that we were shifting left since the publication of agile manifesto in 2001: „Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.“ And now development comes even closer to the stakeholders. I ponder, if „customers“ will start vibe coding on their own at one point without any sort of developers in the loop.

I heard product managers will come with a prototype to the dev team instead of requirements as text. Using tools like lovable, rovo dev and amp this becomes possible. Interesting thought and development. Also use all the tools never decide to one. Some can code some can write tests and one of them will most likely figure it out without one line code written by the developer himself. Wait for all the examples we did this week.

Why Your 'Agile' Team Hasn't Shipped Anything Meaningful in 6 Months" Your daily standups are just group therapy for developers trapped in architectural quicksand. Change my mind. "We're blocked waiting for the backend team" "The API changes broke our sprint" "Database team says 2 more weeks" "Still investigating that integration issue" Sound familiar? That's not Agile. That's Fragile. Your "Agile" reality: 15 people to add a dropdown field 6 meetings to agree on API contract 3 teams to coordinate deployment 2 sprints become 2 quarters Why? Because you separated concerns wrong. You split by technology (database/backend/frontend) Instead of business function (invoice/user/payment) Result? Everything requires everyone. Nothing ships. Real client story: "We do Scrum perfectly!" "How long to add a new field to invoices?" "6 weeks, 3 sprints" "For one field?" "Well, we need database migration, API update, frontend changes..." We rebuilt their system with Yolm: Invoice Block: Contains table, API, UI, logic Time to add field: 30 minutes Deployments: Instant Sprints needed: 0 Agile was supposed to mean FAST. When did we accept 6-week sprints for 1-day work? Your process isn't broken. Your architecture is. Who's ready to admit their "Agile transformation" just added more meetings to slow delivery? #Agile #Scrum #ProductDevelopment #TechLeadership

Ever confused Refactoring with a Spike in your agile sprints? 🤔 While both are crucial for healthy software development, they serve vastly different purposes! Think of it like tending a garden 🌳: Refactoring is like weeding and pruning an existing, productive plant. You're improving its internal structure – cleaning up tangled code, optimizing functions, or clarifying variable names – without changing its external behavior (it still grows the same fruit). A real-time example? Improving the efficiency of an existing authentication service to handle more load, or redesigning a module for better maintainability after it's already working. You know exactly what you're fixing and why. A Spike, on the other hand, is like planting a small, experimental seed 🌱 to see if a certain type of plant can even grow in your garden's soil, or if it will produce the fruit you hope for. It's a time-boxed investigation into an unknown. For instance, prototyping a new third-party API integration, researching a novel AI algorithm, or trying out a new database technology to see if it meets requirements. You expect to throw away most of this exploratory work, gaining only knowledge. One enhances what's already good; the other explores what's unknown. Both are vital for sustainable innovation! #AgileDevelopment #Scrum #SoftwareEngineering #TechLeadership #Refactoring #TechDebt #Spike #ProductDevelopment #CodeQuality #ContinuousImprovement

From Chaos to Clarity in the SDLC Software projects often fail not because of bad code but because of ambiguity. Different teams, different interpretations, different tools. LensHub brings everyone together under one collaborative portal, where practices stay consistent and knowledge becomes cumulative, not fragmented. The built-in AI assistant learns your team’s rhythm. Prompts are customizable, reusable, and context-aware, no external apps required. We made a short 90-second video (https://lnkd.in/dTUt4kvf) that explains it better than words. Would love to hear your thoughts and what does “clarity” mean for your SDLC process?

Sometimes it’s difficult to put ourselves in the shoes of our users. One framework that helps me is the simple Agile user story: As a [type of user], I want [goal/action], so that [benefit]. For example: As a job seeker, I want AI to suggest tailored improvements to my CV, so that I can feel more confident when applying. It’s a small sentence, but it forces us to think about the who, what, and why in every feature. I came across this approach in Agile practices (first in Extreme Programming by Kent Beck and later made popular by Mike Cohn in User Stories Applied). Even years later, it still feels like a grounding reminder to focus on people, not just on processes or features. #ProductManagement #Agile #CustomerCentric

Test Driven Development (TDD) continues to spark intense debate in the software industry, but how well do we really understand its core principles and practical impact? Kent Beck's 2003 book laid out the famous red-green-refactor loop, promising benefits like better interfaces, fewer defects, and seamless code refactoring. Yet, upon closer inspection, many of these advantages aren't unique to TDD, and the process itself can introduce complexities and overhead — especially when applied without flexibility. From my own experience embracing agile development and various software testing methodologies, I've found that while TDD can improve design discipline and test coverage, it's not a silver bullet. The true value lies in understanding when and how to apply it thoughtfully rather than following rigid dogma. What has been your experience with TDD? Do you find it indispensable for code quality and agile workflows, or do you see it as one of many tools available? How do you balance test-first practices with practical development demands? I invite you to read a detailed review of Beck’s original TDD process and its implications in my latest blog post. Let's continue the conversation on effective software testing methodologies and evolving development strategies. Share your thoughts and stories in the comments—your insights are invaluable. #TestDrivenDevelopment #SoftwareTestingMethodologies #AgileDevelopment #CodeRefactoring https://lnkd.in/gqG4e44Z

Behavior-Driven Development (BDD) isn’t just about coding, it’s about collaboration. 🛠️🤝 By using shared examples, BDD helps developers, testers and business teams clarify requirements and stay aligned. BDD bridges the gap between business and tech. Are you practicing it? 🚀 #Agile #BDD #Collaboration #SoftwareDevelopment #TeamworkInTech #Steghub