Awesome List of resources on Agile Software Development.
10 Warning Signs, That Your Team Is Not Self-Organizing - by Peter Stevens
Building a Self-Organized Team in a Radically Agile Company. - by Matthias Kunze and Himanshu Sharma
Fear Has to Go for Agile Teams To Succeed - by Anthony Mersino. “Fear and creativity cannot coexist. If we have fear, we don’t have creativity, we have reduced productivity and are not working effectively. We are not leveraging the full potential of our people and teams. So fear, in all its forms has to go in order for teams to succeed with Agile.”
How To Build An Agile Team - by Luke Morton. “A team needs to know they have the power and responsibility to solve a challenge. A team needs to be excited about their solutions, conversating and learning from each other. A team needs small focussed goals in order to deliver on time.”
How to Align Scrum Teams - by Stefan Wolpers. “In the end, at least in my opinion, aligning Scrum teams will only work based on autonomous feature teams. Any other set-up will create too many dependencies, thus wasting money, brains, and time. It will also prevent the organization from becoming a learning one.”
How to Tell Whether Your Team is Agile - by Gil Broza
Scrum Myths 10 - Non-Scrum Roles by Mishkin Berteig Scrum Expert (Video) - by BERTEIG’s World Mindware. “Many organizations continue to maintain traditional IT / technology roles when they switch to using the Scrum process… but this isn’t Scrum! Scrum only allows three roles. Why is it wrong to have a tester, a business analyst and database admin on a Scrum Team? Find out the advantages of re-defining all the roles in your organization.”
What Is a Team? - by The LeSS Company
Why Cross-Functional Teams Fail? How Solver-Teams Sail! - by Ajay Shrivastava. “Move Fast, Fail Fast, Iterate - is only possible when there is a trusting and synergistic environment.”
How To Kickstart A Great Scrum Team (10 practical things to do) - by Christiaan Verwijs
Trust, Diversity, And Passion — The 3 Ingredients Of Successful Organizations - by Richard Bliss. “Trust, diversity, and passion—these are the ingredients of successful organizations. These soft-edge traits can be taught, but not easily duplicated.”
Storm To Perform: The 4 Stages Of Team Productivity - by Leah Ryder. “Dr. Bruce Tuckman, a psychology professor, first proposed his group development stages model in a 1965 study, reviewing over 50 existing works on team theory. From that body of work, he synthesized team development into four basic stages, even giving them handy rhyming names: Forming, Storming, Norming, and Performing.”
5 Exercises That Break Down Barriers - By Minnie Bredouw. “Any one of these exercises will help bring a feeling of common humanity into view. So, next time you enter a room full of strangers, save the cheesy icebreakers and admit that you’re a cat person instead.”
10 New Rules For Brainstorming Without Alienating Introverts - by Judah Pollack and Olivia Fox Cabane. “Your brainstorm can afford to loosen up and adopt a revolving-door policy, with people coming and going. But once you’ve generated enough ideas, everyone has to come together again and forge ahead as a team.”
Feedback for Teams - by Christina Wodtke. “This is the true “gift” of feedback. To see yourself how others see you, and decide what to do with that information.”
How Awesome Engineers Ask for Help - Greg Sabo. “Asking for help is hard, and procrastination protects us from it. That’s why you must perfect your ability to ask for help. It’s key to achieving productivity as an engineer.”
How To Improve Cross-Functional Collaboration - by Reese Schmit. “… some really smart people have come up with activities to help identify silos and gaps allowing teams to create a plan to fix them. I’m going to show you a few favorites I’ve used in the past with incredible results.”
Meeting Agreements for High Performing Teams - by Joshua Kerievsky. Tips on how to establish psychological safety in order to have productive meetings.
Of Arguments and Agile - by Declan Appleyard. “Ultimately, though, it’s up to you to foster this open culture, be an example of what you are trying to achieve, and be brave enough to challenge ideas. Help defuse hostile situations and remind people that, at the end of the day, we are all working toward a common goal.”
We Fired Our Top Talent. Best Decision We Ever Made. - by Jonathan Solórzano-Hamilton. “Your team’s strength is not a function of the talent of individual members. It’s a function of their collaboration, tenacity, and mutual respect.”
25 Hints You’re Working on a High Performing Team - by John Cutler. “You’ll frequently find teams with incredibly capable individuals…but they are not operating as a team. Similarly, teams exist in a broader system. A great team cannot function in a broken org. Also…sometimes a team is the black sheep. They’re struggling, but the org isn’t exactly helping.”
A Model for High-Performing Teams - by Simon Powers. “Building high-performance is just as much about building an environment that supports teamwork as it is building connections within the team. Both parts of the model must work together to make a high-performing team.”
Beyond OKRs: The Formula for High Performing Teams (Video) - by Christina Wodtke. “Every wonder if there was a better way to form and manage teams?”
Good Product Team / Bad Product Team - by Marty Cagan. “… in this article I wanted to try to give you a glimpse into some of the important differences between strong product teams and weak teams”
How to Build a High Velocity Development Team - by Eric Elliott. “You must eradicate your development team’s fear of change.”
Let Your Teams Plan for Themselves - by Luke Morton. “We decided recently to take a different approach; instead of removing developers from planning we decided to leave planning up to developers. We hoped this would allow teams to take more ownership of delivery. By having a higher level of understanding behind the problem we thought teams would be able to solve them better. We recognise that an increase in responsibility usually correlates to an increase in happiness and therefore performance.”
The 10 Practices of Healthy Engineering Teams – Part 1 - by Andrew Hao
The 10 Practices of Healthy Engineering Teams – Part 2 - by Andrew Hao
The 10 Practices of Healthy Engineering Teams – Part 3 - by Andrew Hao
The Best Teams Hold Themselves Accountable - by Joseph Grenny. “Our research shows that on top performing teams peers immediately and respectfully confront one another when problems arise.”
5 Dysfunctions of a Team: Absence of Trust - by CayenneApps
5 Dysfunctions of a Team: The Lack of Commitment - by CayenneApps
Why Is Genuine Teamwork Elusive? - by Crisp Apples. “If you could get all the people in an organization rowing in the same direction, you could dominate any market, against any competition. But the truth is that genuine teamwork remains elusive in most organizations, and team leaders and members fall unknowingly to the 5 dysfunction pitfalls.”
Part 2: Overcome the 5 Dysfunctions of a Team - by Crisp Apples. “… teamwork ultimately comes down to practicing a small set of principles (not a sophisticated theory) over a long period of time with uncommon levels of discipline and persistence.”