InfoQ Homepage Culture & Methods Content on InfoQ
-
Scaling Agile - Slice and Understand Together
This second article in the series about making scaled agile work digs into how to slice requirements. If this is done right, it will not only result in good slices, but also a common understanding of the product we’re about to build or enhance.
-
Agile at Red Hat
This article is a story of the conversion journey from FeedHenry, a startup from Waterford, Ireland, into Red Hat. It’s also charting the journey of agile as a whole in Red Hat, as this story is being replicated across the product suite that Red Hat offers.
-
Customize Your Agile Approach: Select Your Agile Approach That Fits Your Context
This is the first in a series of articles that will help you think about how you might want to customize your agile approach for your context. This article explores how to make agile approaches work for you: your work, your team, and your organization. It's about understanding the difference between iteration, flow, and cadence and when you might consider each to customize your agile approach.
-
Defining Cloud Native: A Panel Discussion
What is "cloud-native", why should you care, and how can your team adopt this way of delivering software? InfoQ gathered three industry experts to debate the topic.
-
Q&A on the Book Executive’s Guide to Disciplined Agile
The Executive’s Guide to Disciplined Agile explains how disciplined agile works at different levels in the organization. It provides a framework with principles and practices to help you to streamline information technology and business processes in a context-sensitive manner.
-
Retiring Mainframe Programmers: Should I Care?
We stay up on new languages, frameworks, and architectures yet ignore the value of mainframe applications. Mainframes manage 70% of the world’s transactions yet its programmer workforce is rapidly retiring baby boomers. And millennials have no interest in mainframe careers. This article describes that state of mainframe applications, bad talks management, and then provides detailed solutions.
-
Offshoring Agile When You Are a Startup
Working with an offshore partner becomes faster and cheaper as communication technologies continue to improve. It is possible to achieve agility with an offshore team as long as you understand the limitations. Although some of the principles from the agile manifesto are difficult to reconcile with offshoring, they can still be used as guidance to work effectively together.
-
Q&A on "The Complete Software Developer's Career Guide"
The Complete Software Developer's Career Guide answers questions that new and experienced developers often have in advancing their careers. Topics covered vary from learning technical skills, getting a job, and dealing with managers, to doing side projects or starting your own company.
-
Scaling Agile – a Real Story
This is the first in a series of articles about making scaled Agile work with slicing, master planning, and big room planning. It is the true story from one particular program in a financial services company, the EU Mifid regulation of extended responsibility for investment advisors.
-
Q&A on the Book "Humans vs Computers"
Author Gojko Adzic has released a book, Humans vs Computers, in which he tells stories about the impact of inflexible automation, edge cases and software bugs on the lives of real people. He explains the common mistakes built into the systems and provides advice on how to prevent these mistakes from being built into our systems in the first place.
-
Q&A on the Book SAFe Distilled
The book SAFe Distilled breaks down the complexity of the framework into easily understood explanations and actionable guidance. It’s a resource for acquiring a deep understanding of the Scaled Agile Framework, and how to implement it successfully.
-
Is TDD a Form of OCD?
Developers are increasingly testing their own and each other's code. "Evaluation anxiety" is common psychological condition that is directly impacted by self-testing and team-testing. Are practices like TDD a defense mechanism to protect coders from criticism? And do emerging methods like Behavior Driven Development represents a more emotionally healthy approach to team evaluation?