How to effectively communicate to Developers/PMs - A guide for developers and project managers
summary
Developers lose ~20 minutes after an interruption and prefer asynchronous check-ins: put status and updates in JIRA, ping on Slack and wait for a reply, and respect headphones as do not interrupt. Team uses github, Travis, Talia, Agile and test‑driven practices; they run short retros and trimmed backlog grooming, demo each sprint, and expect clear tickets. Estimates often miss unknowns—practical rule: triple developer estimate—and refactoring or contributing back to core must be scheduled, not sprung on the sprint.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 4:19Who is Manny
- 6:33How many PMs
- 6:55Myths
- 8:16Complaints
- 10:32What PMS do
- 16:05What works for us
- 18:12Testing
- 18:58Ticket Status
- 20:28What does your mom say
- 23:02Estimates
- 24:35Team Effort
- 27:22Expectations
- 28:52Happy Medium
- 30:30Magic Secular Expectations
- 31:38Integration
- 33:00Team
related talks
48mCommunication for Developers
26mEnhance Developer Experience by community
51m"Time Management for Developers"
47mCommunication for Developers: estimates, code reviews, and other hard problems
40mAgile Software Development: Practice and Analytics
41mProduct Owner & Developer: An Unexpected Journey
34mBuilding a Culture For Developer Productivity
46mCracking the cadence of your software engineering 1:1s