This discussion is in the context of Software / Systems (Software + Hardware) Projects. We will essentially try to answer a question,

How RMsis is going to be used within an Agile OR Waterfall Model ?

Our view is that the Model does not make a difference at the fundamental level, though there could be questions, which are dependent on the specific context of a project. We will try to explain in the following sections.

Click here to read further.

 

Why should RMsis have Planned and Unplanned tables for managing requirements? This article attempts to provide an answer to this question and tries to clarify the context and need for the Unplanned Requirements Table.

Click here to read further.

 

Collaboration across geographies and development of shared vision remains one of the key problems in large organizations. In this article, we demonstrate how RMsis can be used by multi-locational teams to effectively collaborate and develop a shared product portfolio roadmap.

Click here to read further.

 

CMMI is the standard of choice for many mature Software Engineering Organizations across the world and it is used extensively to benchmark and improve the Software Engineering Practices. In this article, we present a summary of how RMsis can potentially support the goals and practices laid out by CMMI; for Requirement Development and Requirement Management.

Click here to read further.

 

Users desire flexibility in Reporting, which meets their own Project and Organizational needs. RMsis provides custom reporting feature from version 1.5.0 onwards and this simple yet powerful feature can cover almost 90% of the reporting needs for most users. In this article, we present few possibilities, which represent some of the most common use cases.

Click here to read further.

 

RMsis users have considerable flexibility in terms of how they structure their requirements, using the following features

  • Hierarchies
  • Dependencies
  • Categories

However, the Testing Functionality offers just a flat structure for defining the Test Cases. This may leave many users wondering, “what would be an optimal way to organize the test Assets ?”. This article presents analysis and suggestions against this question…

Click here to read furter.

 

A product team always works under constraints of resources, time and quality; while there are always abundance of requirements which need to be implemented. We have also seen that a product need not have too many functions, since most of the customers use only about 10-20 % of the functionality, as indicated by many empirical studies. Many products (like iPod Shuffle) are a living testimony of this theory. In this article, we will look at the “Requirements Prioritization” process …

Click here to read further.

 

Today, despite making a significant progress in technology, majority of software projects still fail to meet the user needs, may it be in terms of cost, quality, timeliness or functionality. While the development tools and processes have significantly improved, we @ Optimizory believe that Requirements Management still remains a key bottleneck in the successful execution of projects. RMsis fills this gap with a user friendly interface and by focusing on a large set of small requirements, which can be iteratively analyzed and which closely map to the delivered product.

However, it is also true that in order to achieve results, the tool has to be complemented by organizational intent and the right set of processes.

In this article, we shall detail out our views about effectively managing Requirements, addressing many dimensions of Requirement Management, not necessarily the areas directly addressed by RMsis.

Click here to read further.