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, team development expert Esther Derby talk about her 13 questions for team managers – a set of questions aimed at helping managers make their development teams more effective. Derby said her goal is to help managers to look at their organization in terms of its capacity, in terms of what its customers desire and in terms of creating more effective work systems.
In this interview, Elizabeth Woodward talks about overcoming the collaboration problems that arise in distributed team development. She also discusses using Scrum in distributed teams. As co-author of "A Practical Guide to Distributed Scrum," Woodward focuses on establishing good, fundamental practices – as she says good practices are paramount for teams and tooling comes second.
In this interview, Diana Larsen gives her perspective on the value of trust in an Agile development environment. Larsen talks of trust, authenticity and forgiveness as being key to teaming efforts. Trust is the glue that holds teams together. Authenticity is showing one’s true self to the team. And forgiveness is critical in rebuilding trust on a team if it is somehow broken.
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.
Ashley Johnson shares his views on Agile development, in particular the move toward “Personal Agility.” Johnson says it is not possible to have an Agile organization of any scale without having the individuals behave in an Agile manner. Part of Personal Agility is about taking responsibility and approaching others as humans rather than obstacles. Johnson also discussed the Scrum vs. Kanban debate.
Scott Chacon talks about the technologies that power GitHub (Erlang, Redis,...), and the benefits of Git as a version control and as a storage system.Also: ShowOff, Scott's JS-based presentation tool.
Tom Preston-Werner introduces Git and GitHub and answers some questions about GitHub's architecture and features. He also talks about its development process and explains that using Erlang was instrumental for making it robust. Kenneth Lundin then talks about the decision of Erlang/OTP team to move it to GitHub and how it helped increasing contributions from the community.
Joe Walker explains the browser-based source editor Bespin: the architecture and implementation, the collaboration features, new ideas for command lines, Canvas vs DOM, speed, extensibility, and much more.
Chris Wanstrath discusses the state of GitHub's architecture, how GitHub is used and its impact on open source collaboration.
Mary Poppendieck talks about her last book "Leading Lean Software Development", a book for the product, program and all C-level managers, showing them how to apply agile principles and practices starting from the realization that development teams are not successful if they are not in the same boat with their managers.
Christopher Avery explains why personal responsibility is a foundational skill for any and all teams and shares his model for personal responsibility and how this affects individuals and teams in the workplace. He goes further with several concrete tips on how to form successful, high performing teams.