My experience speaking at the Panel Event LeadDev Amsterdam

AI is changing how we build software. But are we changing how we lead teams? 🤖🚀

What a fantastic evening at the LeadDev Amsterdam Meetup, hosted at Adyen!

I had the pleasure of being a panelist for “Building Self-Sufficient Teams in the AI Era”, alongside an incredible group of fellow engineering leaders: Oleksandr Tryshchenko, Olaf de Ruiter, and Vanessa Ho.

We explored some thought-provoking questions:

💡 How is AI-assisted engineering changing roles and responsibilities within teams?

🤝 What does the evolving role of Agile leaders look like in this new era?

🔍 Are PR reviews becoming bottlenecks to team autonomy? How do we maintain code quality while moving faster?

🌱 How do we mentor junior developers who are entering a world where prompting is becoming as important as writing code?

⚖️ And perhaps most importantly, how do we give teams the freedom to experiment, learn from mistakes, and grow when AI accelerates everything?

The best part was the energy in the room – the interactive questions, diverse perspectives, and honest discussions that kept the conversation going beyond the panel.

One thought I took away: AI may accelerate how teams work, but building trust, ownership, critical thinking, and a culture of learning remains very human work.

A big thank-you to the @LeadDev team for bringing us together, Adyen for hosting us, my wonderful co-panelists for the stimulating discussion, and everyone in the audience who contributed to such an engaging evening.

Already looking forward to the next conversation! 💜

#LeadDev #EngineeringLeadership #AI #AgileLeadership #SelfSufficientTeams #FutureOfWork #SoftwareEngineering #TeamAutonomy #ContinuousLearning #Leadership

That’s What She Said!

What happens when you bring incredible women, honest conversations, and improv comedy into one room? ✨ A whole lot of connection, inspiration, and laughter! 🔅

Yesterday, I attended “That’s What She Said” at Boom Chicago in Amsterdam – and what a refreshing evening it was! It was so much more than networking. 🤝

💫 I met amazing women from so many walks of life, each with their own stories, career journeys, ambitions, challenges, and perspectives.
🦋 We talked about work, life, taking risks, navigating careers, and everything in between. It was wonderful to connect beyond job titles and professional profiles and simply share our experiences as women.

And then came the comedy! 😆 A huge shout-out to the incredible all-women improv comedy cast at Boom Chicago for turning relatable experiences and unspoken workplace realities into such a hilarious performance. You had us laughing while recognising just how familiar some of those situations can be!

🍀 A heartfelt thank-you to Yoana Leusin and the impowr team for bringing this wonderful experience together. ❤️ & to all the amazing ladies I met there – thanks for bringing your authentic selves!

🤗 My biggest takeaway? Sometimes the best professional connections happen when we step away from formal networking, show up as ourselves, listen to each other’s stories, and have a really good laugh.

🥂 Here’s to more spaces where women can connect, support one another, share openly, and celebrate each other – with a little humour along the way! 🤩

Certified! PSM- AI Essentials

Agile leadership is evolving. Are we evolving with it? 🤖🚀


Happy to share that I’ve earned my Professional Scrum Master™ – AI Essentials (PSM-AI Essentials) certification from Scrum.org! 🎉


With AI reshaping how we work, collaborate, and deliver value, I believe the opportunity for Scrum Masters and Agile leaders goes far beyond simply adopting new tools.


It’s about asking the right questions:
💡 How can AI help us facilitate more effective Scrum events?
🤝 How can we strengthen team collaboration and decision-making?
🚀 How can we use AI to empower teams rather than replace human judgment?
🔐 And how do we ensure we adopt it responsibly and ethically?

For me, this certification is another step in my continuous learning journey – exploring how we can combine Agile principles, human-centered leadership, and AI to build stronger, more effective teams.


Because the goal isn’t to use AI just because it’s available. It’s to use it thoughtfully, where it creates real value.


Excited to keep learning, experimenting, and bringing these insights into practice!


#Scrum #AgileLeadership #ArtificialIntelligence #ScrumMaster #ScrumOrg #ContinuousLearning #FutureOfWork #AIEssentials

My Experience at ‘Unmute’ – A Retreat for Women Ready to Lead with Confidence & Presence

Sometimes leadership isn’t about finding your voice.
It’s about giving yourself permission to use it. 💫



I recently spent two days at Unmute – a Retreat for Women Ready to Lead with Confidence and Presence – and I came away with so much more than I expected!

The biggest highlight?
The women. ❤️

