The Agile Playbook: How I Stopped Managing Teammates and Started Building a Team

The Opening Tip

I’m an organizational psychologist.

I spend my days helping companies untangle complex human dynamics to build more effective, cohesive, and psychologically safe teams.

But on Tuesday nights, I’m just a basketball player.

I’m the guy who, for two hours, forgets about frameworks and data sets and just lives for the simple joy of the game.

There’s a particular magic in a perfectly executed play—a crisp pass to a cutting teammate for an easy layup, a seamless defensive rotation that forces a turnover.

It’s a moment of pure, unspoken connection.

It’s that feeling of being part of something that works.

This is the promise that pulls millions of adults into recreational sports leagues every year.¹

We sign up for the exercise, the stress relief, and the simple fun of playing a game we love.²

But if we’re honest, we’re chasing something deeper.

We’re chasing camaraderie, community, and that feeling of belonging to a team.⁴

In a world that often feels isolating, a rec league offers a chance to reconnect with a shared passion and be part of a tribe, even if just for a few hours a week.

For years, I chased that promise.

And for years, I was let down.

My Tuesday nights were often more frustrating than fulfilling.

I’ve come to believe that most rec teams are set up to fail.

Not because the players are bad or the intentions aren’t good, but because they operate on a fundamentally flawed model of what a team is and how it should function.

The good news is that there’s a better Way. The solution, I discovered, doesn’t come from a legendary coach’s biography or a dusty basketball playbook.

It comes from a place I never expected: the fast-paced, high-tech world of software development.

It’s a counter-intuitive framework that can transform any dysfunctional group of individuals into a cohesive, effective, and genuinely enjoyable team.

The Anatomy of a Meltdown: Why Most Rec Teams Fall Apart

To understand the solution, you first have to appreciate the depth of the problem.

Let me tell you about a team I captained a few years ago.

We called ourselves “The Vipers.” It’s a fitting name, because by the end of the season, the atmosphere was toxic.

The Vipers were a case study in every dysfunction that plagues adult rec leagues.

The Symptoms of Dysfunction

Our games were not basketball; they were a collection of five individual agendas happening to unfold on the same court.

The on-court chaos was the most visible symptom.

We had a couple of guys who had played in high school and clearly felt they were the most skilled players on the team.

They would dominate the ball, taking on multiple defenders while ignoring wide-open teammates.⁶

This is the classic “everyone wants to be Kobe, but no one wants to be Robert Horry” problem.

It’s the belief that individual heroics are the path to victory, a mindset that is poison in a team setting.

The result was a stagnant offense with no movement, predictable one-on-one drives into traffic, and a flurry of contested, low-percentage shots.⁷

This on-court mess was a direct result of our off-court organizational failure.

We never practiced.

An email thread a day before the game was our only form of communication.

Inevitably, someone wouldn’t reply, and we’d show up to a game with only four players, forfeiting before the opening tip or playing a man down and getting crushed.⁶

There was no shared plan, no simple offensive set to fall back on, no agreed-upon defensive strategy.⁷

We were a team of busy adults with competing priorities, and without a structure to manage that reality, chaos was the default setting.⁸

Compounding the problem was the chasm in skill levels.

Like many rec league teams formed from a list of “free agents,” we were a random assortment of talent.¹⁰

We had the two former high school players, a few guys like me who could hold their own, and several players who were picking up a basketball for the first time in a decade.

This disparity is a common structural issue in leagues that lack proper skill-based divisions or a player draft system.¹¹

The result was profound frustration for everyone.

The skilled players felt they had to do everything themselves, reinforcing their ball-hogging tendencies.

The less-skilled players barely touched the ball, felt useless, and quickly became disengaged.¹³

Every game was a blowout, one way or another, which is the fastest way to kill the fun and competitive spirit of a league.¹⁰

Predictably, this environment curdled into a culture of blame.

On-court mistakes were met with exasperated sighs and pointed fingers.

Frustration boiled over into arguments with teammates and referees.¹⁴

As captain, I tried to offer tactical suggestions during timeouts.

“Hey, let’s try to pass the ball three times before we shoot,” I’d say.

Or, “Can we focus on getting back on defense?” My attempts were met with eye-rolls or, in one memorable exchange, a teammate telling me I was “being too negative”.⁶

This is a classic sign of a team that lacks psychological safety—an environment where feedback is perceived as a personal attack rather than a tool for collective improvement.

