Discussion Locked

Quality in IT

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
What do you think will happen if there is failure of quality in information systems?

15 replies

by wayne m.

"What do you think will happen if there is failure of quality in information systems?"

Late projects, cancelled projects, unhappy users, etc. Wait... that sounds like the current state of the industry!

by ebaker

It depends upon a number of factors. If you define "quality" as conformance to requirements, then failure means the system cannot do what it was designed to do. Does the entire system fail, or are some the requirements met and others still fallingshort? As a PM, you need to carefully define and manage quality as much as cost and time.

by charles.stensrud

The question is somewhat vague, and there are various answers over the life cycle of an information system. And there are varying definitions of quality.

During an IS development, quality can be objectively defined as "delivery of the required functionality, on time and within budget." Under the objective definition, the ramifications of lack of quality include wasted time and dollars, late deliveries, missing functionality, and even cancellation. I haven't run across any expanded definitionthat didn't get into subjective areas (i.e., user friendliness, etc.), but for development the results would be the same.

In a delivered IS development, quality could be said to be lacking if there are significant bugs, missing functionality (incompleteness), inconsistency, hard to use, etc. Depending on whether these qualities were recognized, the results could include inability to derive intended information, poor decision support, inefficiency, high cost, or even complete rejection by theintended users.

I

by neufarth

As I define quality as "doing the right thing and doing the thing right", under your premise you end up with the wrong thing or you get the right thing at the wrong time/price or you get something that's constantly in a state of repair.

by jacky chin

I'll put it this way, 'Do the right thing as the first time'. Of course, doing project management, you have to deal with alot of 'estimation' in term of time, manpower and some other resources in order to complete the project. Those are the factors that can be caused a failure of the project. Always, share your idea and experience with someone/your senior.

by ga-pilot

The other responses have covered the obvious.
When looking at the bigger picture, one needs to consider, who is making the judgement call on quality. Hopefully there is a Quality Assurance (QA) unit involved, that is actually looking at the project requirements, the business need, and rating how the product stacks up.

One must take care that their QA organization is not merely the entry point into change management for modification of the production environment. If this is the case, then typically the developers would, by default, self certify, and deploy via change management, possibly with business errors.

by uk77062

Failure of quality in information systems will result in flawed information, or minimally, ineffective information. Poor quality information (or lack of information) will impact business results and sub-optimize business performance.

This discussion is closed to new replies.