InfoQ Homepage Communication Content on InfoQ
-
Great Engineering Cultures and Organizations - Afternoon Sessions from QCon London
The Building Great Engineering Cultures and Organizations track at QCon London 2018 contained talks from practitioners representing digital leaders of the consumer internet as well as transformational corporates from “traditional” sectors. Previously InfoQ published a summary of the morning sessions; this is the summary of the afternoon sessions of this track.
-
Dealing with the Broken Human Machine: How to Create High-Performing Teams
To really progress in developing software and build anything at a scale, you have to examine your blind spots and learn to deal with people. The culture we build is important: the difference between a high performing engineering team and a low performing one is orders of magnitude in terms of productivity and quality. Focusing on how we do things is as important as what we’re doing.
-
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.
-
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.
-
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.
-
Scaling Scrum to Build a New-Technology Printer
When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.
-
Rethink Leadership: Being Ordinary to Accomplish Extraordinary Results
Ordinariness in leadership can help us to accomplish extraordinary results, argues agile/lean coach Katherine Kirk. Several more people have explored approaches that suggest to rethink leadership and go back to behaviour basics for leading people. Although these approaches are about small ordinary things, their effect may cause a revolution in the way organizations are being managed.
-
Agile in Dispersed or Distributed Teams
Cross-cultural team building enables collaboration and teamwork in dispersed or distributed agile teams. You need to invest to get the best out of a dispersed team. An exploration about what is needed to make agile work with dispersed or distributed teams.