BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Collaboration Content on InfoQ

  • 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.

  • Distributed DevOps Teams: Supporting Digitally Connected Teams

    To establish a digital connection within a globally distributed team, an organization provided the team members with both collaboration tools and supplied an extra monitor with a visualization board. Collaboration using the online chat and white board initially posed challenges, as the board was tweaked towards the teams’ needs.

  • How to Improve Your Team's Communication and Psychological Safety

    Mapping your team’s typical communication style can help improve communication and psychological safety, reduce friction within a team, and make conflict more productive. When we understand how we communicate and how we like to be communicated with, we not only have a better understanding of ourselves, but also of others, and this can play to our and their strengths accordingly.

  • How Testers Can Contribute to Product Definition

    Utilizing the tester’s feedback during product definition and design is valuable for the business. Listening to the organization's needs, understanding the business goals, and customizing the test process by incorporating different skills and practices is one way testing can begin while the product is still "on paper".

  • The Impact of Radical Uncertainty on People

    Humans look for certainty as that makes them feel safe. Suddenly becoming an entirely distributed team due to the pandemic disrupted people. According to Kara Langford, radical uncertainty can cause people to believe they are in danger and lead to health issues. People will respond differently; uncertainty has also shown to lead to fresh ideas, innovations, and social good.

  • Variations on New Normal for Workplaces

    Over the last year office work has shifted to almost completely remote, and as vaccination programs roll out around the world it is shifting again. There is a lot of speculation around what the new normal will look like. Employee well-being, flexibility in working arrangements, availability creep, virtual and augmented reality are all factors impacting what work could look like going forward.

  • Fostering Cross-Cultural Collaboration

    Building intercultural relationships are so important to success in the workplace and world today, yet many people are hesitant or unsure of how to build relationships with those who are different from themselves. The first step is to reflect on yourself and notice where and how you spend your time and resources.

  • Virtualizing Design Sprint and UX Workshops

    Design sprint and UX workshops can be done virtually using a combination of remote whiteboards and communication platforms. It brings advantages like being able to invite international experts, having remote participants attend, less travelling, smaller carbon footprint, and lower costs.

  • Paving the Road to Production at Coinbase: QCon Plus Q&A

    As Coinbase scaled both their number of engineers and customers, they needed more projects, faster iteration, and more control over their growing infrastructure. In developing their in-house deployment tool by looking at what developers were doing and trying to help them, they created a culture of self-service.

BT