One of the largest areas of waste in development are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste, as well as examining how this can fit into your current planning and estimation workflow via the underused ‘definition of ready’. It’s a very actionable concept that you can apply immediately.
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.
Mobile and embedded devices, more than any other technology, are an integral part of our lives and have the potential to become a part of us. This article discusses what “human experience” testing is and is not, and uses concepts from human computer interaction design theory to establish a framework for developing “human experience” test scenarios.
User Experience is part of a collaborative, self-contained and balanced team that has all the necessary roles to be wholly responsible for building the right thing, and building the thing right.
Active Architecture is a type of documentation that is based on User Stories and helps to bridge the gap between User Stories in Agile Projects and large design deliverables on Traditional projects. 14
Fixed price contracts are often decried as evil, however they are something which many agile teams face. How can a company execute one using agile practices to achieve better results with lower risk? 15
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques. 17