An incredible group of women, each brilliant in her own way, each at a different point in her journey – exploring leadership, boundaries, clarity, purpose, confidence, identity and simply… becoming more of who they are.

We talked. We laughed. We reflected… and We Unmuted parts of our own selves in different ways.



🦋 We explored somatic practices, guided exercises, self-reflection and some wonderfully honest conversations. And there was something powerful about being in a room where people could put their professional titles aside and simply show up as themselves.



🦄 It reminded me that leadership development isn’t always about acquiring another skill or learning another framework.
Sometimes it’s about:
✨ trusting yourself a little more
✨ understanding what you truly need
✨ setting boundaries without guilt
✨ finding the courage to speak up
✨ and creating enough space to hear your own voice



A huge thank you to Alicia Ingruber and Amanda Gandolpho for creating such a thoughtful and welcoming space. The intention, energy and care behind Unmute really came through. 💜

I left feeling inspired, connected and reminded that the strongest leadership often begins with the relationship we have with ourselves.
Definitely looking forward to joining future events and continuing these conversations.
Sharing a few glimpses from the experience. 📸

Thrilled to see my name in print — in German!

Thrilled to see my name in print — in German!! 🇩🇪📖

When I first wrote this article on Continuous Testing in Agile—highlighting the need to balance speed with quality, and keep the “wheels of testing” running—I had no idea it would travel this far.
But today, I’m proud to share that my work has been published in the print edition of Entwickler.de, one of Germany’s most respected tech magazines! 🎉

Originally written in English and translated by the amazing editorial team, the article is titled:
🔍 “Die Räder des Testens am Laufen halten”
(“Keeping the Wheels of Testing Running”)
— and dives deep into how Agile teams can stay efficient and resilient with continuous testing strategies, even in fast-paced delivery cycles.

🧪 From quality thinking to adaptive test environments, the article covers the mindset and methods teams need to deliver great software, consistently.

💜 A big thank you to the Entwickler.de team for beautifully presenting the article and sending me a print copy that I’ll treasure.
🙏 And a warm shoutout to the Devmio team as well for our collaboration and continued support in sharing meaningful conversations around DevOps and Quality at Scale.

Here’s to celebrating small wins, sharing knowledge, and seeing our ideas come to life across borders and languages! 🌍✍️

📖 Read the article here:
👉 https://entwickler.de/testing/die-rader-des-testens-am-laufen-halten-002

#ProudMoment #ContinuousTesting #AgileQuality #DevOps #EntwicklerDe #AgileTesting #TechWriting #DevOpsCon #WomenInTech #TestAutomation #QualityAtScale #KnowledgeSharing #AgileLeadership #PublishedAuthor #FromIdeaToPrint

From Team to True Squad: Building Synergy in Scrum

I’m excited to share my latest article, “From Team to True Squad: Building Synergy in Scrum,” recently published on Devm.io!

We often hear about the importance of teamwork when we talk about agile and Scrum in particular. But there’s a massive difference between a group of individuals that work together and a squad that truly clicks. Building a high-performing Scrum team is less about following rigid frameworks and more about nurturing relationships, creating trust and creating a shared vision & sense of purpose. What truly elevates a group of individuals into a high-performing squad is synergy—that magical cohesion where the whole is greater than the sum of its parts.

Key Insights from the Article

🔹 Continuous Improvement: Agile squads thrive when retrospectives are used not just as a ritual but as a powerful tool for learning and growth. The key is to focus on actionable feedback, addressing both the wins and the pain points. Improvement isn’t a one-time event; it’s a mindset that fosters resilience and adaptability.

🔹 Alignment with Autonomy: Balancing squad goals with overarching organizational objectives can be tricky, but it’s essential. Alignment ensures that the team delivers value, while autonomy empowers them to decide how to deliver it, fueling innovation and ownership.

🔹 The Role of Trust: A true squad is built on a foundation of trust. When team members trust each other, they feel safe to share ideas, challenge norms, and admit mistakes—without fear of blame or judgment. This psychological safety is the bedrock of creativity, collaboration, and continuous improvement. Leaders must actively foster trust by encouraging open dialogue, leading by example, and celebrating team wins.

🔹 Fostering Synergy: Building synergy means creating an environment where collaboration isn’t just encouraged—it’s ingrained in the squad’s DNA. This involves clear communication, shared accountability, and a shared vision of success.

Why It Matters

Agile is more than a process; it’s a way of thinking. When squads embody these principles, they don’t just deliver—they innovate, inspire, and transform.

📖 Read the full article here: From Team to True Squad: Building Synergy in Scrum

