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: Joe Beda, Simon Crosby, Krish Subramanian, and Cloud Opinion.
The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio 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.
This article explores how Fujitsu UK applied SEMAT and Essence to systems engineering, to combining agile and traditional methods and look at the whole programme of work across all disciplines.
In this week's podcast Richard Seroter talks to James Shore, Llewellyn Falco, and Rebecca Wirfs-Brock on TDD and Incremental Architecture. 1
When adopting inner source, organizations should consider nine factors pertaining to product, process, and organization.
Team that perform great have a perfect balance of orientation on people and results. This article provides several exercises to explore how your team is doing and find your own state of perfection.