Rommana^TM Pre-recorded Webinars

Managing User Stories for Effective Development and Testing with Rommana ALM

Whether your project is agile or not, it is critical that you practice good requirement and/or user story management. Requirements and user stories do not just exist by themselves. Instead, they are linked to other artifacts such as test cases and test sets, scenarios and/or acceptance criteria, code and design components, tasks, risks, and actions. Requirements and user stories also change during the course of a project and over the lifecycle of an application. Some requirements or user stories originate from user requests, some evolve from bug reports or issues, and some are even enhancements to existing functionalities. A good requirement/user story management tool must support all these aspects of features.

This webinar will demonstrate how the requirement / user story component of Rommana ALM supports all these aspects and more. The intent is to help you understand true requirement and user story management so that you can make an informed decision regarding tool selection and tool adoption. If you are already using a tool to manage your requirements and/or user stories, this webinar should help you customize your tool to support all these aspects.

Effective Methods for Defect Prevention - Maturing the Testing and QA Profession

Organizations have become more and more interested in defect prevention as a way of reducing the cost of quality. Historically, the role of the test team in software organizations has been limited to identifying and reporting problems to the development team to fix. Experience suggests that this is a very expensive way to deliver quality products.

In this webinar, Magdy Hanna will present more methods that test professionals can use to prevent defects early in the process as well as using these methods to improve the development process, the test process, and the requirement process. These methods include:

• Closing the gap between development and testing with collaboration
• Scenario-based Development and Testing
• Asynchronous Collaborative Reviews
• Impact analysis

Feature-Based Project Management for Agile and Non-Agile Projects

The success of any project depends on how requirements are being managed, and how changes are being controlled through out the project. When things get hectic and the schedule slips, it becomes crucial to get back to the customer as soon as possible with some adjustments to functionality being delivered. In fact, it is even more crucial to avoid that schedule slippage in the first place. Most importantly, it is critical to any project manager or QA manager to provide accurate estimates for each feature to be delivered, with accurate time frame when it will be delivered. Agile projects also must have better control over increments to make sure specific functionality is delivered at the right time.

In this presentation, Dr. Magdy Hanna will show how Feature-Based Project Management™ adopted by Rommana ALM sets a new standard for managing software projects.

Some of the features that will be discussed in this presentation are:

• Allocating and managing project resources, roles, responsibilities and access rights.
• Creating and managing project tasks for both development and testing on the project level, as well as on the requirement level.
• Creating and maintaining action item lists for both development and testing effort.
• Managing risks throughout the project for both development and testing on the project level, as well as on the requirement level.
• Creating and maintaining project timeline for all project tasks for both development and testing.
• Creating and maintaining cost and time estimates for both development and testing tasks, either on the projects level or the requirement level. Managing product release and features included in each release.

ALM for the Medical Industry and FDA Computer Software Assurance - CSA

As we all know, developing and maintaining software for medical devices and large medical equipment is very different as it must follow a very controlled process. ISO/IEC/FDA standards impose a set of strict procedures and practices that must be followed. In this webinar, Dr. Hanna, Chief Technology Officer of Rommana Software, will discuss those requirements imposed by ISO/IEC/FDA standards and the need for a comprehensive application lifecycle management to support and enforces those requirements. Dr. Hanna will go into a hands-on session to show how Rommana ALM supports and enforce those requirements.

Gaining Control of Product and Process Quality with Integrated ALM

The quality of any software product or system always depend on how well the different processes of the product lifecycle are managed and how the artifacts of these processes are traced to each other. Our experience running projects of different types and sizes suggests that the success of any software project can only happen through fully-integrated application lifecycle management with following processes fully integrated:

• User Story and Requirement Management
• Test Management and Test Design
• Project Management
• Release and Iteration Management
• Issue and Defect Management
• Change Management
• Collaboration Management

Acceptance Criteria Vs Scenarios - Writing Better User Stories

For many years, project teams used user stories to describe functionality in agile projects. It is well established fact among agile teams that user stories in their standard format do not provide much details for developers to build the functionality or for tester to make sure the functionality is working as intended. To overcome the brevity of user stories, project teams sometimes use acceptance criteria to add more details to a user story and to establish the boundaries of a user story. Another approach that has proven to achieve good results is to write scenarios for user stories. In this webinar, Dr. Hanna will share his experience using both acceptance criteria and scenarios. More specifically, Dr. Hanna will discuss the following:

• User stories downsides
• The difference between acceptance criteria and scenarios
• How to use one or the other or both
• How derive tests from scenarios
• How Rommana ALM supports both acceptance criteria and scenarios

Scenario Based Development and Testing-Doing it Right the First Time

Bug reporting, bug fixing, and re-testing is a very time consuming and costly cycle that we all love to shorten. It is even worth when bugs are reported by customers after release. Not only because of the interruption it causes to operation and the frustration that it causes to users. Not only because of the time the customer has to wait until the problem is fixed, retested and released as, in many cases, they might have to wait until the next release. It is mostly because of the disappointment and the loss of confidence caused by the appearance of new bugs where things worked before and are no longer working – regression problems, sounds familiar? I am sure it does. If you have been in software development for a number of years, I am sure you have witnessed the impact of rework on team productivity. And, if you have been in a management position for a while, you probably also have felt the frustration of customers. Well, I very much have been there.

Have you ever though what type of bug reports you get from customers and why we get them? Getting answers to these two simple questions is the secret of how to minimize or even prevent those bug reports from coming back to your team. In fact, it is also the secret of defect prevention. I am really talking about the secret of Doing it Right the First Time; Something software teams have struggled with for many years. Your team might have used things like scenarios or acceptance criteria. They might have used agile, TDD, BDD, continuous delivery, continuous testing, and other seemingly promising methods. Has any of these helped your team achieve the ultimate goal of Doing it Right the First Time or even minimize the number expensive bug reports?

The Scenario-Based development and testing process as implemented in Rommana ALM has proven to reduce the number of bug reports by more than 70% and has shown a major increase in requirement coverage and code coverage. This webinar will shed the light on this process and show how you can get your team, agile or not, to start using it.