Skip to content
~/sph.sh

team-management

13 posts

team-management
Who Owns This Code Now: Accountability vs Blame

Stop asking who wrote the legacy code. Separate responsibility, accountability, and blame, and make inherited code owned rather than orphaned.

engineering-culture · leadership · team-management +3

Engineering Team Documentation: Working Agreements, Definition of Done, and On-Call Docs

The team documents a mature engineering team owns: onboarding, working agreements, Definition of Done, on-call, knowledge transfer, and what makes each one good.

engineering-culture · hiring · documentation +4

Scrum vs Kanban vs Scrumban for AI-Assisted Teams

AI absorbs more of the implementation, so the framework name matters less than four feedback loops. A decision lens for tuning flow, cadence, WIP, and review.

leadership · agile · team-management +3

Role Expectations in Software Teams: RACI and DACI Frameworks

Unclear ownership stalls software delivery. How RACI and DACI assign decision rights, where each one fits, and the pitfalls that kill adoption.

team-management · engineering-management · productivity +2

The Hidden Cost of Cultural Blindness: When Global Engineering Teams Fail

Cultural misunderstandings quietly derail global engineering teams; practical frameworks for adapting feedback, meetings and escalation to cultural context.

leadership · team-management · remote-work +2

RACI and DACI for Software Teams: Fixing Role Ambiguity

Unclear role expectations quietly drain software team productivity; here are proven RACI, swim-lane, and escalation frameworks to remove the waste and lift performance.

leadership · team-management · best-practices +4

Working with Difficult Coworkers in Software Teams: Beyond Textbook Solutions

A field guide to engineering-specific difficult coworkers, from code-review blockers to ghost colleagues, with practical strategies that work for each archetype.

leadership · team-management · best-practices +5

Team Conflict Resolution: A Field Guide to Turning Dysfunction into High Performance

A field guide to spotting, managing, and resolving conflict in software teams, with practical frameworks and early-warning systems that turn friction into performance.

leadership · team-management · best-practices +4

GitHub Copilot ROI: An Enterprise Cost Analysis Framework

How to model GitHub Copilot ROI at enterprise scale: the license and review cost lines, the metrics that matter, payback shape by team size, and rollout anti-patterns.

github-copilot · ai-tools · productivity +7

Lewis Deep Democracy in Engineering Teams: Beyond False Consensus

How Arnold Mindell's Deep Democracy principles transform technical decision-making, build psychological safety, and ensure every voice strengthens architecture.

psychological-safety · team-management · team-dynamics +4

Bus Factor in Engineering Teams: How to Reduce Knowledge Risk

Protect your team from single points of failure through knowledge distribution, documentation strategies, and systematic risk management.

team-management · documentation · knowledge-sharing +5

Documentation as Infrastructure: Scaling Knowledge Across Engineering Teams

Documentation debt can slow teams faster than technical debt. A guide to treating docs as critical infrastructure and scaling knowledge across engineering teams.

documentation · rfc · team-management +3

Git Branching Strategies: Real-World Lessons for Different Teams and Products

Git branching strategies mapped to team size, product type, and release cadence. GitHub Flow is the default; here is when another model earns its overhead.

ci-cd · lessons-learned · team-management +3