User Stories, designed to keep teams laser-focused on customer needs, serve as THE driving force behind delivering valuable, high quality features, fast. This presentation discusses how to write great agile software user stories by defining customer value and keeping teams laser-focused on needs.

Working with stakeholders (customer, business and technology perspectives) to effectively and efficiently deliver high-value products begins and ends with value. “Value” is the beacon, watchword, end game, justification and mantra for Agile. It is the basis of the big “why”.

Learn how leading organizations are investing more in requirements as part of their product development strategy to give everyone involved a common vision of what is being built and who the customer is. Without that common vision even the best teams risk writing the wrong test, focusing on the wrong design elements, or moving the wrong item to the top of the backlog.

Value-based software engineering (VBSE) is an approach that take into account the fact that software has a major influence on most systems’ cost, schedule, and value. Software decisions are inextricably intertwined with system-level decisions. In this article, Barry Boehm discusses the basic principles of value-based software engineering and explains why value-neutral methods are insufficient as a basis of a software engineering discipline.

User story mapping might look like the heavy weight mapping of the past, but it is not. However, if you can’t map your stories back to business value, then why do they make or save the company money? Learn how to improve your business analysis with Agile story mapping.