InfoQ Homepage Culture & Methods Content on InfoQ
-
Adopting Asynchronous Collaboration in Distributed Software Teams
Meetings can be a major time-sink for distributed teams. While they can be valuable, if we reach for them as a default way of working, we inadvertently create a fragmented team calendar. This can be a drain on productivity, especially for knowledge workers who need time to focus on deep work. This article discusses the benefits of asynchronous collaboration and how to implement it on your team.
-
How to work with Your Auditors to Influence a Better Audit Experience
It is possible to influence a better audit experience, transforming it from a check-the-box exercise with little perceived value to one of true value that helps set you up for success, and with way less pain. This article explores how to experiment with adding agility into audit work while auditing a client, which can lead to better outcomes for you and your auditors.
-
Agile Coaching as a Path toward a Deeper Meaning of Work and Life
In this article, we take a deeper look at the practice and purpose of agile coaching. We find out why interactions are the most essential focus in agile coaching - and also the basis of learning and professional development for the agile coaches themselves. We also learn how focusing on our existing strengths and situations can help us discover our authentic purpose in work and life.
-
Beyond the Numbers: Decoding Metrics for Assessing Client-Side Engineer Impact
This article will delve into metrics that can be used for assessing the impact of client-side engineers. Our aim is to provide a more comprehensive perspective that can be useful when developing performance assessment guides for organizations building full-stack software, ensuring a more balanced and fair evaluation of engineers’ contributions and impact.
-
Agile Rehab: Replacing Process Dogma with Engineering to Achieve True Agility
Struggling with your "agile transformation?" Is your scaling framework not providing the outcomes you hoped for? In this article, we’ll discuss how teams in a large enterprise replaced heavy agile processes with Conway’s Law and better engineering to migrate from quarterly to daily value delivery to the end users.
-
How to Sustain Quality and Velocity in a JavaScript or TypeScript Project?
The JavaScript language and its ever-changing ecosystem of packages and practices can make codebases quickly become hard to maintain. The resulting loss of development velocity and/or code quality can be prevented without rewriting everything from scratch, nor pausing the development of new features. In this article, we have analyzed a few best practices to help avoid that.
-
How Agile Teams Can Improve Predictability by Measuring Stability
In this article, we will present our approach for analysing agile systems as networks of queues and how we have used it to analyse 926 projects in the Public Jira Dataset. We explain how you can measure the Stability Metric (SM) for your queues. Finally, we will present our planned next phase of research.
-
User Story: a Placeholder for a Conversation
User stories are meant to be a placeholder for a conversation. This article dives into the differences between user stories and tickets, where stories came from and how recent trends are moving us away from conversations. It shows the impact this is having on product development and easy ways to improve collaboration through conversation and writing better stories.
-
Bridging Silos and Overcoming Collaboration Antipatterns in Multidisciplinary Organisations
There's a worrying trend towards focusing on specialisms at the expense of collaboration, shared responsibility and valuable outcomes, which can take teams away from multi-disciplinary collaboration. This article calls out three collaboration anti-patterns that appeared in more than one organisation, some of the symptoms they cause and some thoughts on how to go about counteracting them.
-
Why Developers and Staff+ Engineers Should Get Involved in Open-Source Collaborative Development
Over the last 30 years, the world has become connected and digital. Open source is how we do modern software development, stitching together downloaded open-source libraries, frameworks, and other code to create new applications or functionality. This is why every developer and senior staff+ roles need to know what open source is and how it works.
-
Managing the Carbon Emissions Associated with Generative AI
There’s an increasing concern about the energy use and corresponding carbon emissions of generative AI models. And while the concerns may be overhyped, they still require attention, especially as generative AI becomes integrated into our modern life. Factors such as model architecture, transparency and quantization of models are required to decrease carbon emission from AI systems.
-
Reducing Verification Lead Time by 50% by Lowering Defect Slippage and Applying AI/ML Techniques
Can we increase our flexibility? Can we increase our test coverage? Can we increase our efficiency? And is it possible to reduce our verification lead-time by 50%? One company challenged itself with these questions. This article explores two important “‘pillars”’ of their testing strategy: shifting left and using state-of-the-art techniques to support verification activities.