The Vicious Cycle of Rec League Failure

My experience with The Vipers wasn’t unique.

In fact, it was tragically typical.

Looking back with my psychologist’s hat on, I see a clear, destructive pattern that dooms many rec teams from the start.

It’s a vicious cycle.

It begins with noble intentions: adults join for community, fun, and healthy competition.²

However, the league structure itself often sets them up for failure.

Without a thoughtful draft or strictly enforced skill divisions, teams are inherently imbalanced.¹⁰

This structural flaw immediately leads to non-competitive games and mounting frustration.

That frustration is the kindling.

It erodes sportsmanship and triggers a psychological shift from a “we” mindset to a “me” mindset.¹⁵

Players think, “This team is a mess, I have to do it all myself.” This leads directly to selfish, individualistic play—the ball-hogging, the forced shots, the defensive lapses.⁶

This behavior, in turn, destroys the very things everyone signed up for: the sense of teamwork, the fun, and the community.

The system is perfectly designed to defeat its own purpose.

The “Captain-as-Coach” Trap

At the center of this vortex is the team captain, a role that is often a leadership vacuum.

The captain is expected to handle logistics like registration and payment, but they are given no framework for actually leading a team of adult peers.¹⁶

Most captains, myself included, fall into one of two traps.

The first is the “Captain-as-Coach” trap.

You try to draw up plays, dictate strategy, and correct mistakes like a traditional coach.

This almost always fails.

Your teammates are not high school kids; they are adults who are volunteering their time and money to be there.

They don’t have to listen to you, and they often resent the implication of a hierarchy where you are the boss and they are the players.⁶

The second trap is the “Captain-as-Administrator.” Fearing the first trap, you do nothing but manage the roster and send emails.

You provide no on-court leadership, leaving a void that is quickly filled by chaos and the competing agendas of individual players.

I failed as the Vipers’ captain because I vacillated between these two failed models, trying to be a coach one minute and a passive observer the next.

What I needed was a completely different model for leadership and teamwork.

The Epiphany: Your Basketball Team Isn’t a Pro Team, It’s an Agile Startup

The turning point for me came not on a basketball court, but in a corporate conference room.

I was working with a software development team, helping them improve their collaborative processes.

I watched them conduct something they called a “sprint retrospective.” It was a short, highly structured meeting where the entire team discussed their last two weeks of work.

The conversation was candid, blameless, and focused entirely on improving their process.

They talked about communication bottlenecks, inefficient tools, and interpersonal friction with a level of honesty and constructiveness I had never seen on a sports team.

That was my epiphany.

Their challenges were identical to the ones my basketball team faced.

They were a small group of people with diverse skills and personalities, trying to collaborate under pressure to solve complex, unpredictable problems.

And they had a system for it.

A system called Agile.

Agile is a project management methodology born in the software world, but its principles are universal.¹⁷

It is a framework designed specifically for small, self-organizing teams to tackle complex work in a dynamic environment.

It prioritizes flexibility, continuous feedback, and iterative progress over rigid, long-term plans.

As I learned more, I realized that a rec league basketball team is the perfect environment for an Agile approach.

Deconstructing the Flawed “Pro Team” Model

The fundamental reason most rec teams fail is that we implicitly model them after professional or college teams.

We think in terms of a top-down hierarchy: a powerful coach who holds all the knowledge, a playbook of set plays to be executed flawlessly, and a singular focus on winning the championship.¹³

This model is completely inappropriate for a group of adults who meet once a week, have varying skill levels, and have never practiced together.⁶

You can’t install a complex offense in a five-minute timeout.

You can’t command the respect of a coach when you’re just another player who paid the same league fee.

The model is a fantasy that leads to frustration.

Presenting the “Agile Startup” Model

A rec league team is not the Los Angeles Lakers.

A rec league team is a startup.

It’s a small, passionate, resource-constrained group of people trying to create a valuable product (a functional team that has fun and competes) in a highly uncertain environment.

They need to be nimble, communicative, and obsessed with learning and adapting.

They need a system that embraces their reality, not one that pretends they’re something they’re not.

This paradigm shift from a “Pro Team” to an “Agile Startup” changes everything.

It reframes the goals, the roles, and the very definition of success.

The following table illustrates this crucial mental shift.

Table 1: The Paradigm Shift: From a Traditional to an Agile Rec Team

