|
Project Server 2010 Training HOME
(1) Project Implementation Process Overview The process by which enterprise projects are created is as follows: An enterprise leader (also called the administrator) customizes Project Server in anticipation of the building of enterprise projects by project managers. That enterprise leader creates an enterprise resource pool whom project managers will later assign to their project, and establishes user accounts for people to log into Internet Explorer to see project data. Once this is done, project managers create enterprise projects on their own computers through Project Professional. They assign resources from the enterprise resource pool to tasks on the projects, and then post the files to Project Server, which is essentially a central depository of those files and its data. The information can then be viewed through a browser, e.g. Internet Explorer. The ability to see the data through the browser is called Project Web App (PWA). Depending on the permissions of a given user, they will have access to some or all of the features of Project Server. E.g. team members will be able to see their assignment to tasks in project via PWA, but will not be able to use the graphical Data Analysis views from multi-project analysis that higher-level management want to access.
In Detail
In the diagram above we see three areas: the Project Server, the Project Pro desktop application, and the Project Web App web client interface. Essentially the Administrator configures Project Server so that Project Pro users (mainly project managers) can interact with Project Server. The Admin establishes the enterprise resource pool in Project Server, which is the list of resources/team members that will be assigned to projects by project managers by using their copy of Project Pro (as shown in the lower left of the diagram). Likewise, the Admin establishes accounts so that users (project managers, team members, executives, et al) can log in from PWA web client (shown in the lower right of the diagram) and see data stored in Project Server. Finally, the Admin will modify the enterprise global file, which will customize the look and feel of Project Pro that project managers will see when they create enterprise projects in Project Pro. (That will also include pre-created enterprise templates that can be the basis of new enterprise projects created by the project manager in Project Pro.) Thus, Project Server is the location through which server accounts, the enterprise resource pool, the enterprise global and templates are formulated by the Administrator; Project Pro is where project managers create projects and assign resources that will be stored in Project Server; and Project Web App (PWA) is the web interface where team members and others will see data relevant to them. When the project manager starts up Project Pro (seen in the diagram in the lower left), the enterprise global version of a new project file loads into that computer's copy of Project Pro. The project manager then selects one of the enterprise project templates earlier established by the Admin, and builds a new enterprise project based on that template. The project manager modifies the project file as needed, accesses the pool of resources from the enterprise resource pool stored in Project Server, and assigns them to various tasks in the project as needed. When the data for the enterprise project is saved and published by the project manager, the MS Project file is stored in Project Server. Also, when the data is published to Project Server by the project manager, it becomes available through Project Web App (PWA). Team members log onto PWA (see lower right corner of diagram), which is essentially Internet Explorer, and see the tasks they have been assigned to across all projects created by project managers. It is also the place where they enter the completion of their task assignments, or alternatively enter timesheets-based completion of tasks plus their administrative time, such as sick leave. The team members will also be asked to fill out status reports and collaborate in various ways with the project manager. The project manager can interact with the team member through Project Pro and/or through PWA. Other stakeholders, especially executives can also get a comprehensive look at all projects, resource assignments, et al by logging into PWA as well. They can examine and manipulate powerful Business Intelligence dashboards that provide comprehensive analysis of high level information across Project Server through attractive and informative graphs and tables. Finally, Project Server (through Project Pro and PWA) allows for group collaboration on documents, risks, issues and other matters through the common "project sites" generated for each project.
(2) Project Proposal and Approval Process The process by which enterprise project proposals are submitted, evaluated, and approved are as follows: Administrators, resource managers, and PMO members collaborate to create a workflow for a process by which project managers and others can create project proposals. These stakeholders also develop a series of strategic goals by which the project managers will rate their project proposals. The project manager or other who initiates a project proposal begins by selecting a predefined project types which will be the basis of the proposal. The project type will indicate the workflow that the project manager must go through to secure approval. The project type will also determine the department or business unit that the proposal is made for (e.g. IT or HR, North America vs. EU, etc.). A portfolio of proposals for future projects is thus created based on a default and custom project type templates. Once the proposal is initiated by the project manager or other stakeholder, it normally goes through a number of stages, with approval points in between. When an approval has been given at a given point/stage, the proposer of the project can move to the next stage in the approval process, which normally requires the project manager or other to enter more detailed information about the project, such as whether it meets organizational or departmental goals (called "business drivers"), what its expected cost is, and so forth. Meanwhile PMO members or other are constantly accumulating a portfolio of these proposals for future projects. They then create scenarios by which they determine which are the best proposals and which to commit to. This is determined by looking at the entire group of proposals, selecting those that are most vital to the organization (or business unit, such as department); which meet most clearly the critical strategic goals of the company; which meet the cost constraints of the organization or business unit; which can move forward given the current resource availability based on data stored in the enterprise resource pool; what the risks involved are; and so forth. Out of this analysis, a determination is made of which projects should be given the go ahead. Once committed to, the project manager or others can begin to create their project in earnest (whether through Project Professional 2010 desktop application, with its comprehensive set of tools, or by creating a Project Web App (PWA) based project). Finally, portfolio analysts, resource managers, and other interested parties can examine and manipulate powerful Business Intelligence dashboards that provide comprehensive analysis of proposal workflow information through attractive and informative graphs and tables.
Order Microsoft Project Server 2010 Online Training Back to Main | See Course Outlines Email Us or call 925-283-1146 |
