Johanna Rothman explores how to scale lean and agile processes to work in large programs in her book - Agile and Lean Program Management: Scaling Collaboration Across the Organization. It explains how to collaborate across the organization to create and steer an adaptive, resilient program.
Cloud bursting! On-premises! Hybrid cloud! Off-premises! Multi-cloud! These are phrases author Michael Coté heard over the past 10 years when covering cloud as an analyst, strategist, and now evangelist. Each of them makes logical sense, especially on a big whiteboard with boxes and arrows going to and fro. In recent times, it’s the last - multi-cloud - that he's seen in actual practice the most.
Big Data Analytics with Spark book, authored by Mohammed Guller, provides a practical guide for learning Apache Spark framework for different types of big-data analytics projects, including batch, interactive, graph, and stream data analysis as well as machine learning. InfoQ spoke with author about the book & development tools for big data applications.
The book Strategize by Roman Pichler provides practices, advice, and examples for product strategy and roadmapping that you can use to create successful products.
Configuration is one of the most widely used cross-cutting concerns in application development. Apache Tamaya is a new incubator project that brings standardized property management to Java.
There's no shortage of opinions on the topic of technology lock-in. InfoQ reached out to four software industry leaders to participate in a lively virtual panel on this topic.
The book Diving For Hidden Treasures by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.
As we move towards microservice-based architectures, we're faced with an important decision: how do we wire our services together?
To adopt Agile at a systemic level, take an Organization Development approach to redesign organizations, redefine learning, empower teams through self-organizing and to reduce resistance to change.
Is pair programming all that it's cracked up to be? Wes Higbee discusses why it definitely shouldn't be mandated, and why you should consider other options where it could be beneficial. 3
It makes no difference how hard you try- some form of lock-in is unavoidable. What matters most is understanding the layers of lock-in, and how to assess and reduce your switching costs.
It can be difficult to change from a Waterfall approach to the Agile practice in which requirements are prepared ‘just in time. The secret to success in Agile is ruthless management of scope.