Traditional Mindset (The Pro Team Fallacy)	Agile Mindset (The Startup Reality)
Goal: Winning the championship.	Goal: Getting measurably better this week.
The Captain: Is the “Coach” who dictates strategy.	The Captain: Is the “Facilitator” who removes obstacles.
The Plan: A set of complex plays that fall apart.	The Plan: A simple, shared focus for each game.
Mistakes: Are failures to be criticized or blamed.	Mistakes: Are data points for learning and improvement.
Feedback: Is seen as personal criticism (“being negative”).	Feedback: Is a structured, blameless process for improvement.
Success: Is measured only by the final score.	Success: Is measured by executing the weekly focus.

This shift in mindset is the foundation of the Agile Playbook.

It’s about trading the fantasy of being a pro team for the practical reality of being a startup, and using the tools of a startup to succeed.

The Agile Basketball Framework: A New System for Playing Together

After my epiphany, I began to develop a new playbook.

It wasn’t about X’s and O’s; it was about process.

I borrowed the core concepts from Scrum, the most popular and straightforward Agile framework, and translated them for the basketball court.¹⁹

Scrum provides a simple, lightweight structure that, paradoxically, creates freedom, clarity, and accountability.

It’s built on three pillars: a new way to define the season and its goals, a new way to define roles, and a new set of rituals that build cohesion.

Pillar I: The Sprint & The Backlog – Redefining the Season

The first step is to stop thinking about the eight- or ten-game season.

That long-term focus is demotivating when you’re losing and leads to complacency when you’re winning.

In the Agile world, work is broken down into short, time-boxed cycles called “Sprints”.²²

The One-Week Sprint: For a rec team, a sprint is simply one week, culminating in your game.

The goal of each sprint is not to win, but to produce a “Potentially Shippable Increment” of value.

In basketball terms, this means making one small, tangible, and observable improvement as a team.

The Product Backlog: To decide what to improve, the team needs a “Product Backlog.” This is simply a master list of all the things the team could work on to get better.²²

At your first team meeting (or in a group chat), you create this list together.

It should be simple and action-oriented.

Examples might include:

• “Run a basic pick-and-roll on the wing.”
• “Every player boxes out on every shot.”
• “Communicate on all defensive screens.”
• “Stop the ball in transition.”
• “Make at least one extra pass on offense.”
  This backlog is a living document, owned by the whole team.

The Sprint Backlog: Before each game, the team selects just one or two items from the Product Backlog to focus on for that week’s sprint.

This becomes the “Sprint Backlog”.²²

By narrowing the focus to a single, achievable goal, you create clarity and eliminate the feeling of being overwhelmed.

You’re not trying to fix everything at once; you’re just trying to get a little bit better at one specific thing.

Pillar II: Roles & Responsibilities – Redefining the Team

The “Captain-as-Coach” model is broken.

Scrum offers a brilliant solution by defining three distinct roles that solve the leadership vacuum and empower the entire team.²⁰

These roles are crucial for establishing the role clarity that is proven to enhance team performance and reduce conflict.²³

The Product Owner (The Vision-Setter): This role is a natural fit for the team captain.

The Product Owner’s job is not to coach.

Their job is to own and manage the Product Backlog.¹⁹

They facilitate the conversation about what the team should prioritize.

They might say, “Guys, looking at our backlog, I think the most valuable thing we could work on this week is our transition defense.

What do you all think?” They guide the vision, but the decision is collaborative.

The Scrum Master (The Facilitator): This can be the captain or another willing player.

The Scrum Master is a servant-leader.

Their job is to facilitate the Scrum “events” (the huddles, which we’ll get to next) and to remove impediments.¹⁹

An impediment is anything blocking the team’s progress.

For example, if players are confused about how to defend a pick-and-roll, the Scrum Master’s job is to say, “Okay, let’s take 30 seconds and walk through it.” If the team needs a new ball or has a question about the league rules, the Scrum Master handles it.

They make the process run smoothly so the team can focus on playing.

The Development Team (The Players): This is everyone else.

In Scrum, the Development Team is self-organizing.²²

This is a critical concept.

The Product Owner and the team decide

what the priority is (the Sprint Goal), but the Development Team—the players on the court—decides how they will achieve it during the game.

This simple shift in responsibility is incredibly empowering.

It leverages the collective intelligence of the group and gives every player ownership over the team’s success.

