InfoQ Homepage Teamwork Content on InfoQ
-
Best Practices for Letting Go of a Remote Team Member
At Doist, letting go of a team member is a last resort. Over 14 years, the remote-first pioneer has parted ways with approximately 25 team members, which has evolved the way they handle remote terminations. Today, Doist employs 100 people in 35+ countries with a 90+% employee retention rate. Here COO Allan Christensen offers his lessons learned on letting go of a remote team member.
-
Hybrid Work is Here to Stay, and Software Teams Need to Adapt
In a post-pandemic workplace, face-to-face conversation is no longer the de facto collaboration method. As hybrid and distributed software development teams emerge, we look at ways that tools and processes can foster collaboration no matter where the team is located. Asynchronous work, a single source of truth, clear documentation and owners, and automation will empower hybrid development teams.
-
Resetting a Struggling Scrum Team Using Sprint 0
Sprint 0 can be a great mechanism in Agile transformations to reset existing teams which are not delivering value, exhibiting a lack of accountability, or struggling with direct collaboration with customers. This article shares the experiences from doing a Sprint 0 with an existing team which was struggling to deliver, helping them to align to a new product vision and become a stronger team.
-
Essential Soft Skills for IT leaders in a Remote World
Leading teams is always challenging, especially when your team is remote; it requires more effort and more skills to be developed. This article describes the skills needed if you would like to become not just a good team leader, but a great one. To start, here are three essential soft skills: be vulnerable and authentic, build a collaborative and safe environment, and provide candid feedback.
-
How to Enable Team Learning and Boost Performance
Team performance is dependent on safety, teamwork and ongoing learning. Clarity in roles, psychological safety, breaking bad habits and constantly learning are critical to enabling high performance.
-
Improving Testability: Removing Anti-Patterns through Joint Conversations
Code is always testable, but the cost may be high, and the effort exhausting. We can change code to be highly testable by identifying anti-patterns and fixing them. And developers can make the code fit the test requirements, by having discussions with the testers who actually test it.
-
How to Recognise and Reduce HumanDebt
We know TechDebt is bad; chances are HumanDebt is worse, and once you’ve seen it, you can’t “unsee” or ignore it. What is now needed is a focus on the humans who do the work. Psychological safety in teams is key. The “people work” -both at an individual, but especially at a team level- is the key to sustainability and growth of high-performing tech teams.
-
How to Work Better Together: Building DEI Awareness in Tech
We have a diversity problem in technology. Many of our visions and standards of success are centered around one group of people, even though there are many groups contributing to global advancement and growth. The main reason for this is legacy, similar to legacy code. We can overcome this inherited debt by educating ourselves and planning time to do work to rebuild and replace our “legacy code”.
-
Outcome Mapping - How to Collaborate with Clarity
To truly improve, organizations need to deliver change to people, process, and tools. To make change effective, they need to identify where that change is needed, what the map of their current state looks like, and what is the best next step to make progress. Outcome mapping helps align teams to a clear goal, gain an understanding of the landscape, and develop a clear plan of action.
-
DEI Is Rooted in Justice: Stop Making it about Profit
Diversity, equity, and inclusion practices exist for the betterment of every single person within a company from the ground floor to the glass ceilings. Don't build a case for diversity, equity, and inclusion. You are an establishment that depends on other humans to operate your business and bring success. Their sense of belonging, inclusion, and psychological safety is your direct responsibility.
-
Facilitating Feedback That's Psychologically Safe
This article focuses on feedback with regards to a plan or proposal - ways to make it easier to give and receive feedback, so the psychological safety of the team can increase. The aim is to give you insights, models, structures and practical things to try, in order to facilitate feedback that boosts psychological safety in your team(s).
-
Augmenting Organizational Agility Through Learnability Quotient (LQ) - an Architect’s Perspective
By creating a robust learning framework for the organization, and involving architects and other key technical leaders, Halodoc improved their organizational agility.