Quality vs Quantity

Many Information Production Projects require after process and functional setup development of reports for users. Reports can be deployed in updated production system or can be produced in Data Warehouse.

Printing reports like on the industrial line. IT likes to produce huge amounts of reports because it is better for their PR. Huge quantity of partly developed reports looks better in presentation comparing to only few reports that are finished and  of high quality. Yes, it is tempting situation to developers if it is not strictly prioritized what needs to be finished till the end first, next and so on. If time line and deadlines are truly very tight then quality vs quantity is an issue, because there is the real risk not all reports can be finished, tested, corrected on time. It is interesting to look fight between users and developers. Users start to test and find many bugs. Bugs are reported to developers but developers are concentrated on publishing of other “new” reports.

Huh, what a mess?! Or not

Is implementation plan defined? Priorities during testing and correcting period? Is testing and acceptance detailed and complete? Are issues communicated to management? Was there any decision?