InfoQ Homepage Culture & Methods Content on InfoQ
-
/articles/go-language-13-years/en/smallimage/go-language-anniversary-steve-francia-logo-small-1609168280799.jpg)
Go Language at 13 Years: Ecosystem, Evolution, and Future in Conversation with Steve Francia
Go was started more than a decade ago in the Engineering department at Google. It was designed with the purpose of providing an easy-to-learn programming language that would allow to develop Google's systems at the next level. In the past decade, the language became more and more stable, currently being used for implementing some of the most popular tools on the web (Kubernetes, Terraform etc.).
-
/articles/metrics-team-dependability/en/smallimage/metrics-team-dependability-s-1609150308847.jpg)
Key Sprint Metrics to Increase Team Dependability
What are the questions you should be asking and what behaviours should you be measuring within your Scrum teams in order to improve overall dependability and delivery efficiency? We explore how you can transform your Sprints into the building blocks for success and ensure you can continue to meet (and even surpass) long-term user and business expectations.
-
/articles/2020-recap-best-posts/en/smallimage/2020-recap-100px-1608641842348.jpg)
InfoQ 2020 Recap, Editor Recommendations, and Best Content of the Year
As 2020 is coming to an end, we created this article listing some of the best posts published this year. This collection was hand-picked by nine InfoQ Editors recommending the greatest posts in their domain. It's a great piece to make sure you don't miss out on some of the InfoQ's best content.
-
/articles/book-review-retrospectives-antipatterns/en/smallimage/Retrospectives_Antipatterns_logo-small-1608656504479.jpg)
Q&A on the Book Retrospectives Antipatterns
Using the familiar “patterns” approach, the book Retrospectives Antipatterns by Aino Vonge Corry describes unfortunate situations that can sometimes happen in retrospectives. For each situation, described as an antipattern, it also provides solutions for dealing with the situation; this can be a way to solve the problem directly or avoid similar problems in future retrospectives.
-
/articles/changes-2020-Scrum-guide/en/smallimage/changes-2020-scrum-guide-schwaber-sutherland-logo-small-1608561536355.jpg)
Changes in the 2020 Scrum Guide: Q&A with Ken Schwaber and Jeff Sutherland
The Scrum Guide has been updated to make it less prescriptive, using simpler language to address a wider audience. These changes have been done to make Scrum a “lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems”. An interview with Ken Schwaber and Jeff Sutherland about the changes to the guide.
-
/articles/think-lawyer-scientist-engineer/en/smallimage/lawyer-scientist-engineer-1608224787782.jpg)
Do You Think Like a Lawyer, a Scientist, or an Engineer?
Law, science, and engineering offer three distinct approaches to logical thinking. Each is important in different circumstances, and in practice, we can use all three. How much understanding and control do you have of a situation? Do you simply need to follow the rules? Are you operating in a world of uncertainty and volatility? Or are you building and defining the rules as you go along?
-
/articles/agile-teams-organization/en/smallimage/agile-teams-organization-s-1607704300549.jpeg)
Moving from Agile Teams towards an Agile Organization
For organizational agility, we need to improve the system for teams and individuals to thrive, instead of expecting them to change and fix the culture. This article explores some elements from a systemic point of view that are essential to create the right conditions for moving from agile teams towards an agile organization.
-
/articles/remote-team-challenges/en/smallimage/dealing-with-remote-team-challenges-logo-small-1607337349621.jpg)
Dealing with Remote Team Challenges
Remote working provides challenges such as providing equitable access, ensuring adequate resources and tooling, addressing social isolation and issues of trust. Remote-first and truly asynchronous teams tend to consistently perform better. In the future, organisations will continue to have remote on their agenda. Fully realising the benefits of remote teams requires trust building and intent.
-
/articles/book-review-cyber-securities/en/smallimage/cybersecurity-logo-small-1607015545941.jpg)
Q&A on the Book Cybersecurity Threats, Malware Trends and Strategies
The book Cybersecurity Threats, Malware Trends and Strategies by Tim Rains provides an overview of the threat landscape over a twenty year period. It provides insights and solutions that can be used to develop an effective cybersecurity strategy and improve vulnerability management.
-
/articles/product-management-ownership-complexity/en/smallimage/complexity-s-1607013693453.jpeg)
The Complexity of Product Management and Product Ownership
Doug Talbot discusses the confusion surrounding Product Ownership / Product Management. He provides some advice on tackling the complexity of creating your own contextualised and personalised product value stream for your organisation or team and using systems thinking and Cynefin for complexity.
-
/articles/book-review-virtual-distance/en/smallimage/logo-1606766502356.jpg)
Q&A on the Book The Power of Virtual Distance
The book The Power of Virtual Distance, 2nd edition, by Karen Sobel Lojeski and Richard Reilly, describes the Virtual Distance Model and provides data and insights from research that can be used to lower Virtual Distance when working remotely together. By doing so, organizations can see quantifiable improvements in both business goals and human well-being among employees.
-
/articles/transformation-by-imagining-it-had-failed/en/smallimage/KICK-OFF-S-1606304485976.jpg)
Kick-off Your Transformation by Imagining It Had Failed
Large scale change initiatives have a worryingly high failure rate, the chief reason for which is that serious risks are not identified early. One way to create the safety needed for everyone to speak openly about the risks they see is by running a pre-mortem. In a pre-mortem, we assume that the transformation had already failed and walk backward from there to investigate what led to the failure.