I’d love to hear your thoughts:

  • How do you foster trust within your teams?
  • What strategies have helped your squads achieve true synergy?

Let’s discuss and share ideas!

#AgileLeadership #TeamSynergy #ScrumMastery #TrustInTeams #ContinuousImprovement #AgileSquads #LeadershipMatters #DevOps

Shipping Daily : From Sprints to Continuous Releases

DevOps Teams that achieve daily releases have mastered a unique set of skills and practices to ship software faster and more frequently, with higher confidence. This high frequency release model differs significantly from the traditional Scrum framework with 2-week sprints (or longer). 

I wrote about this recently in my article published at devm.io platform , where I discussed the daily routines, processes and tools that support these teams, while contrasting them with more familiar cadence of traditional scrum teams. For teams and organizations looking to move towards daily releases, I also covered the key adjustments required to turn this vision into reality.

The Daily Rhythm: Planning, Execution, and Monitoring

1. Planning

For teams delivering code daily, the rhythm of planning, execution and monitoring does not follow the two-week sprint cycle but happens continuously. Here is what this daily rhythm looks like:

  • Frequent Prioritization: Daily release teams prioritize their work each day, selecting high impact tasks that can be completed and shipped within a single day.
  • Dynamic Backlogs: Instead of working with a static sprint backlog which is derived from the mammoth product backlog, these teams operate with highly flexible backlogs – adding things to it every day. They are ready to pivot quickly in response to customer feedback or issues, urgent needs or new business opportunities.
  • Smaller Targeted Tasks: Work items are broken into small, manageable pieces – each designed to be completed within hours. User stories and tasks are refined to be achievable in less than a day, keeping workloads manageable and ensuring that work completed aligns with daily release goals.

2. Execution

Unlike Scrum teams that often release at the end of a sprint, daily release teams execute work with a focus on immediate delivery.

  • Incremental Work: Instead of waiting until the end of a sprint, developers push small, frequent changes every day. Every code change is designed to be testable and deployable at the end of the day.
  • Automated Testing: It is critical to daily releases. CI pipelines are designed to run tests on each code change, ensuring stability and reliability and readiness of production.
  • Seamless Deployment: CD pipelines are in place, so that the code – once tested – is deployed automatically to production. With daily releases, teams cannot afford to spend hours on deployment activity every single day – so it is imperative to automate it.

3. Monitoring

  • Automated Monitoring: Monitoring tools track deployment success, system performance, and error rates in real time. Tools like Datadog, New Relic, or Prometheus help track application performance, error rates and system health. These tools are crucial for catching issues early and preventing them from impacting users.
  • Daily Retrospective Feedback Loops: Instead of waiting until the end of a sprint, the team reviews their daily progress and identifies immediate improvements – leading to quick adjustments.

Read the full article here for details on :

Normal Scrum vs Daily Release : Key Differences

Practices to Support Daily Releases

Key Metrics to Track

When are Daily Releases Appropriate?

Benefits of Daily Releases

Agile Metrics that Matter: Measuring Success in Software Delivery

In the world of software delivery, the agile approach has transformed the way teams work, adapt and succeed. Agile is all about delivering value quickly and iteratively, but how do we know our team is succeeding at that? The answer will lie in the metrics we track.

I tried to answer this in my article that was published on devm.io platform recently.

Why Metrics Matter in Agile

Agile metrics provide valuable insights into:

  • the health of our processes,
  • helping us make informed decisions,
  • identifying areas of improvement and, eventually,
  • delivering better software.

Before we get into specific metrics, it is important to understand why tracking metrics is crucial in agile development.

Agile thrives on feedback – whether it is from users, stakeholder, or the development process itself. Metrics provide that feedback, helping teams understand where they stand and where they need to go.

Metrics help us answer critical questions:

  • Are we delivering value quickly enough?
  • Are we maintaining quality as we move fast?
  • Are our customers satisfied with the product?
  • Where are the bottlenecks in our process?

Without metrics, these questions are left to guesswork.

With metrics, you have data-driven insights that guide decision-making, foster continuous improvement and ensure alignment with business goals.

Let us explore the key metrics that agile teams should track to measure success in software delivery.

1. Lead Time and Cycle Time

Lead time is the time taken for a piece of work from request to delivery. It includes everything from the requirement coming in, to the idea generation, coding, testing & deployment.

Cycle time is the time it takes to complete a specific task or user story from the moment work starts on it to when it is finished. Unlike lead time, cycle time doesn’t include the time spent in backlog or waiting for the work to start.

