Starting your own PMO

If your organization does not have a PMO or has one that has been disappointing in its benefits, then this discussion may be for you! I have an opinion that there are “Five ‘P’s in PMO”: Project, Program, Portfolio, Process, and People.  Others don’t necessarily agree with me but then they are not writing THISContinue reading “Starting your own PMO”

Project in Recovery (not THAT Recovery!)

When a project has been close to failure and shut down is not an option then my repetitive approach to resolving the remaining issues usually goes something like this: Agree on the Recovery Project Charter Scope Objectives Budget Staff List of Open Risks, Issues, Change Request (preferably these lists will be placed in Recovery ProjectContinue reading “Project in Recovery (not THAT Recovery!)”

Project in Trouble?

Despite all of our best efforts, some projects end up in trouble and they need to be ‘saved’ or ‘shut down’! Making the ‘shut down’ decision is very difficult but must be considered once a project that is in trouble is identified.  Some of the questions I have used in the past to determine whetherContinue reading “Project in Trouble?”

Structure Programming – Advice from IT.Toolbox

The only point I disagree with in this article is about replicating code for readability! DO NOT REPLICATE code ’cause it also replicates Maintenance Costs! Other than that – Bravo to the author: Craig Borysovitch! http://it.toolbox.com/blogs/enterprise-solutions/systems-development-structured-programming-guidelines-48980   bgbg

Process Modeling

Flowcharts, Data Flow Diagrams, Swim Lane diagrams, Use Cases and other constructs have been used to reflect what a Business or Systems Analyst thinks the client is describing when they talk about Business Process and the use of information in the conduct of their business. These diagrams have structure, syntax, and rules that have beenContinue reading “Process Modeling”

The Software Engineering Handbook

Information Technology (IT) has been moving towards a “Popcorn Culture” for many years where our Practitioners are regularly looking for a quick POP of a little progress in technology.  When I was growing up in the world of computer programming, we were taught that this work took planning, design, testing, and re-work before a productContinue reading “The Software Engineering Handbook”