Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches Episode: The No-Scroll Bar Rule—Empowering PO’s Through Constraints | Joel Bancroft-Connors
Host: Vasco Duarte
Guest: Joel Bancroft Connors
Release Date: June 6, 2025

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte welcomes Joel Bancroft Connors, an experienced Agile Coach and Scrum Master, to discuss common anti-patterns in Product Ownership and effective strategies to empower Product Owners (POs) through intentional constraints. The conversation delves deep into optimizing team dynamics, enhancing communication, and fostering an environment where developers can thrive creatively within Agile frameworks.

Product Owner Anti-Patterns: The BA That Can't Let Go

Joel begins by addressing a prevalent anti-pattern he has observed in Agile teams: having both a Product Owner and a Business Analyst (BA) on the same team. He explains how this setup often leads to a "game of telephone," resulting in miscommunication and inefficiency.

“Anytime you have multiple lines of communication, things are going to fail.”
— Joel Bancroft Connors [02:04]

Joel shares his experience where a BA struggled to relinquish control, over-documenting requirements and hindering the development process. This micromanagement stifles developers' autonomy and creativity, leading to less effective outcomes.

The No-Scroll Bar Rule: Enforcing Concise Documentation

To combat the issue of over-documentation, Joel introduces his innovative "No Scroll Bar Rule." This rule mandates that the description field in Jira (or similar tools) should fit within 10 lines and 120 characters per line, ensuring clarity and brevity before engaging with developers.

“My rule is called the no scroll bar rule. The description field in Jira... there should be no scroll bar on the description field.”
— Joel Bancroft Connors [04:52]

This constraint forces POs to distill requirements to their essence, promoting clearer communication and enabling more effective discussions with the development team.

Empowering Developers Through Constraints

Vasco and Joel discuss the importance of empowering developers by limiting the extent of detailed instructions, allowing them to inject technical innovation and ownership into their work.

“We want to unleash them. We want to give them problems... create awesome and we'll give you feedback along the way.”
— Vasco Duarte [06:12]

Joel reinforces this by emphasizing that product owners should provide a clear vision without dictating every implementation detail, fostering an environment where developers can contribute their unique insights and expertise.

Effective Product Owner Collaboration: A Dual PO Approach

Joel shares a compelling case study from his experience with an insurance organization that successfully employed a dual Product Owner model. By pairing a business-oriented PO with a design-focused PO, the teams were able to leverage complementary skills, leading to a significantly reduced project timeline from 18 months to just six months.

“They’re going to work together because it’s a shared product goal... build it in, I think it was about six months.”
— Joel Bancroft Connors [12:12]

This collaboration ensured that strategic business goals and user experience designs were seamlessly integrated, demonstrating the power of diverse skill sets working towards a common objective.

Complementary Skills: Enhancing Team Collaboration

The conversation highlights how collaboration thrives when team members bring complementary skills to the table. Joel illustrates how blending business acumen with user experience expertise can create a more robust and effective product development process.

“The business person and the designer both got better... reflecting back to start with why.”
— Joel Bancroft Connors [13:21]

By focusing on a shared persona and aligning team efforts with the overarching "why" of the project, teams can maintain a united direction while benefiting from diverse perspectives.

Embracing Agile Principles: Start with Why

Joel and Vasco conclude by underscoring the fundamental Agile principle of "Start with Why," advocating for teams to understand the purpose behind their work to ensure meaningful and high-value outcomes.

“Build projects around motivated individuals, give them the environment and support they need to get the job done... tell them what you want and then get the heck out of their way.”
— Joel Bancroft Connors [07:49]

This principle not only fosters motivation but also enhances the overall effectiveness and satisfaction of the team, aligning perfectly with Agile methodologies.

Conclusion

This episode provides valuable insights into optimizing Product Ownership within Agile teams. Joel Bancroft Connors offers practical strategies, such as the "No Scroll Bar Rule" and dual Product Owner models, to mitigate common anti-patterns and empower teams effectively. By fostering clear communication, leveraging complementary skills, and adhering to core Agile principles, Scrum Masters and Agile Coaches can significantly enhance their team's performance and product outcomes.

For more resources and to connect with Joel Bancroft Connors, visit thegorillacoach.com or follow him on LinkedIn.

Resources Mentioned:

• Scrum Master Toolbox Membership
• Joel Bancroft Connors' Website: thegorillacoach.com
• Agile Coaching and Training at scrumaliance.org

Subscribe and Rate: If you found this episode valuable, please rate it on your preferred podcast platform and share it with fellow Scrum Masters and Agile practitioners.