SpiraPlan lets you easily manage your requirements and user stories in an integrated requirements matrix. These requirements can be validated with the end customer and then elaborated into more detailed tasks that can be used as the basis for development.
A requirement is a very simply a stated desire or need: For example in a fictitious library system, a requirement could be that "the library system allows people to check-in and check-out books". Requirements management is the process of capturing and managing all of the different ‘needs’ that different stakeholders have in a system. Sometimes the needs relate to the functionality (the system needs to do X), other times it may be technical need (the system needs to run on specific web browsers, database servers, etc.)
The first thing you need to do is brain storm with your stakeholders (business, marketing, technical, end users, …) and put together the wish list of ideas, concepts and needs. SpiraPlan makes this process easy with its easy to use requirement entry screens complete with powerful rich text editor:
Once you have captured the needs, SpiraPlan allows you to quickly and easily organize requirements in a hierarchical structure (for example the system requirements might be organized under the parent functional requirement). Requirements can be prioritized, estimated and also associated with a specific release.
Each requirement is displayed with its associated development task progress. You can move, copy and filter the requirements according to a variety of criteria.
Sometimes a standard requirement is not sufficient to explain the need, that’s where a ‘use case’ comes in. A use case (also known as a scenario) is a description of the steps that a specific user would take to accomplish the task. A single requirement may have several different use cases depending on the different scenarios that are possible. For example an administrator logging in might be a different use case to a general user.
SpiraPlan supports the capture and management of system use-cases as part of the requirements definition process. Use cases can be stored in the system along with their associated scenarios and links to the other requirements that the use case defines:
Requirements can be categorized into different types, each of which can have its own customizable workflow. This allows you to define different rules, permissions and operations for each of the different requirement types:
In addition, SpiraPlan lets you specify that certain operations require an electronic signature which is used to permanently sign the changes made to the requirement.
SpiraPlan lets you decompose each requirement into lower-level work Task work items. These tasks can be assigned to different team members and individually estimated. SpiraPlan lets you compare the top-down story point estimate with the detailed task estimates.
Each requirement can be linked to an unlimited number of other requirements or incidents, providing traceability between related artifacts. For example a change request that turns into a new requirement can be associated to preserve the pedigree of the requirement.
SpiraPlan lets you have projects that share their artifacts with other projects. This powerful feature lets you have projects that reuse components, features and tasks from other projects:
In addition, you can share requirements between projects so that you can view all of your requirements in a single list; those from the current project and those from any component projects being included:
All of the changes made to a particular requirement in the system are tracked by SpiraPlan, so that at any time you can view the history log of all the changes made to an artifact, including the date of the change, who made the change, and what information was changed.
SpiraPlan has a built-in document management system that lets you quickly attach files, screenshots and hyperlinks to requirements so that you can have all your diagrams, specifications and other assets managed within the system and readily available.