InfoQ Homepage Culture & Methods Content on InfoQ
-
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 DesignOps Matters: How to Improve Your Design Processes
DesignOps is a combination of practices and a mindset that improves design workflow, facilitates designer-developer handoffs, enhances the way products and services are crafted, and enables projects to evolve at a faster pace. Design processes may be more complex, dispersed and chaotic than they should be. There are ways to adapt to digital transformation and establish well-functioning DesignOps
-
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.
-
How to Spark a Consumer-Grade UX Revolution
Turning end-users into advocates is one of the most powerful things SaaS companies can accomplish today. This can be a major project for a company, but it’s a revolution that can start small - and start today. Here we cover how to kick-off, manage, implement and iterate upon adding consumer-grade UX to the services that you own.
-
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.
-
Using DevOps Automation to Combat DevOps Workforce Shortages
A focus on automation can help to combat the current staffing struggles many organizations have with DevOps roles. Effective automation can reduce the toil experienced by developers. Automation efforts should focus on security operations, deployments, continuous delivery, QA testing, and continuous integration.
-
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 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.
-
It’s Time to Start Growing No-Code Developers
It’s time to start training and promoting people to be “business application no-code developers.” Why? Because everyone who manages a system is now a “developer,” whether they were trained that way or not. And if you don’t do this, your company will run into insurmountable problems when scaling its systems. Read this advice from a CTO on how your org can catch up.