The Delivery Manager Daily

🎧 Episode: The 30-Minute Delivery Health Check 🎙️ Delivery Manager Weekly with Mario De’CristofanoThink your delivery is going fine? Prove it — in 30 minutes.In this episode, Mario breaks down a tactical, time-boxed framework every Agile Delivery Manager should have in their toolkit. No fluff. No slide decks. Just a sharp, five-part diagnostic to assess flow, clarity, capacity, stakeholder engagement, and delivery readiness — fast.Perfect for retros, 1:1s, or crisis triage.🔍 You’ll learn:The five dimensions of delivery health that matterHow to extract risks, quick wins, and red flags fastWhen and how to run this check solo or with your team🧠 Includes a downloadable cheat sheet for immediate use.🎯 Diagnose first. Then deliver.Downloadable hereThanks for listening. Dont forget to subscribe & follow me on all the socials.

🎙️ Delivery Manager Weekly — Episode: Standardised Dev Environments in Sprint 0 Hosted by Mario De'CristofanoIn this episode, we dive into why setting up standardised development environments during Sprint 0 is a critical enabler for delivery success. Whether you're leading a new squad, onboarding engineers, or launching a greenfield build — this is foundational work that removes friction and sets the tone for engineering maturity.You’ll hear about:The purpose of Sprint 0Why “it works on my machine” is a symptom of a bigger issueTooling and automation that make setup fast and repeatableA practical checklist to use with your teams🔗 Connect with Mario De'Cristofano:Twitter/X: @mariodcLinkedIn: linkedin.com/in/mariodecristofanoGitHub: github.com/mariodcSubscribe, share, and leave a review — it helps others find the show. Catch you next week.

AI projects aren’t coming—they’re already here. Whether it’s chatbots, LLM integrations, or data-driven automation, Delivery Managers are being pulled into artificial intelligence delivery whether they’re ready or not.In this episode, Mario breaks down why AI projects are fundamentally different from traditional software builds, what new skills and frameworks are needed, and how Delivery Managers can take the lead in a landscape full of fuzzy scopes, probabilistic outputs, and ethical pitfalls.This is a practical, no-fluff briefing for anyone managing teams in the age of machine learning and GenAI.🔑 What You’ll Learn:Why AI projects behave differently than standard deliveryKey delivery risks unique to AI and MLWhat new roles you’ll find in cross-functional AI squadsHow to plan for iteration, uncertainty, and driftWhy ethical delivery and explainability matter📱 Connect with Mario De’Cristofano:LinkedInTwitter / XInstagramYouTubeWebsite💬 Have questions or ideas for the show? Send a message on LinkedIn or drop a voice note via the link in the show bio.🎧 Subscribe, share, and keep delivering.

Here's a podcast description that ties both topics together effectively:🎙 Episode Title: Delivering in Volatile Environments & White Privilege BiasIn today’s episode of The Delivery Manager Daily, we tackle two critical challenges in the world of Agile and IT leadership: navigating volatile delivery environments and understanding the impact of white privilege bias in decision-making.🔹 Delivering in Volatile Environments – Whether it’s market uncertainty, shifting stakeholder priorities, or unexpected team disruptions, delivery managers are constantly faced with turbulence. We’ll explore strategies for maintaining stability, adapting frameworks under pressure, and leading teams through unpredictable challenges without losing momentum.🔹 White Privilege Bias in Leadership & Delivery – Bias—whether conscious or unconscious—affects hiring, promotions, and team dynamics. We discuss how systemic privilege influences decision-making in the workplace, the hidden biases that shape delivery outcomes, and how leaders can actively foster more equitable environments.💡 Key Takeaways:✅ How to structure Agile teams for resilience in volatile conditions✅ The role of psychological safety in high-stakes deliveries✅ Recognizing and addressing privilege bias in leadership decisions✅ Practical steps for creating inclusive teams that thrive under pressure📢 Join the conversation and connect with me, Mario De’Cristofano, on:🔗 LinkedIn🔗 Twitter/X🔗 Instagram🔗 WebsiteSubscribe & leave a review—let’s challenge the status quo together! 🚀

