InfoQ Homepage Culture & Methods Content on InfoQ
-
Article Series: Patterns of DevOps Culture
Healthy organizations exhibit similar patterns of behavior, organization and improvement efforts. In this series we explore some of those patterns through testimonies from their practitioners and through analysis by consultants in the field who have been exposed to multiple DevOps adoption initiatives.
-
Linda Rising on Continuous Retrospectives
At the recent Agile Australia conference Linda Rising spoke to InfoQ about adopting an experimentation mindset and running continuous retrospectives in a team.
-
Leadership, Mentoring and Team Chemistry
How does fire fighting compare to DevOps? Michael Biven, team lead at Ticketmaster, shares important lessons on leadership, mentoring and team chemistry from his experience as a fire fighter.
-
Why Agile Didn’t Work
Why Agile didn't work? In this article Ping discusses the pyramid structure of the 12 Agile principles and the managerial and technical support you need to provide for Agile to work. She uses real-life examples to illustrate some common issues encountered in implementing Agile, and offers some solutions on how to detect and fix these issues.
-
A Conversation with James Shore on Agile Fluency and Let's Code Javascript
At the recent Agile Australia Conference James Shore gave a keynote talk and a workshop on Agile fluency. He spoke to InfoQ about his work on agile fluency, teaching and building tools for test driven development in javascript.
-
Drive: How we Used Daniel Pink’s Work to Create a Happier, More Productive Work Place
The story of using Daniel Pink’s principles of Autonomy, Mastery and Purpose to create a happier and more productive workplace. We actively translated his principles into real strategies, trials and experiments which we carried out across the organisation. Some things worked and somethings didn’t, but overall we significantly increased motivation and saw remarkable rises in productivity.
-
Meeting Developer Demands with WebRTC and CloudRTC Platforms
The WebRTC API lets developers easily integrate real-time comms into their apps. This article is the second part of a two part series analyzing the market of WebRTC platforms. It compares data from late 2013 / early 2014 to a survey conducted in April and May of this year as part of an ongoing coverage of the cloud real-time communications platform market.
-
Q&A on the Book Agile Impressions
Gerald Weinberg shares his observations of the agile movement "where it came from, where it is now, and where it's going" in the book Agile Impressions. In the book he explores the agile basics and principles, discusses how he has seen them being violated, and offers ideas and examples for applying the agile principles.
-
Agile Introduction: are you a Laggard?
This paper portrays the world-wide state of agile method introduction throughout the world using data from 330 organizations on hundreds of developments. The paper concludes that those adopting agile today are late. They should accelerate their transformation efforts because they need to catch up to be competitive. It summarizes the results of analysis of data from 330 organizations globally.
-
A Year in Swarm
The article tells a story of a small team of tightly-knit developers, a “human swarm”, who largely worked on a single screen and keyboard practicing mob programming, had no formally defined roles, performed no estimates, seldom worked on more than one task at a time and delivered a quality product to a satisfied customer.
-
How Different Team Topologies Influence DevOps Culture
There are many different team topologies that can be effective for DevOps. Each topology comes with a slightly different culture, and a team topology suitable for one organisation may not be suited to another organisation, even in a similar sector. This article explores the cultural differences between team topologies for DevOps, to help you choose a suitable DevOps topology for your organisation.
-
Q&A on Scrum for Managers
Rini van Solingen and Rob van Lanen wrote Scrum for Managers, a book providing answers for organizations that want to or are adopting Scrum. An interview on what managers can do to give teams enough space to self-organize, the possible ROI of implementing Scrum and how to measure ROI, defining teams and anchoring Scrum in the organizational structure and systems, and much more.