InfoQ Homepage Agile Conferences Content on InfoQ
-
Learnings from Applying Psychological Safety across Teams
Applying ideas from psychological safety can enable people to speak up in teams about what they don't know, don't understand, or mistakes they have made. Trust and creating safe spaces are essential, but more is needed. People need to feel that they will not be punished or embarrassed if they take interpersonal risks.
-
Testing Advanced Driver Assistance Systems
Advanced driver assistance systems can have a huge number of test cases. Cutting the elephant into smaller pieces can ensure every bit and piece is tested. A good test environment is essential to be efficient, fast and flexible to cover all required tests to ensure quality. Testers should be involved in the project right from the beginning to avoid task-forces, quality- or delivery problems.
-
How Defining Agile Results and Behaviors Can Enable Behavioral Change
Specifying and measuring behavior within a certain organisational context can enable and drive behavioral change. To increase the success of an agile transformation, it helps if you link the desired behaviors to the expected results. This way you set yourself up to be able to reinforce the behavior you want to see more of in order to reach your results.
-
Effective Retrospectives Require Skilled Facilitators
Retrospective facilitators can develop their facilitation skills by self-study and training, and by doing retrospectives. Better retrospective facilitation can lead to higher effectiveness of change and impact the progress of an organization.
-
How We Can Use Data to Improve System Quality
To understand how systems are being used, we can collect metrics and identify trends over time. The data and insights gained can be used to improve system quality by improving software design or testing patterns.
-
Applying Machine Learning for Business Outcomes at Travelopia
Travelopia changed its focus from a technology approach to business outcomes, and adapted agile and lean for delivering machine learning solutions. This enabled them to deliver machine-learning business models faster and better.
-
Scalable Automation Frameworks for Functional and Non-Functional Testing
Separating the capabilities of a testing framework from the actual tests can enable scaling automated testing for complex enterprise products. According to Alexander Velinov, we should agree on the types of tests to execute automatically during release and what should be kept as manually triggered tests.
-
The Myth of Product Mindset: It's What You Do, Not How You Think
Companies nowadays are looking for ways to cultivate a product mindset. While the idea of cultivating a “product mindset” allows us to focus primarily on ourselves, actually transforming our organizations often means changing our behavior to focus on our customers and how we work together to serve them.
-
Motivating Employees and Making Work More Fun
Progressive workplaces focus on purpose and value, having networks of teams supported by leaders with distributed decision-making. Employees get freedom and trust, and access to information through radical transparency that enables them to experiment and adapt the organization. In such workplaces, people can develop their talents and work on tasks they like to do, and have more fun.
-
Performance Testing Should Focus on Trends
Performance testing starts by setting a baseline and defining the metrics to track together with the development team. Nikolay Avramov advises executing performance tests and comparing the results frequently during development to spot degrading performance as soon as possible.
-
Reliable Continuous Testing Requires Automation
Automation makes it possible to build a reliable continuous testing process that covers the functional and non-functional requirements of the software. Preferably this automation should be done from the beginning of product development to enable quick release and delivery of software and early feedback from the users.
-
Technical Debt is Quantifiable as Financial Debt: an Impossible Thing for Developers
Technical debt can be quantified in various ways, but you cannot precisely quantify the associated financial debt. According to Kevlin Henney, we can quantify things like how many debt items we have, the estimated time to fix each debt item, a variety of metrics associated with our code, such as cyclomatic complexity, degree of duplication, number of lines of code, but not the financial debt.
-
Using Data to Predict Future Usage and Increase User Insights
By identifying usage trends, you can proactively adjust load, scaling, and routing to better handle the load on particular parts of the globe when you know it will peak there. Data about how users interact with your application can be used to design future features that better mimic these patterns and ensure that new features have a better chance of solving real user problems and getting adopted.
-
Establishing Autonomy and Responsibility with Networks of Teams
Working in outdated ways causes people to quit their work. Pim de Morree suggests structuring organizations into networks of autonomous teams and creating meaningful work through a clear purpose and direction. According to him, we can work better, be more successful, and have more fun at the same time.
-
How to Test Low Code Applications
For low code applications there are technical things you don’t have to test, like the integration with the database and the syntax of a screen. But you still have to test functionally, to check if you’re building the right thing. End-to-end testing and non-functional testing can be very important for low code applications.