🚀 New Episode Alert: The Cloud Exodus – Why Companies Are Moving Back On-Premise 🌍💻For years, the cloud was the promised land—scalable, flexible, and cost-effective. But now, the tide is turning. Organizations are reassessing their cloud-first strategies, moving critical workloads back on-premise. Why?In this episode of Delivery Manager Daily, we break down the key drivers behind this shift, including: ⚠️ Unpredictable Cloud Costs – Why “pay-as-you-go” is turning into “pay-more-than-you-planned.” 🔐 Security & Compliance Risks – Are cloud environments truly as secure as we thought? ⏳ Outages & Downtime – When your entire operation depends on a third party, how much control do you really have?Join me, Mario De’Cristofano, as we explore the reality behind this growing trend. Featuring expert insights and practical strategies, we’ll discuss whether on-premise is making a comeback—and what it means for agile delivery managers navigating this complex landscape.📢 Listen now on Spotify, Apple Podcasts, or wherever you get your podcasts. Don't miss this critical discussion! 🎙️ #DeliveryManagerDaily #CloudComputing #OnPremise #TechTrends

This episode is jam PACKED with information if your a new CS graduate, or wanting to get into the Digital Delivery Manager game in 2025, the things I would do if I were starting fresh. You may want to listen to the episodes below too, as they are all linked & I really hope you enjoy this one. Getting interviews for DM roles & how to do well (here)How to become a DM (here)The skills you need to be a DM (here)Take care

In this episode I wanted to talk about two things;Hybrid working - can you effectively do Scrum with new Scrum teams on new projects? This question came about after my talk at Keele, & I thought it was a great question & one which needed unpacking a bit.Running a good kick of meeting (or any meeting) Hands up how many meetings are you in that are an utter disaster? Try of course doing that hybrid or remote & you can be almost guaranteed to fail - I briefly explain the five things I do to help run the very best meetings.Step One: Know Your PurposeBefore you even send the invite, ask yourself: What is this meeting actually for? If your answer is "because we always do a kickoff,” start again.A great kickoff meeting does three things:It aligns the team on goals, scope, and approach.It builds relationships and sets expectations.It uncovers potential risks early.If your agenda isn’t doing these things, rethink it.Step Two: Get the Right People in the RoomOne of the worst mistakes? Inviting everyone because you don’t want anyone to feel left out. That’s how you end up with a meeting where half the people are checking emails and the other half are confused.Here’s who should be in the room:The key decision-makers—Product Owner, Delivery Manager, Tech Lead.The core delivery team—engineers, designers, testers, analysts.Key business stakeholders who need to understand the project direction.Anyone else? Optional or async. Keep it lean, keep it focused.Step Three: Set the Tone with Energy, Not SlidesNobody wants to sit through a 40-slide deck on “Why This Project is Important.” Instead, open with energy. Be clear, be concise.I like to start with three things:The Why: Why are we doing this project? Who does it benefit? Why does it matter?The What: What are we actually delivering? When? What does success look like?The How: How are we working? Agile? Scrum? Kanban? What’s expected of the team?If you can’t explain these things in under five minutes, your project is already in trouble.Step Four: Get People Talking—FastThe best kickoff meetings aren’t monologues, they’re conversations. Get the team talking as soon as possible.Here are a few great ways to do that:Ask the team: What excites you about this project? What concerns you?Run a mini Futurespective: If this project is a disaster in six months, why?Map out early risks and dependencies together.Engagement isn’t about hearing information, it’s about owning it.Step Five: End with Action, Not AbstractionA weak kickoff ends with “So yeah, let’s get started.” A strong kickoff ends with clear next steps.Summarize in three bullet points:What’s happening this week? (First sprint, onboarding, requirements deep-dive?)Who’s doing what? (Lead engineer setting up repos, BA refining backlog, etc.)What does success look like by next check-in?End with clarity. No open loops.

In this episode & accompanying blog post, I talk about why being too nice at work can be a problem, especially if you're an Agile leader (or leader of any description). As I've built up my leadership experience over the years to now consider myself 'not too shabby' I wanted to just pick at the edges of a few problems I see at work/client sites & what you can do about it to be better. As always thanks for listening.