BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Culture Content on InfoQ

  • Great Engineering Cultures and Organizations - Afternoon Sessions from QCon London

    The Building Great Engineering Cultures and Organizations track at QCon London 2018 contained talks from practitioners representing digital leaders of the consumer internet as well as transformational corporates from “traditional” sectors. Previously InfoQ published a summary of the morning sessions; this is the summary of the afternoon sessions of this track.

  • Using Agile Principles with Scrum Studio to Increase Organizational Responsiveness

    Using a change approach based on agile principles with Scrum Studio helped a Dutch pension and investment management company to become more responsive at structurally lower costs. The change team practiced what they preached by applying transparent and iterative change with similar characteristics as the intended end result. They established a culture where people are taking responsibility.

  • Game Changing Beliefs for Knowledge Working Organizations

    Game changing beliefs carry the strength of the strongest walls to shape our behavior. The beliefs we choose to take on in our professional work are a leverage point. They can help us to change the culture and behavior in organizations to increase agility.

  • Game Changers for Organizations

    We want to approach strategy using choices, direction, and iterative experiments, establish a growth mindset in organizations, and work towards a common purpose or goal with leaders and teams sharing the same values, principles, and mindset; these are some of the game changers for organizations to become more innovative, deliver faster and better, and have happier and more engaged employees.

  • The Future of Work - Afternoon Sessions from Agile People Sweden

    The future of work is about microlearning and unlearning, freedom by technology, agile companies, alignment for autonomy, and self-organized groups of people around common goals and interests; these are some of the ideas that were discussed at Agile People Sweden.

  • The Industry Just Can't Decide about DevOps Teams

    The incidence of DevOps teams is on the rise according to reports, but the industry remains divided on whether a DevOps team should even exist. Some are wary of creating additional silos, or are of the opinion that DevOps is a methodology that everyone should subscribe to in an organisation; others point to DevOps teams as an effective way of transitioning to a new way of working.

  • Paradoxes in Culture Change

    Organizations should realize that organizational culture is an important factor in increasing agility, and then act on this realization. The desired organizational culture must be promoted by example top down; what is happening at the top of the organization concerning values, communication and customer involvement will predict what will happen in the "underlying" layers of the organization.

  • Q&A with Aurynn Shaw on Sharing Her Personal DevOps Journey at DevOpsDays NZ

    Raf Gemmail speaks with Aurynn Shaw about her upcoming DevOpsDays NZ talk and the humanist side of DevOps.

  • Treating Shared Databases Like APIs in a DevOps World

    Simon Sabin, principal consultant at Sabin.io, spoke at WinOps 2017 conference on how to include database changes in a continuous deployment model. A key aspect when sharing databases across multiple services or applications is to treat them as APIs, from the perspective of the database owners.

  • Node.js Forks over TSC Disagreements

    The Node.js Technical Steering Committee (TSC) and Board have weighed in on the results of a vote to remove a member from the TSC based on a pattern of behavior. This has resulted in several resignations from the TSC, a plethora of commentary, and new recommendations by the Board of Directors.

  • Tackling Technical Debt at Meetup

    Continuous product health can be realized by regularly prioritizing the highest impact technical debt items and knocking those off systemically. You need to continuously iterate how you're tackling technical debt to drive more and more impactful results. Going for maximum impact items first and communicating the impact of paying down technical debt is what Yvette Pasqua, CTO of Meetup, recommends.

  • Adopting Agile and DevOps at Wyndham Vacation Rentals UK

    Embedding agile and DevOps had a positive impact on the role of QA at Wyndham; focusing effort in the earlier lifecycle stages has led to smoother releases with fewer bugs and post-production issues. Business colleagues and customers are more involved throughout the delivery cycle, making testing a shared responsibility .

  • What a High Performing Team Looks Like and How to Create One

    High performing is a team property, a temporary state which needs attention if teams want to keep on performing well. Things you can do to build a high performing team include creating safety, investing in developing collaboration skills, and giving peer-to-peer feedback.

  • Q&A with Mayank Prakash: DevOps in UK's Largest Government Department

    Mayank Prakash, Director General, CDO and CIO of UK’s Department for Work and Pensions told the DevOps Enterprise Summit London audience how the largest UK’s government department is moving away “from an organisation based on traditional vendor outsourcing, traditional structures and service delivery models to one with digital in its DNA”. InfoQ had the opportunity to do a Q&A with Mr. Prakash.

  • Q&A With Robert Scherrer: DevOps on the Backbone of the Swiss Financial Center

    Starting with a small core team, and a DevOps approach around 5 + 1 dimensions - skills, organization, process, infrastructure, architecture + mindset & attitude - SIX has been transforming how IT and the business work together to break the silos and align themselves along value streams. InfoQ took the opportunity to talk with Robert Scherrer, head of software dev at SIX, about this journey.

BT