View source for Project dashboard

=== Creating project dashboard ===
Again, returning to ISOs definition of project as ''“temporary endeavor to achieve one or more defined objectives”'' <ref name=ISO/>. As the quotes implies, projects have an end date. Thus, project dashboards also have an end date. However, during their active time used for project management they are updated more frequently to monitor project progress and performance. Therefore, there are some factors the project manager must consider before creating project dashboard to determine if a project dashboard will be beneficial for the specific project. Factors include <ref name=PMI/>: 

*Duration of project. If the project is running over a long period, it may be possible to gather sufficient data and create an effective dashboard for project users. If the project is running for a short period, it should be considered if using resources to create and update a project dashboard adds value. 

*Project staffing. Consider if potential users of the project dashboard have the necessary understanding and training to benefit of the dashboard. Are there competencies available to create and update a dash-board.

*Urgency of information. It should be considered if a regular meetings or written reports is sufficient communication for project success or frequently updated project reporting add value for the stakeholder of the project. 

*Availability of technology. Is a license for a dashboard system available. If not, would an investment in a license be beneficial. 

Once it has been deemed beneficial to create a project dashboard, the process of assessment and designing can start. Krezner presents the process of creating a project dashboard by following these steps (illustrated in figure 3)<ref name=Kerzner/>:

'''1. Needs assessment.''' First there must be and understanding of why a project dashboard should be created. There must be a clear intention with the what the project dashboard is solving and what the benefits for creating a project dashboard will be. By having a clear intention with the project dashboard, then designing the dashboard becomes more purposeful. 

'''2. Selecting and connecting sufficient data input.''' Informed decision making requires effective information and data. it is imperative to establish the meaning of effective information and data, within the context of the specific project. It is necessary to deter-mine if sufficient information and data is available to effectively support the intention of the project dashboard. Furthermore, it must be considered, which stakeholders the project dashboard is targeting. Depending on the stakeholder’s role in the project, the data needed will differ. It is possible to create several dash-boards each targeting different project stakeholders. Moreover, it is essential to make sure that the data can connect with the project dashboard and is able to be updated in the chosen frequency of the project.

'''3. Choosing Key Performance indicator.''' When choosing the KPIs they must be aligned with the intention of the project dashboard. Furthermore, it should be considered if sufficient data is available to effectively measure the chosen KPIs and if not, then consider if more data and information will be gathered over time to increase the quality of the delivery of the chosen KPI. 

'''4. Selecting visuals'''' The visuals of the dashboard should be chosen to display the information in the most intuitive and effective way possible for the project stakeholders. Including the primary users will increase the likelihood of the visuals being suited for them and not the designer. 

'''5. Secure interaction of project dashboard with stakeholder.'''
It is imperative that the project dashboard is designed in regard to the users of the dashboard. Kerzner argues that the core attributes of project dashboards concern aesthetic appearance, which is appealing to the targeted user, easily understood, and remembered, will enhance the likelihood of stakeholder inter-action with the project dashboard. 

'''6. Maintenance''' Project manager should secure resources are allocated to maintain the project dashboard and update it concurrently as the project unfolds. This will allow the project dashboard to maintain relevant throughout the lifecycle of the project. 

It should be emphasized that the critical step of creating a project dashboard is the pre-work which is to be done in step 1 to 3. The quality of the project dashboard is a direct result of the work, which has been made in these steps.

[[File:implement.png|400px|thumb|centre| Figure 3: Creating project dashboards steps. Own figure based on <ref name=Kerzner/>]]

Figure 3 illustrates the necessary steps to create a project dashboard. The process is a cycle as the project dashboard should continuously be evaluated to secure the project dashboard is tracking and communicating the most efficient KPIs for project progress and create value for the key users to be able to make informed decisions.