ThoughtWorks' Quarterly Technology Briefings Content on InfoQ
Latest featured content about ThoughtWorks' Quarterly Technology Briefings

- Topics
- Communication,
- ThoughtWorks,
- Distributed Teams,
- Collaboration,
- Agile in the Enterprise,
- Adaptive Leadership,
- Agile Techniques,
- Teamwork,
- Project Management,
- Companies,
- Agile,
- Distributed Programming,
- Leadership,
- ThoughtWorks' Quarterly Technology Briefings
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.
Presentations about ThoughtWorks' Quarterly Technology Briefings

- Topics
- Devops,
- Collaboration,
- Continuous Integration,
- Removing Waste,
- IT Service Management,
- Operations,
- Agile Techniques,
- Teamwork,
- Lean,
- Build systems,
- Infrastructure,
- Cloud Computing,
- Reliability,
- Programming,
- Agile,
- ThoughtWorks' Quarterly Technology Briefings
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.

- Topics
- ThoughtWorks,
- Project Management,
- Adaptive Leadership,
- Companies,
- Agile,
- Architecture,
- Enterprise Architecture,
- Leadership,
- Legacy Code,
- ThoughtWorks' Quarterly Technology Briefings
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.

- Topics
- ThoughtWorks,
- Agile in the Enterprise,
- Companies,
- Adaptive Leadership,
- Governance,
- Project Management,
- Lean,
- Agile,
- Enterprise Architecture,
- ThoughtWorks' Quarterly Technology Briefings,
- Leadership
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.

- Topics
- ThoughtWorks,
- Adopting Agile,
- Agile Techniques,
- Agile in the Enterprise,
- Adaptive Leadership,
- Lean,
- Companies,
- Project Management,
- Agile,
- ThoughtWorks' Quarterly Technology Briefings,
- Leadership
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.

- Topics
- Iteration,
- ThoughtWorks,
- Agile Techniques,
- Project Management,
- Value & Metrics,
- Adaptive Leadership,
- Companies,
- Agile,
- Design,
- User Interface,
- Usability,
- UX,
- ThoughtWorks' Quarterly Technology Briefings,
- Leadership
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.

- Topics
- Communication,
- DSLs,
- Distributed Teams,
- Domain Specific Languages,
- ThoughtWorks,
- Teamwork,
- Adaptive Leadership,
- Languages,
- Project Management,
- Companies,
- Architecture,
- Business,
- Agile,
- Domain Driven Design,
- Leadership,
- Programming,
- ThoughtWorks' Quarterly Technology Briefings
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.