InfoQ Homepage Business Content on InfoQ

Articles

RSS Feed

Newer Older

Development

Untangling an API-First Transformation at Scale. Lessons Learnt at PayPal – Part 3

This is the third in a three-part series that explores how PayPal has adopted a more API-first approach to building platform services. In this article, we’ll take a closer look at the program aspects and some of the execution and operational challenges that had to be overcome.

Deepak Nadig Erik Hogan
on Mar 03, 2017
Culture & Methods

Tailoring Your DevOps Transformation to Organizational Culture

To build a high performance organization via DevOps, one often needs to change the organizational culture. Culture is a cornerstone which either amplifies or dooms strategic initiatives in your company. This case study shows how you can apply the competing values framework for culture change, supported by tools to measure and visualize culture.

Tomek Pająk
on Feb 22, 2017
Culture & Methods

Q&A on the Book Scaling Teams

The book Scaling Teams by Alexander Grosse and David Loftesness provides strategies and practices for managing teams in fast growing organizations. It explores five areas which often pose challenges when organizations need to scale -- hiring, people management, organization, culture and communication -- and gives solutions for recognizing and dealing with those challenges.

Ben Linders
on Feb 07, 2017
Culture & Methods

The Misaligned Middle and Getting off the Hamster Wheel Using Kanban

At the Agile 2016 conference, Dominica DeGrandis and Julia Wester of Leankit gave talks on helping middle managers adapt to change and how Kanban can be used to identify problems in workflows, which people need to address.

Shane Hastie
on Jan 31, 2017
Culture & Methods

Q&A on The Antifragility Edge: Antifragility in Practice

In the book The Antifragility Edge, Sinan Si Alhir shows how antifragility has been applied to help organizations evolve and thrive. He provides examples of how antifragility can be used beyond agility on an individual, collective (team and community) and enterprise level, and explores a roadmap for businesses to achieve greater antifragility.

Ben Linders
on Jan 14, 2017
Culture & Methods

Predictable Agile Delivery

Human teams are unique, non-linear and unpredictable, but given the right conditions, their output can become linear, scaled and predictable. Managers have an enabling role to play: encouraging the development of predictability; understanding the needs of their teams; and rolling-up their sleeves to clear the blockages themselves or by escalating the problem promptly and responsibly.

Russ Lewis
on Nov 09, 2016
DevOps

Book Review: Site Reliability Engineering - How Google Runs Production Systems

"Site Reliability Engineering - How Google Runs Production Systems" is an open window into Google's experience and expertise on running some of the largest IT systems in the world. The book describes the principles that underpin the Site Reliability Engineering discipline. It also details the key practices that allow Google to grow at breakneck speed without sacrificing performance or reliability.

João Miranda
on Sep 21, 2016
Culture & Methods

Adaptable or Predictable? Strive for Both – Be Predictably Adaptable!

Our efforts to improve software development face the question of what to focus on. Should we govern for predictability without concern of value, maximizing cost-efficiency without concern for end-to-end responsiveness? Or maybe do the opposite and govern for value over predictability, focus on responsiveness over cost efficiency? What we really need is to be predictably adaptable.

Dimitar Bakardzhiev
on Sep 06, 2016
Architecture & Design

Continuous Delivery Coding Patterns: Latent-to-Live Code & Forward Compatible Interim Versions

This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.

Luca Minudel
on Sep 02, 2016
DevOps

Virtual Panel on Bimodal IT

Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.

Manuel Pais
on Aug 31, 2016
DevOps

Respect Your Organisational Monoliths

There is a lot of information about DevOps, the technology, the culture, the behaviour. There is not a lot of information about tackling DevOps in large enterprises and there is certainly very little about tackling DevOps in large financial organisations. This article presents lessons learnt rolling out DevOps in a large insurance organisation.

Margo Cronin
on Aug 18, 2016
Culture & Methods

WTF requirements in Agile Product Development

The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.

Gene Gendel
on Aug 11, 2016