In agile, the goal is to deliver value quickly & frequently. Lead time tells you how quickly your team can turn ideas into working functionality. Shorter lead time would indicate a more efficient process and better response to market changes.

Cycle time helps you understand the efficiency of your team’s workflow, and how long it takes to deliver a piece of work once it is in progress. Shorter cycle times mean that the team is working efficiently and can handle more tasks within a sprint.

—- Follow the link to read further —–

https://devm.io/agile/agile-metrics-software-delivery-analyze

About devmio

devmio is an IT and Tech conference platform that goes beyond the conference room. Join live events, read magazines and articles from the IT experts you know and love! You can join the live events to chat with experts, read magazines written by experts and attend conferences with exclusive discounts all accessible with their Fullstack Experience membership. Join here -> https://devm.io/

New Country. New Life. Same Drive for Growth. 🌍🚀

A Life Update!


A few weeks ago, I took one of the biggest leaps of my life—I moved to a new country.

Hello, Netherlands!

This journey has been nothing short of transformative. From navigating unfamiliar streets to trying to learning a new language, looking for a home, and finding my rhythm in a completely new environment—every day continues to bring its own set of challenges and lessons.

But with every challenge comes growth. 🌱

Moving to a new country isn’t just about geography—it’s about rediscovering yourself, stepping out of your comfort zone, and embracing the unknown. it is not easy to wrap up a life you’ve known forever and built for yourself, and just leave with a few suitcases and heaps of memories – in search for something that is calling for you from hundreds of miles away…. But when were we ever made for ‘easy’ things? After all —

“A ship in harbor is safe, but that is not what ships are built for.” – John A. Shedd

It’s about giving up the comfort and luxury of every ‘known’ , and starting from ground up.

It’s all about learning to adapt, staying resilient, and building connections that make the transition easier.

It is about being Agile!

As an experienced Agile professional with a passion for driving team success, collaboration, and continuous improvement, I’m now actively looking for my next career opportunity in this incredible city.

📢 To my fellow #Agile practitioners, leaders, scrum masters and #QAprofessionals in #Amsterdam:
If you’re part of this vibrant tech and Agile ecosystem, let’s connect! I’m eager to bring my experience in Agile coaching, leadership, and transformation to a team that values collaboration, innovation, and growth.

This is more than just a professional journey—it’s a personal one. And I’d love to connect with people who share similar values and can guide, mentor, or simply share a coffee and a conversation. ☕

To anyone else considering taking a big step like this—trust the process. It’s not easy, but it’s worth it.

Here’s to new beginnings, endless possibilities, and the courage to create a life you truly love!🌟

Cheers,

Nishi

Confronting Technical Debt: Making the Case for Investment in Long-Term Quality

Technical debt is like the credit card debt of the software world – easy to accumulate but expensive to pay off if not managed. Technical debt occurs when shortcuts are taken during the development process, often to meet tight deadlines or push out new features quickly. With agile’s fast pace, it is easy to accumulate technical debt, justifying it as the need of the hour and need of the market. But just like credit card debt, the interest from technical debt compounds over time, making future changes harder, more expensive and riskier. The question many development teams face is how to convince the leadership to invest in resolving technical debt, even when everything seems to be working fine on the surface.

I recently wrote this article for the devm.io platform where I explore effective strategies for communicating the hidden costs of technical debt, demonstrating its impact on innovation, and making a compelling case for prioritizing it – even if it means temporarily slowing down feature delivery. By understanding and articulating the true risks of technical debt, you can help your team invest in long term health and scalability of your product.

The Hidden Costs of Technical Debt

Many teams struggle with increasing time to production, decreasing velocity sprint-after-sprint and it might begin to seem like the team’s productivity is decreasing over time. The most dangerous aspect of technical debt is its impact on your team’s ability to innovate and scale. At first glance, technical debt may not seem like a pressing issue – since the software is running smoothly and features are being delivered. The problem is that technical debt accumulates gradually and its effects remain hidden until they reach a tipping point.

Every shortcut taken, like skipping tests, avoiding refactoring, hardcoding solutions or neglecting peer reviews – creates complexity in your codebase. As this complexity builds up, it slows down your development process, increases the likelihood of issues, makes future enhancements more difficult and time consuming.

Not only this, there may be instances when these skipped actions are actually mandatorily needed for certain regulations, contracts or standards that we adhere to. This means the team would end up having to do them later, spending more time and causing delays in our project completion.

To read the complete article, visit the devm.io platform

<My article published at devm.io platform: https://devm.io/agile/technical-debt-costs-strategies>