InfoQ Homepage Collaboration Content on InfoQ
-
Transitioning to Modern Testing: How Testers Can Stop Being the Training Wheels for Teams
Traditional testing, where testers act as safety nets and testing is separated from implementation, can have a detrimental impact on quality. Testers can instead act as coaches, collaborate in teams, and foster change, to stop becoming the training wheels for teams. Culture is key, particularly in that the environment provides psychological safety.
-
Trust-Driven Development: Building Cognitive and Emotional Pillars
Trust-driven development uses authenticity to build a safe environment for people to operate. To build trust we need to focus on two main pillars of trust – cognitive and emotional. We need to be brave, have courage, and give people access to our authentic selves.
-
Improving Software Quality with Gamification
Bingo Bongo sessions for bug hunting and playing risk storming games can improve quality. Gamification supports learning, can make everyday work interesting, and strengthen team spirit. Playing games should be part of the daily work at the office and seen as an effective work time. In gamification, a real value is created by the creative process.
-
Using Team-Set Salaries for Company-Wide Compensation
Team-set salaries (TSS) can be scaled up by doing appraisals across teams where results are automatically calibrated. The scores indicate where conversations are needed. TSS encourages people to learn new skills and adapt.
-
Creating Tight Cohesive Tech Teams for Women to Thrive
Women in tech need a dynamic, valuing team, stimulating work, push and support, local role models, nonjudgmental flexibility, and personal power. Tight cohesive teams can provide high-quality interactions, making people feel valued.
-
Fair Individual Compensation for Agile Teams with Team-Set Salaries
Team-set salaries can be used to set fair compensation for individuals in multiskilled, collaborative, autonomous teams. People don’t appraise themselves, only their colleagues. It gives everyone a direct say in salary settings.
-
GitHub Codespaces Can Now Be Templated to Improve Performance
GitHub has introduced prebuilt Codespaces to reduce the time it takes to spin up a full development environment for large, complex projects.
-
Increasing Collaboration at Ericsson: Hardware and Software Developers Learn Each Other's Language
You can integrate hardware and software development with a cross-border team setup, where it’s important that hardware and software developers speak each other’s languages. The suggestion is to focus on “us” instead of “we” and “them”, and on the technical competence that connects developers over agile or lean terminology.
-
How to Work Asynchronously as a Remote-First SRE
The core practices for remote work at Netlify are prioritising asynchronous communication, being intentional about our remote community building, and encouraging colleagues to protect their work-life balance. Sustainable remote work starts with sustainable working hours, which includes making yourself “almost” unreachable with clear boundaries and protocols for out of hours contact.
-
Dealing with Cognitive Biases in Software Development
Cognitive biases help us to think faster, but they also make us less rational than we think we are. Being able to recognize and overcome biases can prevent problems and increase the performance of software teams.
-
How Mob Programming Collective Habits Can be the Soil for Growing Technical Quality
Mob programming can support teams in changing old habits into new effective habits for creating products in an agile way. Collectively-developed habits are hard to forget when you have other people around. Mob programming forces individuals to put new habits into practice regularly, making them easier to adopt. Teams are intolerant of repetition, looking for better ways of doing their work.
-
The Future of Agile in Africa: Challenges and Progress
The African continent is trailing behind in the adoption of agile compared to other continents as it faces wicked challenges and setbacks. However, the next two decades seem to be promising to the young continent, as tech startups, SMEs and large corporations are recognizing that a collaborative approach to product development leads to more productive and value-driven results.
-
How External IT Providers Can Adopt DevOps Practices
IT suppliers can follow the “you build it, you run it” mantra by working in small batches, using an experimental approach to product development, and validating small product increments in production. The supplier has to find out what his client’s goal is, and it has to become the supplier’s goal as well to work in a collaborative way.
-
Distributed DevOps Teams: Enabling Non-Stop Delivery
Keeping in touch and being cohesive as a distributed team is a challenge many face. Assigning stories from a shared backlog helped a distributed team in doing non-stop delivery, as did giving all members of the team the authority to promote to production and back-out code at need. You need to give attention to the architecture to prevent creating similar or duplicate micro-services.
-
Assessing Remote Employee Experiences for Hybrid-Remote Work-Settings
Employers and employees have begun to prepare for their return to the office. One of the options is a hybrid-remote work setting which aims to support individual preferences when it comes to where, when, and how to work. According to Kaleem Clarkson, assessing your remote employee experience can help to make decisions on workplace flexibility policies.