Pillar III: The Events – Rituals That Build Cohesion

Scrum is driven by five simple, structured events (or meetings).

These events create a rhythm for the team and enforce the core Agile principles of transparency, inspection, and adaptation.¹⁹

For a basketball team, these can be adapted into quick, powerful on-court rituals.

Sprint Planning (The 5-Minute Pre-Game Huddle): Before the game, the full team huddles up.

This is your Sprint Planning meeting.²²

The Product Owner presents the highest-priority item from the backlog.

The team discusses it and agrees on a “Sprint Goal” for that game.

The goal should be specific and observable.

For example: “Our goal for this game is that on every defensive possession, we call out screens loud enough for our teammates to hear.” That’s it.

The whole team now has a single, shared definition of success for the next hour that has nothing to do with the scoreboard.

Daily Scrum (In-Game Communication): The Daily Scrum in software development is a quick daily check-in.

On the court, it’s not a formal meeting but a continuous mindset.²²

It’s the communication during timeouts, free throws, and dead balls.

The conversation is focused on the Sprint Goal.

A player might say, “Hey guys, I’m not hearing the screen calls.

Let’s pick it up.” Or, “Great job on that last possession, the communication was perfect.” It keeps the team aligned and focused on their shared objective.

Sprint Review (The 2-Minute Post-Game Huddle): Immediately after the final buzzer, before anyone leaves the court, the team huddles for the Sprint Review.²²

The purpose of this meeting is to inspect the “increment.” The Scrum Master asks one question: “Did we achieve our Sprint Goal?” The team gives a quick assessment: “Yes, we did great,” or “No, we forgot about it after the first quarter.” The final score of the game is irrelevant to this specific conversation.

This ritual powerfully redefines success away from simply winning or losing and toward the process of improvement.

Sprint Retrospective (The 5-Minute Parking Lot Chat): This is the most important event in the entire framework.

After the Sprint Review, as you’re packing your bags or walking to your cars, the Scrum Master facilitates the Sprint Retrospective.²²

The question here is different: “Regardless of our goal or the score,

how did we work together as a team? What is one thing that went well in our process? What is one thing we could improve in how we communicate or collaborate for next week?” This is a blameless discussion focused entirely on the team’s dynamic.

It’s the engine that drives continuous improvement and builds team cohesion.

The Secret Ingredient: Building Psychological Safety on the Court

After I developed this Agile framework, I tested it with a new team.

It worked, but I soon realized the framework itself was just a skeleton.

The reason it was so effective was the culture it created.

The Agile rituals weren’t just about managing a project; they were a brilliantly designed system for building the single most important attribute of any high-performing team: psychological safety.

Psychological safety is a concept from organizational psychology defined as a shared belief held by members of a team that the team is safe for interpersonal risk-taking.²⁵

It’s the feeling that you can speak up with an idea, ask a “dumb” question, admit a mistake, or challenge the status quo without fear of being punished, embarrassed, or humiliated.²⁶

It is the absolute antidote to the culture of fear and blame that defined my time with The Vipers and that plagues so many other rec teams.⁶

The Agile Framework as a Psychological Safety Engine

The Agile playbook isn’t just a set of actions; it’s an engine for systematically manufacturing psychological safety.

Each pillar and ritual is designed to lower interpersonal risk and build trust.

Think about the four stages of psychological safety, a model developed by Timothy R.

Clark ²⁶:

1. Inclusion Safety: The feeling that you belong to the team. The Agile framework fosters this from day one by having the team collaboratively create the Product Backlog and agree on Sprint Goals. Everyone’s voice is included in setting the team’s direction.
2. Learner Safety: The feeling that you can ask questions, experiment, and make mistakes without being punished. This is at the very core of the Agile mindset. By framing every game as a “sprint” and every season as a series of experiments, the framework normalizes mistakes as learning opportunities, not failures.²⁸ The Sprint Retrospective provides a dedicated, safe space to ask, “Why didn’t that work?”
3. Contributor Safety: The feeling that you can make a meaningful contribution. By focusing on small, achievable Sprint Goals, the system allows every player, regardless of skill level, to contribute to the team’s success. A beginner might not be able to score 20 points, but they can absolutely contribute to the Sprint Goal of “boxing out on every shot.” This gives them a clear and valued role.²³
4. Challenger Safety: The feeling that you can challenge the way things are done. This is the highest level of psychological safety. Over time, as the team gets comfortable with the blameless feedback of the retrospective, players will start to feel safe enough to suggest new ideas. A player might say, “Hey captain, I know our goal was to work on the pick-and-roll, but I think our biggest issue is transition defense. Could we prioritize that next week?” This is the sign of a truly healthy, empowered team.

