Troubleshooting Agile Making Output Visible
Dec 4, 2019
Explore the fascinating difference between making work visible and showcasing your team's output. Discover how frequent demonstrations of results can build trust and align business and tech teams. Learn practical tips for engaging demos that highlight value to end users. Delve into maintaining a balance between imposed discipline and team autonomy, while focusing on system-wide output instead of local optimization. This insightful conversation unpacks how visible progress can transform relationships and drive success.
AI Snips
Chapters
Transcript
Episode notes
Visible Output Restores Trust
- Lack of visible output often signals low trust between business and technology.
- Making output visible regularly rebuilds trust and reduces suspicion about developer activity.
Demo Incremental Progress Weekly
- Show incremental progress frequently, even if it's a mock, API output, or UI change.
- Use demos as storytelling to explain what changed and why it matters to the business.
Show Customer-Meaningful Results
- Insist the team shows outcomes meaningful to customers or stakeholders, not only developer-facing artifacts.
- Aim for customer-visible progress every day and demos at least weekly to rebuild trust fast.