Originally posted by suityou01
View Post
Having delivered two major projects for clientco and now being made the technical lead on a politically exposive one I have handed over the two projects to a new BA who has a Masters. The first thing this twat is done is point out that (my specs are not to some standard or other and pointed out that some of my flow diagrams / UML diagrams etc are not up to scratch). Hence I'm having to do some extra work in my time to find out what the fook he meant for my next project.
Regardless both systems are up and running and we have onboarded a number of clients which has paid for my time for the last 18 months. The BA's last project was late & the client was well pissed off. Not because his documentation was bad, it wasn't it was exceptional much better than mine but he'd completely not understood the source systems and hadn;t worked out the extraction & transformation rules correctly. So effectively all the reporting was wrong. He's still trying to sort it out 3 months later.
So in response Suity, you can stick your documentation up your arse and start sounding off when you actually finish a project successfully.


Comment