New answers tagged

2

A User Story indicates the impact to users with the business reason for the work to be done. There are tasks that need to get done that don't directly affect users, for example setting up infrastructure or paying down technical debt. However, the examples you provided all look like they have a user impacted reason to exist. As a [type of user] I want to ...


2

I'm familiar with but don't have easy access to IEEE 830:1998. I do have access to ISO/IEC/IEEE 29148, which superseded IEEE 830. From what I can remember about IEEE 830, and from reading ISO/IEC/IEEE 29148, there is nothing that precludes graphical notations in a requirements specification. ISO/IEC/IEEE 29148, in various sections, refers to "graphic ...


Top 50 recent answers are included