The book Improving Software Development Productivity contains practices, models and case studies to quantitatively support adoption of agile software development. An interview with Randall Jensen about measuring and improving productivity, contribution of agile to productivity, benefits from pair programming and teams, knowledge retention in maintenance and commandments for communication.
Lisette Sutherland and Elinor Slomba are collecting and sharing stories from people whose business models depend upon getting remote teams right. These stories showing how remote teams collaborate, bridge distance, build trust and get things done together will be described in the upcoming book Collaboration Superpowers: The Remote Field Guide.
What exactly do we have to do to capitalise on self-organisation? How can we best support our teams? What special kind of leadership is needed? The third article from a series on Leading Self-Organising Teams covers what it means to lead a self-organising team.
Keith Richards looks at how to succeed with agile in a distributed context. His findings are sometimes surprising and he asserts that to some extent nearly all work is ‘distributed’ in some form. 1
A lot of the pain that large and medium-sized organizations are facing boils down to scaling. At Jimdo, the approach to scaling relies on three major factors: culture, communication, and kaizen.
Robert Pankowecki is writing Developers Oriented Project Management, a book which aims to help professionals to improve project management practices and move towards more flat organizations.
Do you find it hard to say no when others ask you for help - even when you are already too busy? In this article, we examine the problem of chronic overcommitment, what causes it and some solutions. 2
Some 80% of all improvement and change programmes fail. Intelligent Evolution ensures long-term business success rather than short-term satisfaction of a standard or theory.
Developers hate writing down anything that isn’t code. But there are times on a project when a little documentation can go a long way. In this article, we discuss when and why to write things down. 5
InfoQ has interviewed Simon Baker, cofounder of Energized Work and the 2009 recipient of the Agile Alliance Gordon Pask Award, author of the "No bull" publication on the past 12 years of Agile. 2
"Swarming" is a technique whereby many members of a team work together to deliver a User Story, taking advantage of the skills of many team members together. How do you do this in a distributed team? 3
InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1