Month: February 2013
Using Approval Branching for Business Requirements
When the business changes rapidly, this is a problem for a development team that has in its current release trunk both approved and unapproved features. In this blog post, Jack Low presents a solution to minimise the issues created by unapproved features in the codebase at the time of a release and contrasts this approach […]
Read More
From Requirements to Automated Tests and Back
Learn how software applications can be specified, continuously developed, tested and delivered and how testing supports the flow from requirements through to acceptable systems. In the Agile community, Acceptance-Test Driven Development (ATDD), Behaviour-Driven Development (BDD), Test-Driven Development (TDD) and Specification by Example are gaining greater acceptance as an effective approach to developing systems of high […]
Read More
Creating a User Story Map
A user story map is a technique created by Jeff Patton where you arranges you user stories into a useful model to help understand the functionality of the system. In this blog post, Steve Rogalsky explains how to create a user story map.
Read More
Goals Oriented Requirements
Collaborating on deriving scope from goals is undoubtedly the most controversial topic in this book. In the last five years, the surge in popularity of value chains in software development has increased awareness of the idea of collaborating on scope and deriving it from business goals.
Read More
Better. Faster. UXier: AToMIC Design
We are designers, and we know how important design is to the success of our projects. We’re also agile! We believe in making incremental changes based on user testing. But there are some parts of the process we’re just not very good at yet. It’s usually still hard to achieve dramatic, site-wide style changes in […]
Read More
Customer Input For a Successful Product
Studies in Human Computer Interaction (HCI), User Centered Design (UCD) and User Experience Design (UED) have found that accurate and frequent customer input is essential for a successful software product. Knowing who your customers are, what their environment is like, and what their needs are gives you the information required to plan and design a […]
Read More