The common thread among clients is that they are mission-driven. The more nuances, the better. Following are some of the organizations with whom Requirements Quest has had the pleasure of working in recent years:
- Allstate Insurance Company
- American Family Insurance
- Armstrong World Industries
- Aurora Health Care
- Beacon Technologies
- BizConstruct
- Bridgestone Americas
- Capital Indemnity
- Church Mutual Insurance Company
- Compass Bank
- Compuware Corporation
- CUNA Mutual Group
- Dean Health Plan
- Direct Supply
- Diversified Business Communications
- Edaptive Systems
- Genesis10
- Great Lakes Higher Education Corporation
- HSA Home Warranty
- Johnson Controls
- Lands’ End
- Madison Area Technical College (MATC)
- Northwestern Mutual
- Oakland University
- Oshkosh Corporation
- Praxilient
- Progressive Insurance
- QBE the Americas
- Safe Bridge Solutions
- Secura Insurance
- SHAZAM
- Stratagem
- TDS Telecom
- Thrivent Financial for Lutherans
- Trissential
- Unigard
- University of Wisconsin System
- University of Wisconsin-Madison
- University of Wisconsin-Milwaukee
- WEA Trust
- West Bend Mutual Insurance
- Wipfli LLP
- Wisconsin State (various departments)
- WPS Health Insurance
Client Testimonial:
Church Mutual Insurance - Merrill, WI
Dear Roxanne:
When our company contracted with you for the requirements class, we were looking for a methodology that we could develop into our own best practices. As of this writing, we are using the Requirements Quest process and have had excellent results.
One of our new development projects was to the point of having the requirements completed. But after the week in your class, the business analyst asked to take the additional time with this project to re-write the requirements using the methodology. She did and the results are amazing. What was going to be a partially automated/ partially manual solution is now going to be fully automated. Why? Because by following the methodology we identified additional stakeholders, documented the "as is" process, used validation and the result was new and complete information that allowed the complete automation. Needless to say, the business is extremely happy.
We have just completed four additional projects. They were implemented within our scheduled dates. They were quality initiatives. They satisfied the customer. Here are some interesting facts. Of the total project time 50% was spent in requirements, 30% in programming, and only 20% in testing. These facts are interesting because prior to this methodology the time for requirements and testing were flipped. And depending on the complexity of the programs there was usually a large amount of re-work. With the new process, two of the projects had one bug each in the programs. The rest of the programs were clean. No rework. None.
There is a learning curve. It does take additional start up time to get people used to doing the new steps and we haven't completely settled on the right format for maintenance projects. But we are seeing success. We have now sent all of our business analysts and system programmers and system analysts through this course. We are sold on the methodology! It works!
Thanks, Roxanne, for the great program and for your passion in presenting it. It encouraged people to try it for themselves. And gave us the methodology we were looking for.
Marj Krause
Director of Application Analysis and Design
Church Mutual Insurance Company
Our Clients
The common thread among clients is that they are mission-driven. The more nuances, the better. Following are some of the organizations with whom Requirements Quest has had the pleasure of working in recent years:
Client Testimonial:
Church Mutual Insurance - Merrill, WI
Dear Roxanne:
When our company contracted with you for the requirements class, we were looking for a methodology that we could develop into our own best practices. As of this writing, we are using the Requirements Quest process and have had excellent results.
One of our new development projects was to the point of having the requirements completed. But after the week in your class, the business analyst asked to take the additional time with this project to re-write the requirements using the methodology. She did and the results are amazing. What was going to be a partially automated/ partially manual solution is now going to be fully automated. Why? Because by following the methodology we identified additional stakeholders, documented the "as is" process, used validation and the result was new and complete information that allowed the complete automation. Needless to say, the business is extremely happy.
We have just completed four additional projects. They were implemented within our scheduled dates. They were quality initiatives. They satisfied the customer. Here are some interesting facts. Of the total project time 50% was spent in requirements, 30% in programming, and only 20% in testing. These facts are interesting because prior to this methodology the time for requirements and testing were flipped. And depending on the complexity of the programs there was usually a large amount of re-work. With the new process, two of the projects had one bug each in the programs. The rest of the programs were clean. No rework. None.
There is a learning curve. It does take additional start up time to get people used to doing the new steps and we haven't completely settled on the right format for maintenance projects. But we are seeing success. We have now sent all of our business analysts and system programmers and system analysts through this course. We are sold on the methodology! It works!
Thanks, Roxanne, for the great program and for your passion in presenting it. It encouraged people to try it for themselves. And gave us the methodology we were looking for.
Marj Krause
Director of Application Analysis and Design
Church Mutual Insurance Company