iRise 11 now combines prototypes and requirements capture with new text management and collaboration capabilities to track and manage requirements or user stories throughout your own software development lifecycle process.

For some time we have seen the key to successful product definition and delivery coming in two parts - you must capture the right requirements (visual/text in context) and you must effectively manage those requirements through development, testing and deployment. iRise Manager provides a consolidated view of all your captured requirements, user stories, tasks and other related deliverables so you can can manage them from ideation through to go-live.  It’s flexible enough to store, sort and organize user stories, epics, tasks, acceptance criteria, tasks and even attach entire specification documents, so no matter how your team organizes requirements, iRise can be the system of record rather than a starting point or a means to an end.  

  • Manage Requirements/Stories with the team and beyond: The new Manager module is accessible to all Definition Center users, not just Authors. Anyone with Edit access to a project can review, sort, add, and update any requirements that are in the project, link to screens, add attachments and integrate with other ALM tools that you use for your development workflow.  
  • Customizable Attributes: Each organization and team tends to have different processes, workflows and attributes that work best for their definition, development, test and deployment activities.  The new Manager functionality has a graphical editor to help define the attributes and values that work for you and your team.  The attributes and values can be exported and used for any project; the Definition Center can also be set up to have a default schema with these attributes and values in it for each new project that is created.  
  • Configurable Views: Anyone with Edit access to a project can set up views, which are a powerful way to filter, sort, and organize the requirements based on your defined attributes and values. Views are flexible ways to group, sort and filter requirements/stories for any number of different situations.  For example, different views can be quickly set up on a project and used for backlog grooming sessions, planning meetings, testing sessions or perhaps to highlight ship blockers. A view could be used to communicate upcoming features and tasks with the devops crew downstream. 

Did this answer your question?