A Guide Through the Storm

Another way to understand why this works is through the lens of Bruce Tuckman’s classic model of group development: Forming, Storming, Norming, and Performing.²⁴

Most rec teams get stuck permanently in the “Storming” stage—that period of conflict, frustration, and jostling for position as individual personalities and working styles clash.³²

The storming on The Vipers was personal and destructive (“You’re being too negative,” “You’re a ball hog”).

The Agile framework doesn’t prevent the storming phase; it’s a natural and necessary part of a team’s growth.

Instead, the framework provides a safe harbor and a compass to navigate it.

The Sprint Retrospective channels the storm’s energy constructively.³⁴

It depersonalizes conflict by focusing it on the

process, not the people.

Instead of a player yelling, “You never pass me the ball!” the conversation in a retrospective becomes, “How can we, as a team, improve our ball movement to create more open shots for everyone?” This simple reframing allows the team to address its core issues without damaging relationships.

It helps the team move quickly from “Storming” to “Norming” (where they agree on new processes) and, ultimately, to “Performing” (where they operate as a truly cohesive and effective unit).

As a leader—the Scrum Master or Product Owner—your job is to foster this safety.

You do this by modeling vulnerability and admitting your own mistakes first.²⁹

You frame all work as a learning problem, not an execution problem.²⁶

And you facilitate the team’s rituals with a focus on open, honest, and respectful communication.³⁵

The System in Action: A Toolkit for Transformation

Theory is one thing; practice is another.

After my time with The Vipers, I joined a new team.

I was hesitant to be captain again, but I agreed on one condition: that we try a new way of doing things.

I called us “The Scrappers.”

From the very first email, I introduced the Agile Playbook.

I explained that our goal wasn’t to win a championship, but to have fun and get better every week.

At our first game, I led a five-minute pre-game huddle.

“Okay, Scrappers,” I said, “our only goal for this game is to call each other by name on defense.

That’s it.

If we do that, we’ve succeeded.” We lost that game by 20 points.

But in the post-game huddle, the mood was different.

“How’d we do on the goal?” I asked.

The consensus was that we did pretty well.

In our first-ever retrospective in the parking lot, a player said, “I felt like we actually talked to each other for the first time.”

We kept the process up.

Each week, a new Sprint Goal.

Each week, a quick review and retrospective.

We started winning a few games, but more importantly, people were showing up.

They were engaged.

The high-skilled players were teaching the beginners.

The beginners were setting screens and making the extra pass.

In the last game of the season, we were down by 10 points with three minutes to go.

In the timeout, there was no panic, no blame.

Our Sprint Goal that week was “stay positive.” One of the guys just said, “Hey, let’s stick with it.

One possession at a time.” We chipped away, got a few stops, and won the game on a last-second shot.

It wasn’t the win that mattered.

It was the feeling in that huddle.

We had become a team.

The Step-by-Step Implementation Guide

You can replicate this success.

Here is a simple guide for any captain or player who wants to implement the Agile Playbook.

1. Session Zero: The Kick-Off. Before the season starts, send an email or have a quick meeting. Introduce the concept simply. Say, “Hey everyone, instead of just showing up and playing, I’d like to try a simple system to help us play better together and have more fun. It’s just a few short huddles before and after each game to keep us focused.”
2. Build the Product Backlog. At that first gathering, ask the team: “What are all the things a good basketball team does?” Write them all down on a whiteboard or a shared note. This is your Product Backlog. Then, have the team vote on the top 3-5 priorities.
3. Run Your First Sprint (Game 1). Use the toolkit below. Before the game, facilitate the Sprint Planning huddle. Pick one of your top priorities as the Sprint Goal. During the game, remind the team of the goal. After the game, run the Sprint Review and Sprint Retrospective. Keep it short, positive, and focused on process.
4. Sustain Momentum. The key is consistency. Do the rituals every single week. The Scrum Master’s job is to protect the process. Even if people are tired or frustrated after a loss, insist on the two-minute huddles. They are the foundation of the entire system.

To make it even easier, here is a simple “cheat sheet” you can use for every game.

