InfoQ Homepage Distributed Team Content on InfoQ
-
Making Our Language and Behaviour More Inclusive
To avoid excluding people, we need to gain more awareness when we are in the wrong and be introspective to find out why someone is upset or offended by what we have said or done. By being excluded, people will eventually leave their jobs, communities or profession, which is something that we need to prevent. Peter Aitken suggested taking a positive approach when addressing inclusion issues.
-
The Industry Just Can't Decide about DevOps Teams
The incidence of DevOps teams is on the rise according to reports, but the industry remains divided on whether a DevOps team should even exist. Some are wary of creating additional silos, or are of the opinion that DevOps is a methodology that everyone should subscribe to in an organisation; others point to DevOps teams as an effective way of transitioning to a new way of working.
-
How Blogging Empowers Agile Teams
Moving the thinking and decisions a team makes from people’s inboxes onto a blog can make it accessible to all, findable in the future, and referenceable by everyone. Instead of writing documentation, you can use blogumentation to transfer knowledge and document the history of projects that provide context to the code.
-
Q&A with Aurynn Shaw on Sharing Her Personal DevOps Journey at DevOpsDays NZ
Raf Gemmail speaks with Aurynn Shaw about her upcoming DevOpsDays NZ talk and the humanist side of DevOps.
-
Tackling Technical Debt at Meetup
Continuous product health can be realized by regularly prioritizing the highest impact technical debt items and knocking those off systemically. You need to continuously iterate how you're tackling technical debt to drive more and more impactful results. Going for maximum impact items first and communicating the impact of paying down technical debt is what Yvette Pasqua, CTO of Meetup, recommends.
-
First Annual Retrospective Report Published
The First Annual Retrospective Report provides a deeper understanding of how retrospectives are used in the real world. The results indicate that retrospectives lead to improved team communication and productivity and help to create an environment of trust. Major challenges are that topics discussed cannot be solved by the team and people do not feel comfortable speaking up.
-
Better Engineering via Better Discourse
Killing opposition with kindness is a real strategy in online discussions; there is power to disarm in acting as if the other party did not intend to be insulting or condescending. Accept that there will be bias in online communication, use facts and reason to deal with it, and practice awareness of bias and attempt to compensate.
-
QCon New York – Optimizing Yourself Track
Day 3 of QCon New York had a track focused on how individuals can build non-technical competencies. Titled Optimizing Yourself, the track had five talks covering a wide range of personal skills from empathy to communication, remaining relevant as an older person in tech, deep listening and working remotely.
-
QCon New York Day 1 – High Velocity Development Teams Track Summary
QCon New York was heeled this week. This is a summary of the key messages from the opening keynote and from the High Velocity Development Teams track.
-
How the Financial Industry Is Doing DevOps
The second DevOps Enterprise Summit (DOES) Europe, once again held in London, brought together the DevOps enterprise community. The financial industry was well represented, giving the attendees a unique perspective on the challenges facing this heavily regulated industry and how DevOps is helping to address them.
-
Fearless Feedback for Software Teams
Feedback builds trust, increases team cohesion, and helps individuals to improve their skills and grow in their craft. An effective feedback cycle is the best possible tool for improving team performance. With feedback, issues are addressed before they become toxic and mistakes can be course-corrected early on.
-
Atlassian Opens up Team Health Monitors and Team Playbook Blueprints
After introducing a tool-agnostic version of its Team Health Monitors at Summit 2016, Atlassian now also bundles Team Playbook blueprints with the recently released Confluence Server 6.1. A Health Monitor workshop is a team self-assessment aiming to identify pain points and formulate a plan to address weak spots by running low-ceremony "plays" that "can help improve a team's overall health".
-
Michael Nir on Conduct Objectives for High Team Performance
Michael Nir will give a talk at the upcoming Agile Games conference titled "Bring the Scrum Master a Glass of Water: Conduct Objectives for High Performance Team". InfoQ spoke to Nir about the goal of Conduct Objectives, the way to measure behavior, the common problem with the appreciation of personalities, how to use a Team Charter, and the link with Core Protocols.
-
3 Years of the Merit Money System, a Revolution on the Recognition Methods Proposed by Cláudio Pires
Back in 2014, Cláudio Pires, a CEO in the healthcare business, implemented an alternative employee recognition method, the Merit Money System. Three years later, InfoQ challenged him to talk about the wins, the pitfalls and the lessons learned so far.
-
Making Distributed Development Work
Distributed development depends on effective communication: you need to look for ways to have robust and diverse communication, build empathy towards each other to encourage feedback, and keep an eye on motivation. Team members are more engaged and creative when there’s shared ownership and responsibility for complete delivery from idea to production in distributed teams.