I doubt that there are many IT projects of any size that can be deemed a complete success in all respects.  There is always something that could have been done better, differently or more cheaply.  The post-implementation review process is there precisely to identify those 'failings' and, if it doesnt find any, can itself be deemed a failure!

I also would agree that an individual can perform their own role superbly while the overall outcome is an unmitigated disaster.

But a project requires team work and the ideal team is a team of peers. Whatever my nominal role, I should have equal respect with all other members, take an interest in the overall project and contribute in whatever way I can to its success.  If I see something going wrong, whether or not it is my nominal responsibility, it is my duty to my colleagues (and to myself) to point it out and offer a solution.  If they reject my suggestion and the project fails as a consequence, then it was, at least in part, my fault for not being persuasive enough!

At the end of the day, it's a question of the attitude that you bring to your work - and life in general.  You also will find that (positive) contributors usually end up with more interesting projects and more successful careers.