Table 2: The Agile Basketball Toolkit: A Game-by-Game Guide

Phase	Agile Event	Time	Key Questions / Actions
Pre-Game	Sprint Planning	5 Mins	“Welcome. Looking at our backlog, what’s the one thing we want to focus on this game? Let’s agree on our Sprint Goal.”
In-Game	Daily Scrum	Ongoing	During timeouts/dead balls: “How are we doing on our Sprint Goal? What adjustments do we need to make?”
Post-Game	Sprint Review	2 Mins	“Huddle up. Did we achieve our Sprint Goal of [e.g., ‘communicating on defense’]? Yes/No/Sort of? Great.”
Post-Game	Sprint Retrospective	5 Mins	“Okay, separate from the goal, how did we play as a team? What’s one thing that went well in our process? What’s one thing we can improve for next week?”

Conclusion: More Than a Game

My journey from the frustration of The Vipers to the cohesion of The Scrappers taught me a profound lesson.

The chaos and disappointment that define so many adult recreational sports experiences are not inevitable.

They are the result of using the wrong model.

We are not professional athletes, and our teams are not professional organizations.

We are groups of people seeking connection, joy, and a bit of healthy competition in our limited free time.

The Agile Playbook works because it is designed for this reality.

It provides just enough structure to prevent chaos, but not so much that it crushes the fun.

It redefines success away from the scoreboard and toward the process of collective improvement.

It gives every player, regardless of skill, a clear and valued role.

Most importantly, it systematically builds the psychological safety that allows a group of individuals to risk becoming a team—to communicate honestly, to learn from mistakes, and to trust one another.

This framework does more than just help a team win a few more games.

It transforms the entire experience back into what we all signed up for in the first place: a source of growth, a challenge to be overcome together, and a genuine human connection.²

By focusing on the process over the outcome and on team cohesion over individual glory, the Agile Playbook offers a better way to play basketball.

But more than that, it offers a better way to be a team.

Works cited

