DevOps promises to break down the barriers between the developers and the systems operators, but success with DevOps hinges on the company's culture and flexibility.
The AdoptOpenJDK has released the first code coverage percentages for the OpenJDK codebase.
Ash Maurya describes the importance of writing a problem statement in the business model.
Doing pair programming when working remote helps to increase interaction between developers and build relationships in teams, it makes knowledge flow and can prevent developers from drifting away. You can experiment with tooling to find a setup that works for you. Empathy and egolessness can emerge organically when doing pairing in a distributed team. Read about experiences with remote pairing.
This post describes the changed role of PMO (Project Management Office) in the Agile organizations.
Avishai Ish-Shalom talked about the importance of moving from agile cargo cult to agile organizations at DevOps Days Ljubljana 2015. He gives some practical examples and guidance for taking full advantage of Conway's Law.
Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.
Rodoljub Petrović shares his lessons learned from growing engineering teams for years. If you want to change your organization's culture, take care of your hiring process and give it top priority. And follow these lessons.
With SmartBear Software recently announcing that they are assuming responsibility for the Swagger API open-source project, many companies involved in API development tools have wondered if there will be major changes. Questions are also coming from the open-source community and from professional API developers. InfoQ interviewed Tony Tam, founder of the Swagger project.
Although the world has changed we still worship ideas from ancient management heroes says Tomasz Wykowski. Our behavior changes quite slowly. To get servant leadership adopted in organizations you need to start from yourself and be an example. Give trust to people and respect them, and invite them to change.
Organizations are increasingly working with remote teams to discover that it can be challenging to establishing remote teams and collaborate effectively with people in remote or distributed teams. An interview with Janis Janovskis on the challenges of remote teams, working together in different time zones, using hangouts and experiments to establish remote teams and finding the right people.
Ron Jeffries recently posted about the need for a Product Champion, someone who knows the customer marketplace, who can be accountable for maximizing success. He discusses how in many Scrum, XP and "Agile" teams the Product Owner is not adequate for the task and that by taking the perspective of a Product Champion they can deliver great outcomes.
You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.
Fran O'Hara's lessons learned integrating testing in agile teams, in particular ensuring required test competencies are in place. Full test integration in an agile team is not as simple as mixing a couple of testers in the team, instead multiple working practices and skills are needed for delivering quality applications in an agile world.
Here's an experience story from a tester who decided to move onward and become a Scrum master to help her team to become more agile, with learnings from their agile journey and pieces of advice for doing change in organizations.