This article series explains how containers are actually being used within the enterprise. It dives into the core technology behind containers and how this is currently being used by developers, examines core challenges with deploying containers in the enterprise and the future of containerisation, and discusses the role unikernels are currently playing within leading-edge organisations.
Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.
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.
This article outlines the steps needed for the creations of a fully automated continuous-deployment pipeline that builds microservices deployed via Docker containers. 2
This article provides 10 ways to successfully fail your agility. By replacing these practices with ones that do the opposite, you will increase agility and improve the odds of being successful.
InfoQ spoke to Chris Bailey and Patrick Bohrerand asked them where they see Swift going in the future.
HashiCorp's Million Container Challenge is a test for how efficiently its scheduler, Nomad, can schedule one million containers across 5,000 hosts. This post outlines the lessons learned.
The Scrum Field Guide - 2nd Edition 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.
When you absolutely positively MUST build your own offshore dev team to get the quality you need, consider NOT. The author knows what it takes to do it right, and it isn't easy. 3
This article summarizes the key takeaways and highlights from QCon London 2016 as blogged and tweeted by attendees.
Gal Zellermayer describes a process for handling bugs 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. 2