1. Adult Sports Leagues – Mustang Morning News, accessed on August 8, 2025, https://mustangmorningnews.com/18964/uncategorized/what-is-the-reason-for-adult-sports-leagues/
2. 5 Life-Changing Benefits of Playing Adult Rec Basketball – AFC Fitness, accessed on August 8, 2025, https://www.afcfitness.com/blog/5-life-changing-benefits-of-playing-adult-rec-basketball/
3. The Case For Joining a Rec Sports Team as an Adult – 37.5 Technology, accessed on August 8, 2025, https://www.thirtysevenfive.com/blog/the-case-for-joining-a-rec-sports-team-as-an-adult/
4. Adult and Youth Sports & Recreational Leagues and Programs – YMCA, accessed on August 8, 2025, https://www.ymca.org/what-we-do/healthy-living/sports-recreation
5. 5 Reasons To Join an Adult Sports League – Spotz, accessed on August 8, 2025, https://www.findspotz.com/blog/5-reasons-to-join-an-adult-sports-league
6. Annoyed at rec teammates and my frustration shows : r/Basketball, accessed on August 8, 2025, https://www.reddit.com/r/Basketball/comments/13cfecu/annoyed_at_rec_teammates_and_my_frustration_shows/
7. [Help] Teaching Adults how to play organized basketball (&as a unit …, accessed on August 8, 2025, https://www.reddit.com/r/BasketballTips/comments/125xtxw/help_teaching_adults_how_to_play_organized/
8. The 4 Main Challenges of Managing a Youth Sports Team – SquadLocker, accessed on August 8, 2025, https://www.squadlocker.com/squad-blog/challenges-of-managing-a-youth-sports-team
9. Player Commitment | – Holliston Youth Soccer Association, accessed on August 8, 2025, https://hollistonsoccer.org/parents/player-commitment/
10. How serious do men’s rec leagues tend to be? : r/Basketball – Reddit, accessed on August 8, 2025, https://www.reddit.com/r/Basketball/comments/1bd9mkb/how_serious_do_mens_rec_leagues_tend_to_be/
11. Adult Sports | City of Peoria, accessed on August 8, 2025, https://www.peoriaaz.gov/government/departments/parks-recreation-and-community-facilities/recreation-programs/sports/adult-sports
12. Youth Basketball | Henderson, NV, accessed on August 8, 2025, https://www.cityofhenderson.com/government/departments/parks-and-recreation/programs-classes/sports/youth-sports/youth-basketball
13. What’s Wrong With Youth Basketball Leagues, accessed on August 8, 2025, https://www.breakthroughbasketball.com/coaching/developmental-league.html
14. First Time Doing Men’s League – The Official Forum, accessed on August 8, 2025, https://forum.officiating.com/basketball/100460-first-time-doing-mens-league.html
15. The Rec League Jerk: Overcoming “THAT” Person – Sport & Social Club, accessed on August 8, 2025, https://sportsocial.blog/2015/03/02/the-rec-league-jerk-overcoming-that-person/
16. Adult Basketball – Town of Cary, accessed on August 8, 2025, https://www.carync.gov/recreation-enjoyment/sports/adult-sports/adult-basketball
17. 9 Best Agile Project Management Tools – Atlassian, accessed on August 8, 2025, https://www.atlassian.com/agile/project-management/tools
18. What is Agile? | Atlassian, accessed on August 8, 2025, https://www.atlassian.com/agile
19. The 2020 Scrum Guide TM, accessed on August 8, 2025, https://scrumguides.org/scrum-guide.html
20. What is Scrum?, accessed on August 8, 2025, https://www.scrum.org/resources/what-scrum-module
21. Scrum Guides: Home, accessed on August 8, 2025, https://scrumguides.org/
22. Scrum 101: Your Guide to Getting Started with Scrum – Parabol, accessed on August 8, 2025, https://www.parabol.co/resources/scrum-101-guide/
23. What Is Role Clarity? How to Define Roles and Responsibilities, accessed on August 8, 2025, https://theorgchart.com/role-clarity/
24. Tuckman’s Stages of Group Development – WCU of PA – West Chester University, accessed on August 8, 2025, https://www.wcupa.edu/coral/tuckmanStagesGroupDelvelopment.aspx
25. How to Build Psychologically Safe Workplaces | CCL, accessed on August 8, 2025, https://www.ccl.org/articles/leading-effectively-articles/what-is-psychological-safety-at-work/
26. Psych Safety – What is Psychological Safety?, accessed on August 8, 2025, https://psychsafety.com/about-psychological-safety/
27. What is psychological safety? – McKinsey, accessed on August 8, 2025, https://www.mckinsey.com/featured-insights/mckinsey-explainers/what-is-psychological-safety
28. Agile For Small Teams: Positives, Challenges, And Limitations | by Syeda Taqvi | Medium, accessed on August 8, 2025, https://medium.com/@syeda_taqvi/agile-development-for-very-small-software-teams-66eaa6adc502
29. Psychological Safety First: Building Trust Among Teams – Slack, accessed on August 8, 2025, https://slack.com/blog/collaboration/psychological-safety-building-trust-teams
30. The 5 Stages of Team Development: Tuckman’s Model – Institute of Project Management, accessed on August 8, 2025, https://instituteprojectmanagement.com/blog/the-5-stages-of-team-development/
31. Using the Stages of Team Development | MIT Human Resources, accessed on August 8, 2025, https://hr.mit.edu/learning-topics/teams/articles/stages-development
32. Forming, storming, norming & performing: Tuckman’s stages of team development, accessed on August 8, 2025, https://www.bitesizelearning.co.uk/resources/tuckman-stages-team-development-forming-norming-storming-performing
33. The 5 Stages of Tuckman’s Team and Group Development Model Plus How to use it | by Emma-Louise | The Launchpad – The Coaching Tools Company, accessed on August 8, 2025, https://www.thecoachingtoolscompany.com/get-your-team-performing-beautifully-with-this-powerful-group-development-model/
34. Tuckman’s 5 Stages of Team Development (Forming, Storming, Norming, Performing, Re-forming) – YouTube, accessed on August 8, 2025, https://www.youtube.com/watch?v=-RwkZxGPQb8
35. 11 best practices to improve team communication – RingCentral, accessed on August 8, 2025, https://www.ringcentral.com/us/en/blog/11-best-practices-to-improve-team-communication/
36. Why It’s Necessary to Improve Team Communication | American Public University, accessed on August 8, 2025, https://www.apu.apus.edu/area-of-study/business-and-management/resources/why-it-is-necessary-to-improve-team-communication/
37. Never Too Late Basketball | Play Better, Play Forever, accessed on August 8, 2025, https://nevertoolate.com/