With countless projects always under way, CIOs need to feel confident that their teams have things under control in terms of \n\nproject scope, budget, prioritization and time line. Few would argue that a project management office (PMO), \n\nwell-planned and implemented, won't go a long way toward governing projects to more satisfactory conclusions. For many CIOs, \n\nit's a requirement.\n\n"My philosophy is that there are three legs of the stool that are required in any successful IT department: a PMO, portfolio management and IT governance," says Eric Hungate, CIO of the Texas Association of School \n\nBoards, a nonprofit educational association.\nUsing Collaboration To Build A Project Management Methodology\nPMO adoption benefits from team-based efforts to create a framework\n\n\nIn smaller, more nimble organizations, CIOs can try unique models for project management and governance. In Hennepin County, \n\nMinn., PMO Director Pan Hall hired Karen Piet to work with a select group on a biweekly basis to set up an initial project management methodology. The 12-person \n\nteam is open to anyone in IT and to select business partners.\n\n"We call it the 'best practice' model. It's a grassroots effort that provides structure for different phases of project \n\nmethodology, template advice and other aspects of PMO oversight," says Hall.\n\nThis collaborative effort is very different from buying a set methodology or adopting a well-known practice. Instead, Piet \n\nasks the team about the best documentation for a particular phase of a given project, and what the deliverables should be. \n\nResponses are compiled and discussed, and form the basis of the methodology. "Adoption of the PMO has been much smoother with \n\nthis team-based effort, rather than going out and telling people that we have made the decision, and this is how it is going \n\nto be done," says CIO Toni Jelinek. \n\n-C.M., \nWhen it comes to setting up a PMO, all CIOs struggle with securing buy-in, demonstrating value and choosing the right project \n\nmethodology for the corporate culture. More than their larger-company peers, though, mid-market CIOs (those whose companies \n\nreport less than $2 billion in annual revenue) must grapple with finding staff and funding resources to develop an effective \n\nPMO. But a mid-market company's size and agility also allow its CIO to try out different processes that a larger company \n\nmight not risk. Below, four Council members share tactics to make their mid-market status an advantage when forming a PMO.\nAdvocate from the start. Mid-market CIOs have many priorities pulling them in different directions. That's why new CIOs \n\nshould seize the opportunity to jump-start a PMO. "I used my honeymoon as the first CIO to advocate for a PMO, and then \n\nstarted to get the basics established," recalls Hungate. "My first step was to hire a PMO director."\n\nMajor new projects can also help launch a PMO. "When I arrived at the county in 2004, it needed this type of discipline for \n\nthe large projects we had lined up, especially a huge ERP implementation," says Toni Jelinek, CIO of Hennepin County, Minn., \n\nwhich has an operating budget of $1.6 billion. Implementing an ERP system is complex and "with the PMO, county senior leaders \n\nhad a baseline to understand why project management would contribute to the overall success of the project," says Pan Hall, \n\nJelinek's director of enterprise PMO.\n\nYou don't need a big staff. "The size of a PMO is very dependent on the size of the IT organization, the \n\nscope of their activities," says Matt Hartzman, vice president of information services at the College of American \n\nPathologists, a $125 million organization. He recommends a lean staff approach. Hartzman has a single dedicated PMO manager \n\nand two other staff members, and then the virtual PMO is filled in unofficially by other IT staff. "All my project managers \n\nare considered part of the PMO," he says. "There is no solid-line reporting relationship to the PMO manager, but all project \n\nmanagers attend a weekly PMO meeting, abide by the same standards and requirements, and view themselves as a team, albeit a \n\nvirtual one."\n\nEducate the rest of the team. Jelinek asked Hall to not only assess what type of PMO the county needed but \n\nto do marketing across the organization about a PMO's benefits. Hall conducted one-on-one staff sessions, held road shows in \n\nother departments, and attended management meetings equipped with research data demonstrating value. He also highlighted \n\ngovernment-sector entities' PMO successes, rather than rely on private-sector case studies. To convince staff to embrace the \n\nPMO, Hall highlighted high-profile projects that had dragged on due to poor management and a lack of PMO oversight.\nPMO Templates to Try\nAt Pacific Blue Cross, the following are essential tools or templates used in the PMO project governance methodology.\n\n Monthly project portfolio traffic-light report \n Post-project review template\n Post-project review process\n Resource utilization spreadsheet\n Project role descriptions \t \n-C.M.\n\nStay nimble. The agile nature of a smaller organization can work in a CIO's favor. "We can move quickly: put \n\ntemplates in place, train the users and start seeing results," says Greg Brierley, PMO manager at $750 million Canadian \n\nhealthcare company Pacific Blue Cross. "We also make a point not to have an overly bureaucratic process with excess \n\noverhead."\n\nHaving Pacific Blue Cross located in one building also helped speed PMO implementation. However, Hennepin County's Hall \n\ncautions not to move too quickly. "Make sure the people around you are moving at the same pace; they need to internalize \n\nthings," she says.\n\nShow the value and benefits. A PMO's value is shown by the hard benefits it produces. All four CIOs are \n\ntracking metrics and highlighting benefits gained. Hungate has seen gains in operational efficiencies and project performance \n\nsince the PMO launched. Pacific Blue Cross cites cost benefits from better budget tracking, and more knowledge around project \n\nprioritization and where dollars should be spent. Hennepin County's IT team has a better understanding of project scope and \n\nindividual roles within large projects. "People have started to make decisions from a factual basis," says Hall. "Before, we \n\nwould have an idea and then execute. With the PMO, the planning stage of the project is in place. With that comes success."\n\nCarrie Mathews is group manager, member services, for the CIO Executive Council.