|
|
| (8 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | '''Welcome to the project Navigator FAQ'''
| |
| | | | |
| − | {{Table of Content}}
| |
| − |
| |
| − | ==<span style="font-family:Trebuchet MS; color: SteelBlue">'''NPMS RENEWAL'''</span>==
| |
| − | {{Collapse
| |
| − | |1=The NPMS Renewal initiative aims to put in place a more comprehensive project management process that is better aligned to industry best practices. NPMS Renewal will address requests from Public Services and Procurement Canada’s (PSPC) project management community for improved efficiency and simplicity as well as recent Treasury Board of Canada Secretariat (TBS) requirements associated with its new Directive on the Management of Projects and Programmes and Policy on the Planning and Management of Investments
| |
| − | This initiative includes four critical and interrelated components:
| |
| − | ● an interim NPMS update
| |
| − | ● project transition activities associated with Benefits Realization
| |
| − | ● the PSPC Project Navigator
| |
| − | ● the new Project Management Curriculum
| |
| − |
| |
| − | The end goal is that the PSPC Project Navigator will completely replace the current NPMS by winter 2021, with existing projects becoming fully compliant through phased implementation over three years.|bg=#ececec|padding=10px
| |
| − | |2=What is the National Project Management System (NPMS) Renewal initiative?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=NPMS Renewal offers PSPC the opportunity to holistically assess how the NPMS has evolved and improve upon areas that have gradually become cumbersome. The result of this assessment will be the evolution of the NPMS into the newly-branded PSPC Project Navigator—a single linear process with consolidated documentation and project gates.
| |
| − |
| |
| − | By streamlining the documentation, project managers at PSPC are able to spend more time on planning and less time on repetitive tasks. The revitalized process introduces simplicity and integration, while empowering anyone managing projects to achieve even greater levels of delivery excellence and efficiency.|bg=#ececec|padding=10px
| |
| − | |2=This initiative sounds like a lot of work. How will I be expected to implement this change while maintaining an already busy workload?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=At the Project Management & National Capital Area Project Delivery service lines town hall held on January 24, 2020, Assistant Deputy Minister Stéphan Déry referenced the TBS President’s mandate letter, which included a requirement to “improve project management capabilities so that all major projects in government are led by a certified professional with at least five years of experience.” To realize this, the new Project Management Curriculum will be launched to correspond with learning plan submission deadlines. The Curriculum is based on a professionally-recognized approach to competency development, and will help us, as a department, to establish a clearer picture of our project management capacity while better matching knowledge with project complexity. Moreover, the new Project Management Curriculum provides career development opportunities and a path for participants to achieve Project Management Institute (PMI) Project Management Professional (PMP) certification.|bg=#ececec|padding=10px
| |
| − | |2=How will we build competencies associated with the PSPC Project Navigator?|Category=NPMS Renewal}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">To facilitate an easier migration from the old to the new, a dedicated team has been put in place to inform stakeholders, to provide learning opportunities and resources, and to establish and support a regional network of PSPC Project Navigator and Project Management Curriculum change agents. The intent is to ensure a continual flow of information and updates, and to provide opportunities to hear stakeholder’s thoughts and concerns.
| |
| − | </p>|bg=#ececec|padding=10px
| |
| − | |2=The Department has experienced considerable change in the recent past and many people are experiencing fatigue. How will we support employees through this renewal?
| |
| − | }}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">"Due to the TBS requirements, this initiative has had an accelerated schedule. To help ease implementation, the components are being launched sequentially, and a PSPC Project Navigator proof of concept exercise comprising of three to five projects per region will occur to identify and address issues that may arise. To be clear, this exercise will not test a fully functioning PSPC Project Navigator product, but rather will be a period during which documentation components and the gating model are reviewed and improved. Subsequent results will then be submitted to the appropriate governing bodies for their approvals.
| |
| − |
| |
| − | In addition, it is important to understand that building employee knowledge about, and ability with, the PSPC Project Navigator and Project Management Curriculum will continue well after the launch dates. Change agents and tools are being put in place to support those managing projects, including feedback mechanisms that will enable users to report on experiences and highlight areas that may need improvement."
| |
| − | </p>|bg=#ececec|padding=10px
| |
| − | |2=Do we have enough time to properly prepare for and launch the NPMS Renewal components?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">No, just behave in line with the [[code of conduct]] and the [[GCpedia:Terms and conditions of use|terms and conditions of use]]. Tens of thousands of Public Servants have registered accounts on GCpedia and thousands of GCpedians across the country use it every day as part of their work. It has proven its value as an indispensable work tool and many organizations have developed approaches for using GCpedia that give explicit approval to employees for using the wiki. Keep in mind that secure, confidential, and sensitive information does not belong on GCpedia. </p>|bg=#ececec|padding=10px
| |
| − | |2=Do I need permission from anyone to use GCpedia?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">No you do not need to seek the permission of TBS to use GCpedia as long as you abide by the [[code of conduct]] and the [https://gcconnex.gc.ca/terms-termes Terms of Use].</p>|bg=#ececec|padding=10px
| |
| − | |2=Do we need to consult TBS prior to commencing our project?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">If by 'governance models' you mean Westminster, and with it, Parliamentary relations or Ministerial responsibility, it doesn't change that. It does, however, change ''how'' we work, which does change regularly. It makes what was ''vertical'' now more ''horizontal'', which is a drastic change for more parochial departments which were overdue for change and who had their silos reinforced for a long time (they don't need to be; [[Intellipedia]] demonstrated the otherwise impossible breakdown of necessary silos). The public service isn't the same public service of 20 years ago, where information (before the Internet) needed to be controlled, counted and filed away. Now information is recognized for its possible value, which increases with input (collaboration) and connections (distributed). Collaborative tools (like wikis) and social media accelerate this information sharing, retrieval and creation, adding value in so many more values with each iteration.</p>|bg=#ececec|padding=10px
| |
| − | |2=How does the fact that we are doing this in a mass collaboration, distributed way change governance models?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">
| |
| − | * By distinguishing ''public servant'' from ''department representative''
| |
| − | * Make recognition based on ''people'' vs. department (your department is merely a ''tag'' to define you, like your title). People representing themselves (instead of their department) at meetings, recognized for their skill, insight and information sharing. Central agencies providing ''support'', direction and even ''protection''</p>|bg=#ececec|padding=10px
| |
| − | |2=How do we get all these smart people actually working together on real problems in real time?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">
| |
| − | All pages on GCpedia can be seen by all users. GCpedia sysops can protect a page from editing if there is a strong justification for doing so (i.e. protecting a template that is used thousands of times on the wiki). If you need your page protected to prevent other users from editing it, ask yourself whether it belongs on GCpedia in the first place. A simple alternative to protecting a page is to use the template {{tl|protected}}, which asks users to refrain from editing the page.</p>|bg=#ececec|padding=10px
| |
| − | |2=Why can’t we have our own departmental pages on GCpedia that aren't accessible to other departments?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;"> Members of the [[Chief Information Officer Council (CIOC)]] provide funding to the [[GCTools Team]] to support operations of GCpedia and GCconnex.</p>|bg=#ececec|padding=10px
| |
| − | |2=Is there a cost to using GCpedia?}}
| |
| − |
| |
| − | {{Collapse
| |
| − | |1=<p style="text-align:justify;">Yes, federal government employees total approximately 250,000 Canada-wide, which is not a lot of users in the large scheme of wiki/web use. Pages are lightweight in terms of memory use because they contain “thin” media-wiki code. Maximum capacity (all Government of Canada) was considered in the planning stage.</p>|bg=#ececec|padding=10px
| |
| − | |2=Can GCpedia support every employee in the federal government?}}
| |
| − | <br>
| |
