Bridging the Gap: Creating Trust Between Non-Technical...
summary
Claims a measurable way to build stakeholder trust by shipping repeatable metrics: extracts accepted stories between Sprint start and end using the Pivotal Tracker API, pulls them into Google Sheets via Google Apps Script, tags work with labels to split line‑of‑business, computes points per Dev hour and short‑ and long‑term averages, and surfaces trends because Pivotal only keeps three months of history so exports matter. Delivers a plain Sprint email cadence — biweekly Sprint summary with context — to create transparency and accountability.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:09Why trust matters
- 7:19Competency vs character
- 11:12Trust-building behaviors
- 16:08Trust order
- 18:55Trust in meetings
- 23:48Data for stakeholder trust
- 35:04Summary
related talks
43mPredictable Delivery
40mAgile Software Development: Practice and Analytics
11mLeading Agile Teams to Success: Lessons from the Trenches
35mScrum Overview
01h 13m3... 2... 1... We Have Sprint-Off
26mVirtual Scrum
12mRebuilding trust & improving understanding between business & engineering
20mRefactoring Trust on Your Team