InfoQ Homepage Teamwork Content on InfoQ
-
Learnings from Discussing Developer Enablement at QCon London
Developer enablement can increase the potential of individuals in small and larger companies. Where individuals can have their own solutions, there will be things that are mandatory for all. Metrics can help to see what is being used or not. Be careful about supporting developer enablement for legacy systems; if it’s outdated and needs to be replaced then it might be better to not invest in it.
-
How Developer Enablement Brings Benefits to Software Organizations
Developer enablement is about tools and approaches that can greatly increase the potential we can have as individuals. It can have an impact on productivity and happiness, on profits and retention. Developer tools make it easier for engineers to deploy products, enabling them to focus on building a product.
-
How to Prepare an Agile Business Game
To make playing games "interesting" from the business owner's perspective, we need to ensure that they are aligned with the business needs. There are four steps in preparing a game: exploring the context, knowing your target group, defining the focus, and deciding how to facilitate it.
-
Becoming an Effective Staff-Plus Engineer
To increase your effectiveness as a staff-plus engineer, it can help to develop your communication, listening, technical strategy, and networking skills. Blanca Garcia Gil presented Five Behaviours to Become an Effective Staff-Plus Engineer at QCon London 2022 and will present at QCon Plus May 10-20, 2022.
-
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.
-
Making On-Call Less Painful for Developers by Using High-Quality Alerts
On-call is an increasing reality for developers. Improving alerts to reduce noise, automation, and removing warnings can help to make on-call work more humane. A driving force behind automation is Infrastructure as Code. Over time you can abstract that code so that it fits other use cases, which helps propagate best practices.
-
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.
-
Scaling Software Architecture via Conversations: the Advice Process
Andrew Harmel-Law recently published an article describing a decentralised, scalable software architecture process based on the "Advice Process". The Advice Process promotes software architecture by encouraging a series of conversations driven by an empowering, almost anarchistic, decision-making technique. It comprises one rule - anyone can make an architectural decision.
-
Shifting to Asynchronous Communication in Software Teams
As some companies begin to go back to the office and embrace hybrid working, they are at risk of alienating those who wish to remain remote, which is looking to be a considerable number of workers in our industry. James Stanier suggests using more asynchronous means of communication and spending more time writing to each other rather than speaking in meetings.
-
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.
-
Will the Hybrid Work’s Great Paradox Be the Decade’s Challenge?
The pandemic moved the office home, and while the medical system is trying to eradicate it allowing us to resume our lives as we know them, we also need to understand what the new normal will be. While some leaders will return to the office as soon as it is allowed, others adopt a fully remote approach as the main-approach. Probably a hybrid approach would be the new normal for most of us.