InfoQ Homepage Articles
-
Characteristics of a Great Scrum Team
This article explores 'What makes a great Scrum team?' by offering detailed descriptions of the characteristics and skills needed in the Scrum roles of Product Owner, Scrum Master and Development Team.
-
Continuous Deployment with Containers
Many of us have already experimented with Docker - for example, running one of the pre-built images from Docker Hub. However, a comprehensive build pipeline is required before deploying any containers into a production environment. This article outlines the steps you need to take for a fully automated continuous-deployment pipeline that builds microservices deployed via Docker containers.
-
Ten Ways to Successfully Fail your Agility
This article is intended for newbies and agile sceptics who want to challenge their take on agile. It provides 10 ways to successfully fail your agility, implying that by replacing these practices with ones that do the opposite, you will increase agility and improve the odds of being successful.
-
State of the JavaScript Landscape: A Map for Newcomers
Modern JavaScript development is in constant motion. Build tools that were popular 12 or even six months ago are no longer en vogue. In this article, Bonnie Eisenman gives JavaScript newcomers a map to get started on their JavaScript journey. For more experienced JavaScript developers, Bonnie provides an update on where the community is at and what technologies to use for new projects.
-
IBM's Swift on the Server
Since Swift's open-source release, IBM has been working on the project and providing libdispatch on Linux, as well as providing a Swift web-based runtime and a managed catalog of Swift projects. InfoQ spoke to Chris Bailey and Patrick Bohrer, who presented at QCon London 2016, and asked them where they see Swift going in the future.
-
Lessons Learned from Scheduling One Million Containers with HashiCorp Nomad
HashiCorp's Million Container Challenge is a test for how efficiently its scheduler, Nomad, can schedule one million containers across 5,000 hosts. The goal of the challenge is to observe and optimize the behavior of Nomad at exceptional scale. Ultimately Nomad was able to schedule one million containers across 5,000 hosts in under five minutes. This post outlines the lessons learned.
-
Q&A on the Scrum Field Guide - 2nd Edition
The Scrum Field Guide - 2nd Edition by Mitch Lacey is a "what to expect" book for organizations transitioning to agile, which aims to help teams to deal with issues that occur and fine-tune their own implementation. An interview about the essentials of Scrum, sprint length, full time Scrum masters, making time available for solving defects, preventing bad hires, and increasing benefits from Scrum.
-
Build Your Own Offshore Development Team - or Not?
When you absolutely positively MUST build your own offshore dev team to get the quality you need, consider NOT. There is an argument for ‘owning’ vs ‘renting’ when it comes to leveraging an offshore dev team, the author disagrees with the idea that building one’s own team is better than outsourcing the job. He knows what it takes to do it right, and it isn't easy.
-
Key Takeaway Points and Lessons Learned from QCon London 2016
This article summarizes the key takeaways and highlights from QCon London 2016 as blogged and tweeted by QCon's 1,400 attendees. Over the course of the next 4 months, InfoQ will be publishing most of the conference sessions online, including 21 video interviews that were recorded by the InfoQ editorial team.
-
0 Bugs Policy
Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.
-
C#/Web API Code Generation Patterns for the RAML User
In this article, Jonathan Allen outlines the design patterns that users of REST specification languages such as RAML, Swagger, and API Blueprint should adhere to when generating code for C# and ASP.NET Web API. This includes topics such as model validation, async support, and request cancellation.
-
Test Management Revisited
The concept of test management sits awkwardly in agile, mostly because it’s a construct derived from the time when testing was a post-development phase, performed by independent testing teams. Agile, with its focus on cross functional teams, has sounded the death knell for many test managers. While test management is largely irrelevant in agile, there is still a desperate need for test leadership.