by clicking the arrows at the side of the page, or by using the toolbar.
by clicking anywhere on the page.
by dragging the page around when zoomed in.
by clicking anywhere on the page when zoomed in.
web sites or send emails by clicking on hyperlinks.
Email this page to a friend
Search this issue
Index - jump to page or section
Archive - view past issues
Project Manager : Project Manager Dec Jan 2012
www.aipm.com.au Project Manager 29 28 Project Manager 2000’s 2000 PMBoK second edition published. Project management in The 2000s history Managing multiple simultaneous projects gained traction and a shift in focus from project deliverables to benefits – these are just two of many project- related events that defined the 2000s. By AlAn Stretton, lFAIPM It is perhaps too early to identify the most significant project-related events of the 2000s. However, a few features stand out. Simultaneous multiple projects The 2000s saw a proliferation of papers, articles, chapters and books on the simultaneous management of projects, some under the heading of program management, others labelled the management of portfolios of projects. Despite the surge of interest in program management, the literature is fragmented. As Engwall and Jerbrant put it: “Theories on multi-project settings have a limited empirical foundation; most of the contributions are either based on the author ’s practical experience or research findings from one specific industry, one type of project, or one type of organisation. “ We have little knowledge concerning which factors are context-specific and which factors are universal. Consequently, there is a need for comparative studies of multi-project settings from different contexts, with different kinds of project portfolios, and working under different environmental contingencies.” At the same time, computer- based advanced project management on several fronts, from facilitating the emergence of virtual teamwork to managing dispersed project teams. Outputs versus outcomes It was not until the 2000s that discussion on obtaining the benefits from the project gained traction. Some contributors on program management imply that the delivery of benefits/outcomes is the sole province of programs, and that projects are only concerned with deliverables/outputs. “Programs deal with outcomes; projects deal with outputs,” stated the Office of Government Commerce. This distinction has been criticised by Morris: “There is a view ... that project 2000 the y2K Project, known as the millennium bug, prompted many organisations to set up a project office to control and comply with their stakeholders regarding the y2K issue. 2001 Agile Alliance formed to promote ‘lightweight’ software development projects. 2009 three new core PrInCe2 manuals are released. 2008 AIPM Professional Competency Standards for Project Management are formally released. 2006 Australian Department of Defence makes a public release of Version 2 of its Competency Standards for Complex Project Managers.
Project Manager Oct Nov 2011
Project Manager Feb March 2012