InfoQ Homepage Agile Content on InfoQ
-
The Battle for Talent Can Be Won with Employee Recognition
In response to retaining high performers during an impending recession, employers need to prioritize giving employees recognition to increase retention and engagement. This article explores the power of recognition, what makes recognition meaningful, and how companies can create a culture of recognition in their workplace.
-
Rules of Thumb & Traps When Approaching Tech Stack Decisions
At the MVP stage - do only the stuff you would do in a hackathon. Scalability and processes will become important once we have predictable revenue streams. Where are you generating your unique value proposition? Outsource all aspects of the tech solution which are not in a relationship with your competitive advantage. Follow a general tech directive but balance it with the team's autonomy.
-
Infrastructure as a Code—Why Drift Management Is Not Enough
The reality is that configuration drift will remain unavoidable for the foreseeable future. An EaaS solution, coupled with an IaC platform and good change management policies will help you prevent drift and shorten your development cycles.
-
How Open Source is Contributing to Your Team’s Development: What Leaders Should Know
Today’s open source landscape plays a critical role in the developer journey and in business as well. This piece examines common barriers to contribution, how businesses benefit from open source, and what it may look like for businesses to help prioritize open source contribution among their employees.
-
Talking about Sizing and Forecasting in Scrum
Scrum Teams can use different approaches to size the effort to deliver a Sprint/Product Goal. The forecast will be wrong. We're moving one Sprint at a time, and refreshing forecasts frequently. Some would say, "Discover and deliver capabilities—review outcomes with the customers and end-users. Learn what can be learned. Act on what we have discovered. Don't manage expectations."
-
Why DevOps Governance is Crucial to Enable Developer Velocity
The application environment should be managed centrally by the DevOps team. This allows them to better track modifications and changes which would then be swift and transparent to developer teams.
-
Scaling and Growing Developer Experience at Netflix
An optimal Developer Experience will depend a lot on the company the developer is working for. This article discusses why and when changes to developer needs will occur, how to get ahead of them, and how to adapt when these changes are necessary. I talk through some of the experiences myself and peers have had at Netflix, identifying some key learnings and examples we have gained over the years.
-
Open-Source Testing: Why Bug Bounty Programs Should Be Embraced, Not Feared
The growing importance of the Web3 ecosystem based on blockchains shows how important community test programs are. Some within the testing community see this trend as a threat. However, it is actually an opportunity. Bug bounties and open-source test contributions are a great tool for test teams, and there is every reason for testers to embrace this new trend rather than to fear it.
-
The Four P's of Pragmatically Scaling Your Engineering Organization
Scaling your organization during a period of hyper-growth is a challenge every founder wants to face. For engineering leaders, the concept of "scale" can quickly spiral out of control. There are four key areas of focus when pragmatically scaling an organization through hyper-growth: people, process, product, and platform.
-
Transitioning into the Staff+ Engineer Role - from Player to Coach
This article describes how staff+ engineers transition to supporters, enablers and force multipliers of others and what technical leadership looks like away from the management track. It explains the benefits organisations get by having leadership roles that are focused on technical enablement and support.
-
How Development Teams Can Orchestrate Their Workflow with Pipelines as Code
Infrastructure as Code was just the beginning. Configuration as Code followed shortly after – again becoming extremely commonplace and enabling organisations to scale their engineering capacity by a number of times. And in order to continuously increase the value development teams generate, Pipelines as Code is the natural consequence.
-
How to Introduce Innovation into the DNA of 21st Century Companies
An innovation mindset is about the tiny little improvements any employee can do; hundreds of simple, low-cost- no-effort activities are in plain sight just waiting for somebody to deploy them. This article provides guidelines that can support you in changing the attitude of employees in your organization providing trust, time, space, teams, a second operating system, MVPs, and co-creation.