PROJECT MANAGEMENT
According to CIO.com, 50% of software projects fail. Not mine.
When I manage a project, if I do not run the specifications phase, I go through the specifications completely and ensure that they can be successfully developed. I create a data model that will allow them to be developed. I also create any other documents needed to spot holes or contradictions in the specifications.
I moved into Business Systems Analysis as I was tired of being on failed projects. I found that most projects failed as the persons creating the specifications had little idea of how to ensure the specs were complete, comprehensive and able to be developed.
By the time the specs are turned over to developers, they can be developed and I can help them do that.
Waterfall And Agile
I have managed and worked on Waterfall projects. I have managed and worked on Agile projects.
I personally think that much of the discussion about which method to use, Waterfall, Agile/Scrum, Agile/Kanban, etc., is based on so many project managers' inability to successful pull off a complex development effort.
I personally think that people are trying to put rules in place so managers do not need to understand what to do.
When I run a project, I make sure I know what is being built and how it will be built. I know the data model, I know the functionality, I know enough or learn enough about the different technologies involved to understand how they will work together.
I am excellent at working with technical staff so their work can seamlessly fit into the overall product.
The projects I produce have a very low bug rate. I do not like the current acceptance of "just good enough". It is much more cost effective to ensure the software works correctly during development than to wait and have to fix it one item at a time over and over again.