Roy Osherove talks about the challenges and opportunities of being a software team leader. He shares his hard won experiences in growing teams, their members and influencing behaviour. Being a software team lead is about getting out of your comfort zone, creating trust and commitment in your team but also about knowing about team maturity levels and the different approaches needed.
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.
M Dwyer of BigVisible Solutions talks about the process of transforming businesses to agility, including the concept of Agile localization in global efforts. Dwyer says that with distributed teams across multiple time zones and cultures it is good to establish a group of Agile missionaries to go forth and train people on Agile. He also discusses how to transfer Agile skills to the next generation.
In this interview, Agile management expert Johanna Rothman talks about the process of managing in Agile environments, particularly for distributed teams. Rothman also helps to distinguish between self-directed, self-organized and self-managed teams. And she stresses the importance of clear communication amongst team members, as well as the ability for managers to learn new skills.
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.
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.
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.