Showing posts with label Software Development. Show all posts
Showing posts with label Software Development. Show all posts

Sunday, May 17, 2026

The AI Engagement Lifecycle with Endava, Dava.X.AI, and Miro


Endava set out to reinvent how IT services get delivered in an AI-native world. Dava.X.AI is the group inside Endava driving that shift. Miro is the workspace they're building it on. Together they've shipped Davaflow — an AI engagement lifecycle that runs from signal to explore to govern to evolve, with humans and agents working alongside each other the whole way.


Takeaways

Reframe from value capture to value creation — don't use AI to make existing processes 10–15% better, reimagine the work entirely from an AI-first perspective.

IT services hit its "ChatGPT moment" two years ago when clients and analysts started asking Endava why they were needed if AI could just write the code.

AI is becoming a method, not a tool — just as Agile organized humans to do work, this new method organizes agents and the people working alongside them.

The technology question is largely settled; the change management question isn't — quality has hit the inflection point, and what remains is the human shift, much like Waterfall-to-Agile.

DavaFlow runs in four phases — Signal, Explore, Govern, and Evolve — moving from identifying the right problem, through virtual personas and prototypes, to governing agent output, to evolving in production.

Chat is the wrong interface for most of this work — humans are visual creatures, and tools like Miro give LLMs context that a chat box never could.

AI-driven work can produce better traceability than humans ever did — every decision and prototype connects back through the chain of thought, what Joe called "traceability on steroids."

Anyone can buy the tools — what separates enterprise work from vibe-coding chaos is policy-as-code, defined skills, and human-in-the-loop checkpoints.

Adoption happens in baby steps, not the full vision — showing people the end of the journey overwhelms them, so start at signal and layer in each next step.

The hardest part is the identity question — engineers liked writing code and designers liked crafting prototypes, and the shift is a growth-mindset problem, not a skills problem.


Links from the Podcast


Upcoming Miro Canvas Events


Contacting the Guests



Chapters

00:00 Introduction to Endava and AI Transformation

08:54 Navigating the AI Landscape: Challenges and Opportunities

17:52 The Evolution of Miro and AI Integration

24:00 Dava Flow: The AI Engagement Lifecycle

25:49 The Power of Visual Context in AI

27:03 Enhancing Contextual Understanding with AI

29:12 Temporal Dimensions in Decision Making

31:27 Navigating Change in Organizational Mindsets

35:40 Demonstrating Value to the C-Suite

38:13 Embracing the Future of Work

41:09 Amplifying Human Creativity with AI


Wednesday, October 20, 2021

What Do We Do With The QA Manager? w/ Joel Norman


Joel Norman is joining me for this episode to respond to a question I got in class recently about what happens to the role of QA Manager once all the QA folks have joined teams. Do we still need someone to manage QA if everyone in QA is part of a cross-functional, self-organizing team? If the answer is yes, what do they do day-to-day? If the answer is no, who is going to advocate for things like continuous integration across all the development teams?

You can find the podcast here.

Wednesday, October 25, 2017

Reframing Technical Debt as Technical Health - with Declan Whelan

In this interview Agile Alliance Board Member Declan Whelan makes the case for reframing Technical Debt and having organizations develop practices and programs supporting Technical Health. During the interview we discuss what technical debt it, how our perception of it has evolved and why taking a more positive and proactive stance for it can be so beneficial for organizations that are trying to improve flow and remain competitive in the marketplace.

Declan also shares details on the Agile Alliance’s OnAgile 2017 virtual conference which is taking place on October 25, 2017.



SHOW NOTES

00:09 Interview Begins
00:36 Background on Declan
02:35 What is Technical Debt?
03:55 How the definition of Technical Debt has evolved
05:11 Impediments to flow
06:15 Why it makes sense to think of Technical Debt as Technical Health
09:42 How does technical debt happen?
11:15 The environment (or system) may be set up to support increased technical debt
13:12 Explaining to management why technical wellness is so important
14:26 Measuring technical health (and debt)
15:58 Explaining the debt in dollars and showing the value of investing in technical health
16:22 How much faster could you go?
17:25 Why Declan enjoys legacy code and why some folks get frustrated with it
19:00 Finding the right people to work on it
20:16 Should technical debt go in the Product Backlog?
20:55 Employing the Boy Scout rule
24:25 Does Leadership and the PMO understand the importance of dealing with technical debt?
26:00 How the PMO can have a positive impact on technical wellness
30:55 OnAgile 2017 - the Online Conference (10/25)
30:04 What is Psychlomatic Complexity?
34:16 The things in Agile that Declan is focusing on learning about 
36:00 Contacting Declan

OnAgile 2017


CONTACTING DECLAN