September 2022 Summaries

People management involves recruiting, training, engaging, and retaining employees to optimize their productivity, a task that becomes complex as team size increases. Effective people management requires addressing team capacity, onboarding, training, mentorship, and fostering a positive work culture, while also dealing with the challenges of synchronization costs, which arise when individual team members interpret tasks differently. Pair programming is proposed as a solution to these challenges, as it encourages collaboration, reduces synchronization costs, enhances team performance, and improves product quality by having two developers work together on tasks, thereby facilitating continuous feedback and reducing conflicts. Studies support the effectiveness of pair programming, showing it enhances design quality, reduces defects, and improves team communication, making it a valuable approach for managing larger teams and promoting a collaborative engineering culture.

Smaller team sizes are linked to higher quality and better performance in terms of schedule and cost/effort, with studies indicating that teams of 3 or fewer members often achieve optimal outcomes. This is due to minimized communication paths, limited productivity gains from parallelized work, and increasing management complexity with larger teams. Amdahl's law explains that there is a cap on speed improvements from parallel work due to necessary synchronization, which can decrease delivery time. The Kanban method's Work In Progress (WIP) limits align with this concept, suggesting that restricting parallel tasks to 6-7 items can enhance delivery speed. By combining Kanban's principles with Amdahl's law, it's suggested that teams should focus on reducing parallel work and maximizing task execution speed to deliver value efficiently.

A recent update has revamped the sidebar Wizard, making it more user-friendly and functional by integrating test case navigation and execution within the Run Dashboard itself, eliminating the need for a separate modal window. The sidebar now displays test case results, aligning with the platform's updated UI, and allows users to manage defects efficiently by toggling between creating new defects or linking existing ones. Several bugs have been addressed, including issues with Redmine projects and fields, task ordering in exports, errors in large projects, API token access for deactivated or read-only accounts, and Slack app settings. Additional improvements include consistent icon colors, enhanced export options, and improved custom widget functionality for project distribution.

Achieving overlapping team knowledge requires a supportive environment that encourages collaboration and learning without the pressure of individual performance metrics or stress, which can hinder educational progress. Engineering Managers (EMs) should focus on fostering a culture where team members feel safe to express vulnerabilities and learn from each other, rather than concentrating solely on individual performance and time utilization. Neuroscientific research highlights the negative impact of stress on learning, emphasizing the need for designated learning times free from work pressures. EMs should lead by example, admitting their own gaps in knowledge to inspire team openness and growth. A safe environment devoid of competitive grading systems, flexible growth plans tailored to individual strengths, and opportunities for team members to showcase new skills through voluntary presentations can help cultivate a community eager to learn and share knowledge.

The discussion explores the detrimental effects of time pressure on developers, such as reduced quality, creativity, and mental health, and questions the necessity of imposing deadlines and estimations in project management. While acknowledging that certain scenarios, like public tenders, require estimations due to external constraints, the text argues that many internal pressures for deadlines are irrational and often stem from a lack of collaboration or poor forecasting abilities. The reliance on estimations is scrutinized, with examples illustrating how inaccurate predictions can lead to misguided decision-making. The text suggests that instead of focusing on precise time estimates, teams should aim for value-driven goals and consider alternative frameworks like Kanban's statistical forecasting to manage workflows without imposing stress. It also recommends exploring the #NoEstimates approach to achieve objectives without enforcing rigid time constraints on developers.