Decisions, Decisions
Dan North engages the audience into a discussion about the tradeoffs involved in making decisions regarding the team composition, development style, architecture, and deployment solutions.
InfoQ
InfoQ
Topic/Tag specific view
Distributed Team Content on InfoQ
Latest featured content about Distributed Team
News about Distributed Team
Design Thinking and Culture of Collaboration
Design thinking is about creating vision of the future, not just managing the present. Bill Burnett from Stanford University recently spoke about design thinking and what questions we need to ask to shift from design to design thinking.
The Daily Standup/Scrum is not for the Scrum Master
Mike Cohn recently suggested that the Daily Standup (or Scrum) is not a status meeting for the Scrum Master, but a forum where team members are synchronising their work. Techniques such as breaking eye contact are helpful for Scrum Masters to fix this anti pattern in their teams.
Is Agile Stifling Introverts?
For years Agile has been encouraging teams to work together collaboratively in open spaces and encouraging developers to pair program, but lately these types of practices have been coming under fire.
Articles about Distributed Team
Agile Adoption – Vital Behaviours and Influence Strategies
Steve is interested in uncovering better ways to deliver successful projects regardless of whether or not those ways are ‘agile’. After reading "Influencer, the Power to Change Anything" he found a set of behaviours and influence strategies that are helpful for giving projects the best chance for success and also for helping teams transition to agile.
Laurent Bossavit: Agile Ten Years On
Laurent Bossavit discusses the importance of learning from history and reflects on the historical influences that have contributed to emergence of agile practices and techniques. He examines the impact agile approaches are having and the emergence of the new discipline of agile software development, and calls for formulation of a new generation of more inclusive Agile institutions.
Git, Gerrit Review and Jenkins or Hudson CI Servers
Together, Gerrit and Jenkins/Hudson allow you to propose changes and have those proposals automatically compiled/tested/verified before a human review even starts. This article shows how to install and configure Gerrit and how to hook it up to Jenkins/Hudson to build all proposed changes.
Presentations about Distributed Team
Scaling Lean & Agile: Large, Multisite or Offshore Delivery
Craig Larman presents practices and tips related to adoption, structure, requirements, contracts, architecture and design, offshore, multisite development, and coordination with large Scrum teams.
DevOps for Business - Lessons Learned
Stephen Nelson-Smith’s presentation is a case study and lessons learned by implementing Agile and Lean practices by both the development and operations team in an attempt to overhaul the entire development, testing, staging, and production process of a UK governmental website.
Interviews about Distributed Team
Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches. Jesper also discusses the benefits of integrating elements of Kanaban into existing Scrum teams and what can be achieved from the team seeing the entire value chain and owning the whole process.
Mike Cottmeyer on Agile Adoption and Transformation
In Agile, adoption and transformation are typically viewed as one big event. Mike Cottmeyer provides a holistic perspective that looks as adoption as the implementation of practices, and transformation along two dimensions, organizational and personal. Mike discusses how they are a means to an end, and how to avoid the trap of focusing on practice adoption as a goal.
Books about Distributed Team
Priming Kanban
This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.