development

A major concern when developing new software features is that another part of the code will be affected in unexpected ways. With a typical development processes, testers often do not run a full set of product regression tests until late in the release when it is much more costly to fix...

Many development organizations are experimenting—but getting mixed results—with lean development techniques. As a test or development manager, you have the power to help eliminate defects—the largest source of waste in development—and the enormous rework costs they incur.

Just as those in the software world are getting their hands around agile practices, leading software organizations are going beyond continuous delivery for acceptance testing and now adopting continuous deployment—the practice of immediately releasing new code from development into...

In my research study, I need to identify the list of key features of user story management tools that can be used to support agile development. So far, I identified the following general groups of features: User role modeling and personas support, User stories and epics management, Acceptance testing support, High-level release planning, Low-level iteration planning, and Progress tracking. Each group contains some specific features, e.g., support for story points, writing of acceptance tests, etc.

Please help me elaborate the list by posting your list of such features, such as those that you've already used as part of a user story management tool, or those that you'd like to see in the software tool you use. Do you find some features more important than the others? Many thanks in advance!