Fragile Agile: Continuing the Humdrum Scrum Series
Welcome to Part 2 of our three-part series on Humdrum Scrum, where we explore common issues companies face in agile deployments. In the series, we delve into issues and antipatterns for organizations that have transitioned to agile and offer suggestions and remedies to transform the crumbs of humdrum into substantial savings of time and funds. If you missed it, be sure to read Part 1 to catch up on the first set of challenges and insights. Part 3 is up next, where we will conclude our series with more reflections and actionable strategies to enhance your agile practices.
Issue 4: Hot Potato (Handoffs Over Cross-Functional Collaboration)
In many organizations, a pervasive “hot potato” mentality persists where specialists within a development assembly line are eager to pass tasks along to the next person once their specific, isolated contribution has been completed. This sequential handoff process, while straightforward and simple, often leads to inefficiencies and a lack of ownership over the final product. 
Team members wait for the work to come to them, completes their portion, and quickly pass it off, missing opportunities for holistic improvement and innovation. This siloed approach may get the job done, but it squanders the potential for cross-functional collaboration that could enhance both the product quality and process efficiency.
- Encourage Team Integration: Break down silos by encouraging teams to work in integrated cross-functional groups that share responsibilities and insights throughout the product development lifecycle.
- Implement Pair Programming or Mob Programming: These methodologies not only improve code quality but also enhance team knowledge and cohesion by having multiple people work on the same task simultaneously.
- Regular Cross-Functional Meetings: Hold regular meetings that involve members from different stages of the development process to discuss ongoing projects, share challenges, and explore solutions collaboratively.
- Incentivize Collaborative Success: Redefine success metrics to include team-based achievements and collaborative efforts rather than individual accomplishments. Reward teams for collective output and innovation rather than speed of individual task completion.
Issue 5: This Isn’t What I Ordered (Result Differs from the Need)
In the race to deliver products swiftly, a critical gap often emerges between what is built and what users actually want or need. This disconnect arises when product designers and analysts define requirements based on their interpretations rather than direct input from end-users. Developers, pressured by deadlines, forge ahead without securing user signoff—viewed as a time-consuming hurdle rather than an integral part of the process. Consequently, the final product may fail to meet user expectations, rendering it unusable without costly and time-consuming rework. Ironically, the time believed saved by bypassing user engagement is often lost to modifications post-delivery, at a much greater expense.
- Incorporate User Feedback Early and Often: Engage with actual users from the initial stages of product development and continue this engagement throughout the project. Create prototypes and minimum viable products (MVPs) to gather feedback early and iteratively refine the product based on real user input.
- Adopt Agile Feedback Loops: Utilize agile methodologies that incorporate regular check-ins with stakeholders, including users, to ensure the development process remains aligned with user needs and expectations. This helps catch misunderstandings and misalignments early before they escalate into bigger issues.
- Empower Product Owners: Strengthen the role of product owners to act as the bridge between the development team and users. Ensure they have the authority and responsibility to make user engagement a priority and the power to influence the development process based on user feedback.
- Measure Impact, Not Just Output: Shift success metrics from purely delivery-based to impact-based. Evaluate how well the product meets user needs and the value it adds to their experience, rather than just adherence to timelines and specifications.
Issue 6: Whispering Into the Wind (Scattering Info Instead of Intentional Communication)
Effective communication is the spine of any successful project, yet all too often, it becomes an afterthought in program management. Information ends up scattered across emails, instant messages, meetings, and informal chats without a structured communication plan. This ad-hoc approach relies on chance rather than strategy, hoping that critical updates reach the right stakeholders through random broadcasts. The absence of defined channels, specified formats, and scheduled frequencies leads to missed connections, misunderstandings, and gaps in knowledge, impacting the project’s success, benefits, and efficiency.
- Develop a Comprehensive Communication Plan: Create a detailed plan that identifies all key stakeholders, specifies the channels for communication (e.g., email, newsletters, meetings), outlines the information format, and sets a regular frequency for updates. This plan should be tailored to the needs of different stakeholder groups and be integrated into the overall project management strategy.
- Utilize Centralized Communication Tools: Adopt tools that centralize communication, such as project management software or platforms like Confluence or SharePoint that consolidate messages, documents, and updates in one accessible location. This helps ensure that all team members have access to the same information and can easily find what they need when they need it.
- Regularly Review and Adjust Communications: Regularly solicit feedback from stakeholders about the effectiveness of communication strategies and make adjustments as necessary. This iterative process ensures that the communication remains relevant and effective throughout the life of the project.
- Train Team Members in Effective Communication: Provide training for team members on effective communication techniques and the importance of intentional information sharing. Empower team members to take proactive roles in disseminating information appropriately and responsibly.