One Size (Does Not) Fit All
As organizations attain a higher level of information systems, project management maturity, one of the key focus areas, is incorporating the use of a consistent approach for project and portfolio management. This focus area has twofold objectives—do the right projects and do projects right. Thus, this becomes part of the charter of the information systems project management office (PMO). In order to achieve the objectives in the charter, the PMO defines several tactics, including standards and procedures, templates and governance processes for managing information systems projects.
One of these standards that PMO defines for managing information systems projects is a project management methodology. Most widely used project management methodology is the waterfall model. In this model the progress of a project is seen flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design (validation), construction, testing and maintenance. It should be apparent that this model has its origins in the manufacturing and construction industries. And that raises a question: Do all information systems projects need to follow the same model?
Different Strokes (Approaches) For Different Folks (Projects)
In an organization, a wide variety of strategic, regulatory and discretionary information systems projects are
Please log in or sign up below to read the rest of the article.
|
"Being powerful is like being a lady. If you have to tell people you are, you aren't." - Margaret Thatcher |




