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.
A software development analogy comparing building a house to building websites, emphasizing the need for upfront planning for accessibility and performance.
A developer analyzes the costly mistakes behind his $46k website redesign, offering lessons on project management and hiring.
A senior engineer discusses taking on product management duties to fill a gap, arguing that initiative and leadership are key at higher levels.
A data scientist shares a structured approach to starting data science projects, focusing on business goals, requirements, and avoiding common pitfalls.
A developer discusses balancing project deadlines with the long-term benefits of improving processes and automating tasks, using examples like PowerShell scripts and cloud services.
A developer's personal recap of blog posts written for their employer's tech blog and side projects, including Slack guides, web development, and open-source contributions.
A developer reflects on their first year of self-employment, sharing insights on productivity, motivation, and the transition from hobby coding to full-time work.
The author argues for the importance of increasing productivity and velocity, countering common objections and using a personal project as an example.
A programmer shares his method for providing realistic project estimates by multiplying optimistic timelines and using ranges to account for unforeseen changes.
Article argues that motivating software developers requires belief in the project's purpose, not just financial incentives, and discusses key management principles.
A developer explains how 'Yak Shaving'—the process of tackling tangential tasks—can be a positive motivation for starting and improving open source projects.
Introduces the Nijute concept: Not Impossible, Just Too Expensive, a mental model for reframing 'impossible' tech problems as solvable cost/constraint issues.
