• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Agile Buddha

Demystifying Agile, Getting to its Core

  • Our Blog – Agile Buddha
  • Agile Workshops and Certifications
  • Agile Commune – Join Here!
  • Webinars
  • Contact
  • About Us
  • Show Search
Hide Search

14 Years of Writing. One AI System. Here’s What It Found.

by ShriKant Vashishtha Leave a Comment

There is no shortage of articles telling you what RAG is.

This is not one of them.

This is what happens when you actually build one — over real content, with real questions, and an honest evaluation of what works and what does not.

What Is RAG and Why Should You Care?

RAG stands for Retrieval Augmented Generation.

The idea is simple. Before answering your question, the AI searches your documents, finds the most relevant pieces, and uses those to construct a grounded answer — not a generic one.

Think of it as the difference between asking a colleague who has read your internal policy documents versus asking someone who has only read the internet.

Most enterprise AI assistants being deployed right now use this approach. Internal knowledge bots, policy assistants, code documentation tools — RAG is underneath most of them.

What I Built

I wanted to understand what enterprises actually face when they deploy these systems. The only honest way to do that was to build one myself and stress-test it.

So I built a RAG system over 14 years of my own content — 111 blog posts from agilebuddha.in and my book on Agile estimation. Then I ran real questions against it and documented every failure.

The technology itself took eight focused sessions of 60-90 minutes each. It is not rocket science.

What came after building it — that is where it gets interesting.

What I Found

[Read more…] about 14 Years of Writing. One AI System. Here’s What It Found.

Your Team Got AI Tools. Why Isn’t Anything Moving?

by ShriKant Vashishtha Leave a Comment

I was recently working with a software team that just received AI coding tool licences, one for every developer on the team. Their leadership was excited. The CTO had made the call personally. AI-assisted development was going to change everything.

Sprint 1 ended. Not a single story was done.

Not in review. Not in testing. Not deployed. Done.

I want to tell you this had nothing to do with AI coding tool.

The team did not know how to use it well yet – that was true – but that was not the reason.

The real reason was that the constraint was somewhere else entirely.

[Read more…] about Your Team Got AI Tools. Why Isn’t Anything Moving?

Scrum Mythbusters : Sprint Backlog is Fixed During the Sprint!

by ShriKant Vashishtha Leave a Comment


A sprint in Scrum begins with a Sprint planning event in which Scrum team considers the Product Backlog Items (PBIs) from the top of the Product Backlog for the upcoming sprint.

The main activities of Sprint planning event are to:

  • select the PBIs the team forecasts it can deliver during the sprint
  • come to a consensus on a Sprint Goal
  • plan how to achieve the Sprint Goal

What is a Sprint Goal?

A Scrum team jointly commits to a short statement of the value it intends to deliver during the sprint. This is guided by the Product Owner. This becomes the focus of all work in the sprint and the team creates a Product Increment to meet the Sprint Goal.

Sprint Goal can be formed in many different ways.

[Read more…] about Scrum Mythbusters : Sprint Backlog is Fixed During the Sprint!

Introducing Mocktail: A Java Framework to Cache/Mock the External Dependency Response for Automated Tests

by ShriKant Vashishtha Leave a Comment

Most of the software applications use interfacing points, e.g. a database, XML datasource, or a restful service. Such interfacing points pose challenges while creating repeatable automated tests. The challenges are as follows:

Tests Become Flaky

Tests become flaky as they depend on the connection itself. If a database or a restful service is down, the tests dependent on them fail.

Tests that sometimes work and sometimes do not, break the trust of a team. Sometimes just because of that people stop paying attention to the test suite and may not fix them. After some time such tests become unmaintainable and people stop using them. As a result, the entire investment in creating such tests goes in a drain.

[Read more…] about Introducing Mocktail: A Java Framework to Cache/Mock the External Dependency Response for Automated Tests

When Story Point Estimation Doesn’t Work!

by ShriKant Vashishtha Leave a Comment

Story points are used to arrive at a shared understanding around a PBI. This works well when a team works collaboratively. Such teams take a PBI and swarm together to complete it. For instance, a front-end developer does her job, along with a designer and a back-end developer. In other similar scenarios, a team can have a mix of specialists and full-stack developers. These folks pair up and keep switching from one story to another as part of pair switching. 

In all these scenarios, having a shared understanding on a PBI helps. That’s the reason why planning poker and in turn story points work.

[Read more…] about When Story Point Estimation Doesn’t Work!

  • Page 1
  • Page 2
  • Page 3
  • Interim pages omitted …
  • Page 23
  • Go to Next Page »

Primary Sidebar

LikeBox

Tags

5 Whys Acceptance Criteria Adoption agile Agile Culture Agile Estimation Agile Offshore Agile Teams agile testing Agile Thinking Agile Transformation Agility Appraisals ATDD Automation Backlog Grooming BDD Big Picture business analyst Capacity Planning case-study code quality Collaboration Daily Scrum DevOps distributed agile Distributed Scrum Estimation Good Practices kanban kanban-mythbusters lean Metrics Planning Poker Prioritisation product owner Scrum ScrumMaster Sprint Sprint Demo Sprint Retrospective Story Point Story Points Sustainable Pace User Story

Categories

  • Agile
  • Agile Leadership
  • Agile Testing
  • Agile Transformation
  • AI
  • ATDD
  • BDD
  • Continuous Inspection
  • Culture
  • DevOps
  • Distributed Agile
  • Estimation
  • In Conversation with Tim Ottinger
  • Java
  • Jira
  • Kanban
  • Lean
  • noprojects
  • Patterns
  • Presentation
  • Product Owner
  • Scaled Agile
  • Scrum
  • Software Metrics
  • Testing
  • Testing Practices
  • User Story

Copyright © 2026 · Malonus Consulting LLP

  • Email
  • LinkedIn
  • Twitter
  • Facebook
  • Privacy Policy