InfoQ Homepage Continuous Improvement Content on InfoQ
-
How Continuous Discovery Helps Software Teams to Take Product Decisions
Continuous discovery for product development is regular research that involves the entire software product team, and that can actively inform product decisions. Equating continuous discovery to weekly conversations with one or more customers can be misleading. Combining quantitative and qualitative research methods can help software teams gather data and understand what is behind the data.
-
Booking.com Doubles Delivery Performance Using DORA Metrics and Micro Frontends
The team in Booking.com’s fintech business unit implemented a series of improvements across the backend and the frontend of its platform and was able to double the delivery performance, as measured by DORA metrics. Additionally, the Micro Frontends (MFE) pattern was used to break up the monolithic FE application into multiple decomposed apps that could be deployed separately.
-
Embracing Complexity and Emergence in Organisations
Focusing on the actual emerging organisation and the work people are doing can make a difference in embracing complexity and dealing with it a bit better. Psychological safety is critical for people giving feedback without fearing retribution or negative consequences. Fred Hebert spoke about embracing complexity at QCon New York 2023.
-
A Culture of Continuous Experimentation: Learnings from QCon New York
At QCon New York 2023, Sarah Aslanifar presented Building a Culture of Continuous Experimentation. She showed how fostering a culture of continuous experimentation and leveraging the principle of continuous learning can drive efficiency, eliminate waste, and improve product outcomes.
-
Treat Your CI System as a Product for Faster and Better Feedback
Improving the feedback time of a continuous integration (CI) system and optimizing the test methods and classes resulted in more effective feedback for development teams. CI systems are an important part of the development process and should be treated as such.
-
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.
-
Improving Retrospective Effectiveness with End-of-Year and Focus Retrospectives
Doing end-of-year retrospectives can help to improve the effectiveness of agile retrospectives, by focusing on the actions done and the formats used. To increase the impact of retrospectives we can alternate between “global galactic” and focus retrospectives.
-
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.
-
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.
-
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.
-
Getting Feedback When Your Colleagues Are Also Your Customers
Getting and using feedback from colleagues who are also customers using your product can improve the quality of the product and help to improve the way of working. In this situation, it’s easier to receive feedback, but you can get overloaded by it.
-
How Getting Feedback from Angry Users Helps to Develop Better Products
Every time you change something in your product, angry users can show up. These users are engaged and they care about your product. Listening to them can help you find golden nuggets of user insight to improve your product.
-
How Removing Staging Environments Can Improve Your Deployments
Squeaky - a company which helps businesses to understand how visitors are using their website or web app without invading their privacy - have outlined why they don’t use a staging environment. They believe that this helps them to ship faster, and lower the number of issues found in production.
-
How Mob Programming Collective Habits Can be the Soil for Growing Technical Quality
Mob programming can support teams in changing old habits into new effective habits for creating products in an agile way. Collectively-developed habits are hard to forget when you have other people around. Mob programming forces individuals to put new habits into practice regularly, making them easier to adopt. Teams are intolerant of repetition, looking for better ways of doing their work.
-
How a Test Strategy Helped to Increase Deployment Maturity and Product Quality
Implementing a test strategy helped an organization to move away from push and pray deployment toward continuous and confident deployment to production. The organization mapped their test strategy in a framework with different enablers, which has helped them align on quality metrics for the whole product together with a strong safety net of tests before moving to production.