Thursday 14th August. XP Lean Coffee

[Leon Hewitt]

Here's your monthly reminder that we'll be gathering Thursday morning to drink coffee and chat all things XP.

Link: https://us06web.zoom.us/j/84091336753?pwd=U29CT1BBUHJaSGFHL01pK0dQcjhIdz09

Not sure what to expect, here's a summary of last month's meeting:

Team Morale and Code Quality
Many teams have been facing issues with code quality and testing, which led to critical questions from external stakeholders. Concerns were raised about the impact on morale. The group discussed approaches such as expressing appreciation, fostering a supportive culture, and shielding the team from outside criticism. Broader industry issues around professionalism and training were also noted, and the discussion ended with ideas for improving communication and protecting focus for process improvements.

Development Workflow

Difficulties with testing and deployment include separate processes for code and database changes, weak version control, and inconsistent environments. These problems caused late QA failures and accusations of inadequate testing. We suggested improving communication, celebrating small wins, demonstrating the value of test automation, and educating management on software complexity.

Fixed Scope and Priorities
A challenging project with fixed scope and tight deadlines was discussed. We agreed that scope was rarely truly fixed and advised focusing on the most valuable outcomes. Suggestions included assigning senior staff to critical tasks, prioritizing deliverables with the highest stakeholder value, and completing one major goal exceptionally well to build confidence.

Product Prioritization and Accountability
We observed there was a lack of clear accountability for product prioritization, which allowed both technical and business teams to deflect responsibility. The product owner’s limited experience was noted, and it was agreed they should remain accountable for backlog priorities and executive communication, potentially supported by value-based assessment methods.

Beyond Monetary Value in Prioritization
Can product teams rely solely on monetary value for prioritizing work? While useful for cost-saving initiatives, it was seen as less effective for new revenue streams or complex strategic choices. Involving subject matter experts was recommended for more balanced decision-making.

Developer Learning Culture
Formal training was seen as less effective than fostering a culture that encouraged self-driven growth. Mixed results had been observed from providing learning budgets and time. Attendance at internal knowledge-sharing events had declined, possibly due to a smaller proportion of engaged developers or economic pressures placing many in “survival mode.”