Self-organized teams manage their work, the processes that they use and the way that they work together as a team and with their stakeholders. Robert Pankowecki is writing a book on Developers Oriented Project Management which aims to help programmers, product owners, project managers and agile company owners to improve their project management practices and move towards more flat organizations.
Why do we promise more than we can deliver? Why do we say yes when we are already too busy? Chronic Overcommitment is a pervasive problem in the IT industry. In this article we take a look at the behaviors that drive over commitment and the dynamics at play in your organization the make it a difficult problem to solve. Finally, we offer some advice to those who suffer from this affliction.
Some 80% of all improvement and change programmes fail: they did not achieve the expected results, the investment in the change programme was greater than the value achieved, “improvements” were seen as mostly bureaucratic, or changes were abandoned soon after the implementation. 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
Agile and offshore development are critical success factors for many organizations, but have never worked well together. The “Design for Hybrid Agile Adoption (DH2A)” methodology offers a solution. 3
Ken Howard and Barry Rogers have written a book that focuses on the first value from the Agile Manifesto. They provide advice, tools and techniques to help teams and individuals improve interactions. 2
In this IEEE article, John Stouby Persson and Lars Mathiassen discuss a process for managing risks associated in managing the distributed software projects. 2
In this article, excerpted from the book Coaching Agile Teams, Lyssa Adkins shows you how to activate the journey toward high performance in an Agile team in both provocative and practical ways.
This article by Andres Kutt summarizes six learnings from 55 months as an architecture team lead at Skype. Some of them are technical while some focus upon the softer aspects of an architect's work. 20