DevOps East 2017 - Agile Requirements
Wednesday, November 8
Rightsizing User Stories
PreviewUser stories and their big brothers, epics, are an excellent way to describe requirements for a software system. They act as stakes in the ground to keep track of what the system needs to do, the type of user most interested in each feature, and the reason the requirement provides value. As projects reach a certain size, stories often become too large for a team to complete within a single sprint. The solution? Split them into smaller stories, each of which can be completed within the duration of one sprint. Dave Todaro describes proven techniques to split epics and stories, making...
Balance Discovery and Delivery with Dual-Track Agile
PreviewDo your product teams frequently struggle to have groomed and well-defined stories ready for the developers? Do you find yourselves frequently in “feed the beast” mode to keep your development teams busy? Do your product teams have problems gaining shared understanding across product management, interaction designers, developers, and QA? If so, your product teams manifest the symptoms of single-track agile—and this session is for you. Sean McKeever explains the key steps in establishing dual-track agile methodologies at your organization, presents his experiences, and provides...
They Said, We Said: Bridge the Communication Gap with Behavior-Driven Development
PreviewHave you heard that only 36 percent of business features built into software are actually used by end users? And why do we get functionality that fails to work as expected? One of the age-old problems between IT and our clients is that we don’t speak the same language. Sheetal Patel shares her experience of how behavior-driven development (BDD) introduces the bridge of common language that both IT and non-technical, business clients can speak to build the right product. Sheetal explains how collaborating on agile teams with BDD gains a common understanding among developers, testers...