Rolf Russell & Andy Duncan discuss how to have rapid and reliable releases from the perspective of build, release, and devops, considering the relationship between the teams involved, the metrics needed to measure the performance achieved, the required skills, and the need to remove waste and bottlenecks.
Roy Osherove discusses principles and practices that make teams more effective, successful and happy. Team topics covered: automating everything possible, buying/using/discarding tools, getting quick feedback, communicating without using meetings, building by feature not layer, code & tests reviewing. Lead topics: bottleneck ninja, integrity, removing obstacles.
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.
The PMO needs to be aware of how well each project is performing at any given time. Agile practices give transparency, with clear reporting of what’s done, its cost, and how well constructed it is. Learn how you can create a real-time governance capability that anticipates challenges, makes timely course corrections, and seizes opportunities to maximize the business impact of IT investments.
Agile practices emerge in a collaborative environment. As the leader on several projects, Pollyanna used collaboration processes to create a culture that fostered the emergence of iterative development, test first, evolving functional specs, pair programming, minimal documentation, and customer involvement at every step of the way. Pollyanna presents the steps leaders for emerging agile methods.
This session explores the approach and challenges to transforming multi-thousand person division to adopt new approaches to developing software. Questions about how to inspire and motivate change, identifying the change agents, the tooling to enable the masses will be discussed.
Martin Fowler talks about ThoughtWorks's experience with using Ruby on client projects for the past three years, and the creation of a Ruby-based product 'Mingle'.
Durnall and Parkinson provide a thorough introduction to Lean principles, the idea of "Lean Thinking," and the application of those ideas to software development. IT is viewed as a system, a process, as well as a series of production steps and the presenters show how Lean ideas apply to and can improve each aspect.
The state of the art in political technology evolved radically 2004-2008. In 2004, software development in Democratic political campaigns consisted of a few rag-tag hackers taking shots in the dark and building applications. In 2008, political start-ups built innovative social applications that raised nearly 1/2 billion dollars, and elected a President.
In this presentation filmed during ThoughtWorks’ Quarterly Technology Briefing, Dave Robertson and John Johnston explain what the Agile and User Centered Design’s (UCD) common denominators are, common values being the most important one in their opinion.
During QCon San Francisco 2008, InfoQ and BayAPLN, a local group of Agile Project Leadership Network (APLN), organized a panel comprised of Agile experts which answered questions from the audience. The panelists were: David Chilcott, Moderator, Polyanna Pixton, David Hussman, Sue Mckinney, Pat Reed.
Scott Shaw, Director of Services at ThoughtWorks, and Martin Fowler, Chief Scientist at ThoughtWorks, talk about the need for a new relationship between the business department and the IT department. Studies have constantly shown that the main culprit for unsuccessful projects lies in miscommunication between the business people and the IT ones.