The book fifty quick ideas to improve your user stories aims to help people to write better user stories, supporting teams in iteratively delivering products that satisfy the needs of their customers. InfoQ interviewed Gojko Adzic about the format of his new book, when and when not to use user stories, the ideas that the book provides, organizing product backlogs and prioritizing user stories.
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.
The third article from a series on Leading Self-Organising Teams covers what it means to lead a self-organising team.
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 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
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 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.