A guide to using a simple four-column Kanban board to organize work, reduce stress, and improve visibility for yourself and your team.
A developer shares their methodology of 'Notification-driven Development' to efficiently manage GitHub notifications and maintain multiple projects.
A software engineer's reflection on the challenges of switching between coding (IC) and management roles, and the impact on productivity.
A developer critiques the blind adoption of Scrum, arguing it's often misapplied and becomes a rigid, unproductive ritual rather than a useful framework.
A software engineer shares six practical strategies to prevent burnout, focusing on goal-setting, workload management, and self-care.
A guide to creating and sharing personal and team weekly digests to track work progress, increase visibility, and improve transparency in a tech workplace.
A tech manager argues that team problems are often human issues, not process flaws, using a PR example to advocate for direct communication.
Argues that product backlogs are harmful, never shrink, and proposes working without them for better productivity and team alignment.
A manager argues that effective management is crucial for keeping engineering teams focused on business goals and preventing technical rabbit holes.
Explores practical mechanisms like pilot/copilot roles and literature reviews to improve the success rate of machine learning projects.
Strategies for managing team dependencies in tech organizations when other teams can't provide support, focusing on understanding constraints and building trust.
A manager's role as a buffer, shielding their team from external pressures and internal stress to maintain focus and productivity.
Discusses the importance of managing a project backlog by closing out old, unrealistic issues to improve focus and efficiency.
Explores the role of courage in Agile software development for managing inherent project risks, using a hiking analogy to illustrate risk strategies.
A software engineer's perspective on the value and pitfalls of time estimations in software development projects.
A developer reflects on achieving high productivity and shipping speed in a small tech company with minimal process and no project managers.
A template for creating structured technical design documents to record decisions, scope, and solutions for software projects.
A satirical guide on how to misuse and distort the Scrum framework, leading to failure, to highlight common Agile anti-patterns.
Argues that Kanban is more adaptable and effective than Scrum for software teams, explaining how Kanban principles enhance responsiveness and decision-making.
Argues that deadlines harm software quality and morale, proposing 'preemption points' and queueing disciplines as better alternatives.
