InfoQ Homepage Delivering Quality Content on InfoQ
-
Making Software Development Boring to Deliver Business Value
Given there’s a limit to our cognitive abilities and our comprehension of complex systems, Corstian Boerman argues that software development should become boring. He suggests moving infrastructure out of the way so that it does not burden the day-to-day development process, and focusing on delivering business value in a predictable and repeatable way.
-
How Moral Values and Ethics Impact Software Delivery
Ethics and morality ensure fairness and integrity, which according to Anton Angelov is crucial for software professionals and society. The rise of technological advances, globalization, and demographic changes pose challenges to maintaining moral values in software delivery. Angelov believes that it is crucial for the QA industry to have a strong ethical framework.
-
The Value of Repaying Good Technical Debt
Bad technical debt is the stuff that has been lingering around; teams need to work around it or fix the fallout as a consequence of this bad technical debt. Good technical debt is intentional, enables benefits for the organisation, and is controlled. Teams can use a disciplined approach for managing and repaying technical debt, for instance by using the wall of technical debt.
-
How Spotify Carries through Experiments at Scale for Spotify Home
Spotify runs more than 250 online experiments annually on its Spotify Home platform, which are used by dozen of different teams. To accomplish running experiments at such scale, Spotify uses a number of different tools, explains Spotify product manager Nik Goyle.
-
How to Assess Software Quality
The quality practices assessment model (QPAM) can be used to classify a team’s exhibited behavior into four dimensions: Beginning, Unifying, Practicing, and Innovating. It explores social and technical quality aspects like feedback loops, culture, code quality and technical debt, and deployment pipeline.
-
Helping Teams Deliver with a Quality Practices Assessment Model
The quality practices assessment model explores quality aspects that help teams to deliver in an agile way. The model covers both social and technical aspects of quality; it is used to assess the quality of the team’s processes and also touches on product quality. With an assessment, teams can look at where their practices lie within the quality aspects and decide on what they want to improve.
-
How Twitter Automated Data Quality Check Process
Twitter engineering has recently shared a blog post on how they architected and developed a quality automation platform. Twitter digests and creates thousands of data sets for different data products and applications. The next natural step is to make sure of the quality of the data by adding automation on top of it. In this news post, we explore this architecture in more detail.
-
Automating Software Quality Certification at eBay
The eBay Application Platform Team has started using Kubernetes Operators, Helm Charts and Jenkins to ensure software quality at the organization. In order to perform safe changes within the associated containers and environments, the team has created a self-service “certification” solution.
-
Shifting Quality Left with the Test Pyramid
Shifting quality left means building in quality much earlier in the software development cycle, rather than testing for quality after completion of development. Using the test pyramid model, a project was able to move testing towards earlier stages, thereby finding defects that caused integration issues earlier in development.
-
Agile Approaches for Building in Quality
Built-in quality is a core pillar in agile. However, if we want to build in quality at scale, we need to look at the whole development life cycle. Quality awareness needs to be increased at multiple layers of the organization; agile coaches can help by boosting quality thinking by embracing an agile way of working.
-
Deliver Faster by Killing the Test Column
Columns like "In test" often lead to teams having more work in progress and less work actually being finished. Removing such columns can increase collaboration between testers and developers and enable teams to deliver faster.
-
OverOps Releases Second Annual DevOps Survey
In their recent survey, OverOps, a continuous reliability platform vendor, found that within DevOps investment initiatives, organizations invest the most towards enabling the constant flow of software development. The survey also revealed that automated code analysis is being adopted more as engineering teams embrace cutting-edge technologies and practices.
-
What Made the iOS 13 Launch So Buggy and How to Fix the Development Process
Apple's latest iOS release, iOS 13, was affected by a number of bugs that caused disappointed reactions by users. In a story ran by Bloomberg, sources familiar with Apple explained what went wrong in the iOS 13 release process and how Apple is aiming to fix this for the future.
-
Experience Building a QA Team in a Growing Organization
Shifting the test team to the left brought the whole team closer together, enabled faster learning, and improved collaboration, claimed Neven Matas, QA team lead at Infinum. He spoke at TestCon Moscow 2019 where he shared the lessons learned from building a QA team in a growing organization.
-
Sustainable Software with Agile
Sustainable software enables you to deliver changes to the customer more quickly with a lower likelihood of bugs, decrease of the total cost of ownership of applications, and increase business agility. It’s possible to verify the sustainability of software using a combination of automated analysis of source code, expert review of technical artifacts, and comparison with benchmark data.