Test report sent; now the fighting starts

[Mich the Tester]

Have sent test report to project manager and acceptant. Basically, the system does pretty much what the design says it should (which itself is a historic moment in the annals of systems development), but the acceptant won’t accept the system as he’s saying the design doesn’t address his business needs, despite having signed off on it. Project Manager rightly says he's delivered what was asked for and should now recieve praise from all around and sign-off.

I have suggested a compromise which should keep them occupied long enough for me and Project Manager and Program Manager to send some more invoices while they thank me for rescuing them all from a Catch-22 situation; Project Manager should cost and estimate all changes demanded by acceptant while acceptant writes business cases for each change required, assisted in doing so by me. F**king obvious really, but try explaining that to permies.

This could blow up in my face, or it could give me 2 more months invoicing.

[EternalOptimist]

Have sent test report to project manager and acceptant. Basically, the system does pretty much what the design says it should (which itself is a historic moment in the annals of systems development), but the acceptant won’t accept the system as he’s saying the design doesn’t address his business needs, despite having signed off on it. Project Manager rightly says he's delivered what was asked for and should now recieve praise from all around and sign-off.

I have suggested a compromise which should keep them occupied long enough for me and Project Manager and Program Manager to send some more invoices while they thank me for rescuing them all from a Catch-22 situation; Project Manager should cost and estimate all changes demanded by acceptant while acceptant writes business cases for each change required, assisted in doing so by me. F**king obvious really, but try explaining that to permies.

This could blow up in my face, or it could give me 2 more months invoicing.

Sounds like a win/win to me.
or even a win/win/win

[suityou01]

Have sent test report to project manager and acceptant. Basically, the system does pretty much what the design says it should (which itself is a historic moment in the annals of systems development), but the acceptant won’t accept the system as he’s saying the design doesn’t address his business needs, despite having signed off on it. Project Manager rightly says he's delivered what was asked for and should now recieve praise from all around and sign-off.

I have suggested a compromise which should keep them occupied long enough for me and Project Manager and Program Manager to send some more invoices while they thank me for rescuing them all from a Catch-22 situation; Project Manager should cost and estimate all changes demanded by acceptant while acceptant writes business cases for each change required, assisted in doing so by me. F**king obvious really, but try explaining that to permies.

This could blow up in my face, or it could give me 2 more months invoicing.

Was it just gaps in the requirements or were the requirements misinterpreted?
Was this a waterfall SDLC?
Who gathered the requirements?

[Mich the Tester]

Was it just gaps in the requirements or were the requirements misinterpreted?
Was this a waterfall SDLC?
Who gathered the requirements?

Package implementation. Board chose the package according to GCTPM*, department didn't agree in the first place, wanted something else; design covered differences to standard functionality. Acceptant agreed to designs without understanding the standard functionality. Development team have covered all the designs, but acceptant is still upset about the package. And rightly so; there should now be lots of RFCs to test.


*Golf Course Technology Purchasing Methodology

[suityou01]

Package implementation. Board chose the package according to GCTPM*, department didn't agree in the first place, wanted something else; design covered differences to standard functionality. Acceptant agreed to designs without understanding the standard functionality. Development team have covered all the designs, but acceptant is still upset about the package. And rightly so; there should now be lots of RFCs to test.


*Golf Course Technology Purchasing Methodology

What a shower.
Keeeeeeeeeeeep invoicing.