What are you supposed to do when you are onboarding on a project at the UAT phase? How can you be responsible for the result when you have no influence on the quality of the knowledge and documents handed over to you? And on top of that, you are the only analyst on the project…
Everyone knows how to work "correctly". At that, the question of how to build a scheme of work when an analyst onboards on a project where the UAT phase is almost upon us, no artefacts are left behind, the team plays partisans and arranges strength tests, and the customer builds a gallows because of unfulfilled expectations and hopes - can often be questionable even for experienced analysts.
Within the talk, the author
will offer useful advice on how to release a project with the highest possible
quality based on real cases from the personal experience and the experience of her