Two of ThoughtWorks’ finest, Martin Fowler and Jez Humble, talk about the notion of Continuous Delivery, which enables organizations to build software that is production ready at all times. To do this, enterprises automate the build, deployment, and testing process, and improve collaboration between developers, testers, and operations. The duo discusses a variety of related issues.
ThoughtWorks recently published its Technology Radar; a report to help technology leaders understand emerging technologies, identify strategic platforms and tools and prepare their organizations for them.
ThoughtWorks has issued the January 2011 edition (PDF) of their Technology Radar, a document meant to indicate current software technology trends in a concise form.
ThoughtWorks Studios recently released the latest version and second major revision of Twist, its Agile test automation product. Twist 2.0 helps testers, developers and business analysts with collaborative testing. It also supports writing tests scripts using Groovy dynamic language.
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
Matthew Simons and Steven Boswell consider that although distributed software development is hard, it is a strategic capability that a company should consider, presenting a framework and Agile practices that help building a healthy distributed environment.
In this ThoughtWorks Quarterly Technology Briefing, Amit Uttam and Derek Longmuir discuss what a legacy system is, the typical approaches to dealing with legacy systems, the cost of legacy systems, replacement strategies and techniques, technology asset portfolios, system health checks, executing a migration plan, "strangler" vs phased approaches, and continually evolving your system.
In this interview Jez Humble discusses the concept of continuous delivery, which implies that software should always be production ready throughout its lifecycle. That means that every build could be released into production and run effectively. Continuous delivery involves build and deployment automation, continuous integration, test automation, managing infrastructure and environments and more.
In this interview, Cyndi Mitchell talks about ThoughtWorks’ concept of “Continuous Delivery,” which focuses on the last mile of software delivery. Mitchell also discusses the “adaptive” in ThoughtWorks Studios’ Adaptive ALM (Application Lifecycle Management) strategy, in which Agile solutions must be adaptive to users’ needs. And Mitchell describes ThoughtWorks Studios tools: Mingle, Go and Twist.
