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.
When you think about outsourcing one or more project elements, what are you most concerned about? Missed deadlines? Low quality delivery? Inaccurate or incomplete scope? Increased risk? Everyone worries that the physical separation is going to lead to problems. Working together during project planning and recognizing that you both share the same concerns increases the chances of success.
This article discusses “human experience” testing and uses concepts from human computer interaction design theory to establish a framework for developing “human experience” test scenarios.
This article presents a new model proposing two key factors to consider for software delivery using impact maps, and why recognising the right context is crucial to get the most out of this method.
In his new book Scrum: The Art of Doing Twice the Work in Half the Time, Jeff Sutherland explains how the Scrum framework can be used as a general business practice to accelerate work of all kinds.
Pair programming can increase quality, velocity and even job satisfaction, and yet it is not a widely used practice today. Melinda shows how and why you should bring this practice into your team. 5
The book Improving Software Development Productivity contains practices, models and case studies which help you to quantitatively support adoption of agile software development.
Common System and Software Testing Pitfalls provides 92 pitfalls that make testing less efficient and effective. It aims to help you to avoid falling into pitfalls or dealing with the consequences.
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? 2
In this article, authors discuss the Reflective Agile Learning Model (REALM) that embeds reflective practice into the iterative and agile software engineering development cycle.
This article describes how Danske Bank effectively introduced Kanban for development teams in a two day workshop using an “involve me and I learn” method.