Project dashboard - Revision history

Fie Fredshavn Nielsen: /* Implementing Project Dashboards */

2022-03-17T19:04:32Z

Implementing Project Dashboards

← Older revision		Revision as of 19:04, 17 March 2022
Line 89:		Line 89:

	== Implementing Project Dashboards ==		== Implementing Project Dashboards ==
	When the dashboard has been created and designed accordingly to the project and the ~~primary~~ users, then the dashboard can be implemented. The implementation process must take the specific project circumstances and stakeholders into consideration. Dashboards vary depending on the organization and in some cases the departments. Furthermore, it may not be all stakeholders who are familiar with dashboards. By simply setting up the dashboard there is a risk of the dashboards not being used as intended <ref name=Kerzner/>.		When the dashboard has been created and designed accordingly to the project and the key users, then the dashboard can be implemented. The implementation process must take the specific project circumstances and stakeholders into consideration. Dashboards vary depending on the organization and in some cases the departments. Furthermore, it may not be all stakeholders who are familiar with dashboards. By simply setting up the dashboard there is a risk of the dashboards not being used as intended <ref name=Kerzner/>.

	Rasmussen et. al argues that to obtain a successful implementation of dashboards it is important to ~~con-sider~~ the people related items and the technical related items. The people related items include identifying responsibility areas and assigning roles regarding the ~~dash-board~~. This includes identifying the ~~primary~~ users, executive sponsors, implementation teams, KPI and metric responsible <ref name=Rasmussen/>. By having clearly defined and assigned roles and securing these individuals has the capability or gets the necessary training to fulfill the assigned role, then implementation of project dashboard in regard to people related items will be smoother.		Rasmussen et. al argues that to obtain a successful implementation of dashboards it is important to consider the people related items and the technical related items. The people related items include identifying responsibility areas and assigning roles regarding the dashboard. This includes identifying the key users, executive sponsors, implementation teams, KPI and metric responsible <ref name=Rasmussen/>. By having clearly defined and assigned roles and securing these individuals has the capability or gets the necessary training to fulfill the assigned role, then implementation of project dashboard in regard to people related items will be smoother.
	The technical related items include the tools and platform considerations, such as identifying the data source, securing funding for software, hardware, and consulting, selecting the appropriate software and hardware to create the project dashboard and establishing the components and metrics to be included. By having clearly defined the technical scope of the dashboard and having done thorough preparation work the actual set-up of the technical system will provide the ideal situation for implementation for the technical related items <ref name=Rasmussen/>.		The technical related items include the tools and platform considerations, such as identifying the data source, securing funding for software, hardware, and consulting, selecting the appropriate software and hardware to create the project dashboard and establishing the components and metrics to be included. By having clearly defined the technical scope of the dashboard and having done thorough preparation work the actual set-up of the technical system will provide the ideal situation for implementation for the technical related items <ref name=Rasmussen/>.

	The technical implementation itself is not the most difficult part of implementing a project dashboard. The more thorough the team has been in considering the above-mentioned technical items and ensuring having the right capabilities handle these tasks, the smoother the implementation of the technical part of the project dashboard will be. The most difficult part of implementing a project dashboard is however the people related items and having the stakeholders engage with the technical system. Project managers must collaborate and communicate with the project stakeholders and especially the ~~primary~~ users. This will enable the ~~primary~~ users to accept and actively use the project dashboard. Thus, the value and ~~bene-fits~~ of a project dashboard can be obtained. Therefore, having a somewhat sufficient project dashboard, which has active users is better than having a perfect project dashboard which no one uses <ref name=PMI/> <ref name=Rasmussen/>.		The technical implementation itself is not the most difficult part of implementing a project dashboard. The more thorough the team has been in considering the above-mentioned technical items and ensuring having the right capabilities handle these tasks, the smoother the implementation of the technical part of the project dashboard will be. The most difficult part of implementing a project dashboard is however the people related items and having the stakeholders engage with the technical system. Project managers must collaborate and communicate with the project stakeholders and especially the key users. This will enable the key users to accept and actively use the project dashboard. Thus, the value and benefits of a project dashboard can be obtained. Therefore, having a somewhat sufficient project dashboard, which has active users is better than having a perfect project dashboard, which no one uses <ref name=PMI/> <ref name=Rasmussen/>.

	== Limitations of project dashboard ==		== Limitations of project dashboard ==

Fie Fredshavn Nielsen: /* Choosing key Performance indicators */

2022-03-17T18:56:42Z

Choosing key Performance indicators

← Older revision		Revision as of 18:56, 17 March 2022
Line 41:		Line 41:

	=== Choosing key Performance indicators ===		=== Choosing key Performance indicators ===
	To achieve the benefits as mentioned above it is crucial to establish the right KPIs for the individual dash-board. This is important, because ''"You cannot correct or improve something that cannot be effectively identified and measure (Kerzner, 2017, p. 1)."<ref name=Kerzner/>'' Thus, it is imperative to establish an understanding of what are ~~effective KPIs~~, within the context of the specific job, objective or others task the dashboard is to ~~measure~~. For certain dashboards common KPIs such as time and cost can be sufficient. For other dash-boards customized metrics may be required <ref name=Kerzner/>. In general dashboards should be aligned with the company’s strategic and business goals <ref name=Pauwels/>. Furthermore, dashboards should only include the necessary KPI which must be relevant and communicated in regard to the primary users of the dashboards. Occupying the limited space on the dashboard with wrong or unnecessary KPIs will lead to the dashboard becoming redundant <ref name=Few/>.		To achieve the benefits as mentioned above it is crucial to establish the right KPIs for the individual dash-board. This is important, because ''"You cannot correct or improve something that cannot be effectively identified and measure (Kerzner, 2017, p. 1)."<ref name=Kerzner/>'' Thus, it is imperative to establish an understanding of what the efficient KPIs are, within the context of the specific job, objective or others task the dashboard is to monitor. For certain dashboards common KPIs such as time and cost can be sufficient. For other dash-boards customized metrics may be required <ref name=Kerzner/>. In general dashboards should be aligned with the company’s strategic and business goals <ref name=Pauwels/>. Furthermore, dashboards should only include the necessary KPI which must be relevant and communicated in regard to the primary users of the dashboards. Occupying the limited space on the dashboard with wrong or unnecessary KPIs will lead to the dashboard becoming redundant <ref name=Few/>.

	===Visualization===		===Visualization===

Fie Fredshavn Nielsen: /* Dashboards as visual display */

2022-03-17T18:54:20Z

Dashboards as visual display

← Older revision		Revision as of 18:54, 17 March 2022
Line 8:		Line 8:
	The following section will give an introduction to the general concept of dashboard. Followed by a description of the importance of choosing the right Key Performance Indicator (KPI) for the dashboard and how the information and data is visually displayed to enhance communication.		The following section will give an introduction to the general concept of dashboard. Followed by a description of the importance of choosing the right Key Performance Indicator (KPI) for the dashboard and how the information and data is visually displayed to enhance communication.

	[[File:dashboard2.png\|500px\|thumb\|Figure 1:Example of dashboards <ref name=~~Krezner~~/>]]		[[File:dashboard2.png\|500px\|thumb\|Figure 1:Example of dashboards <ref name=Kerzner/>]]
	===Concept of dashboard===		===Concept of dashboard===

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:53:14Z

Creating project dashboard

← Older revision		Revision as of 18:53, 17 March 2022
Line 67:		Line 67:
	*Availability of technology. Is a license for a dashboard system available. If not, would an investment in a license be beneficial.		*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 <ref name=Kerzner/>:		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.		'''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.

Fie Fredshavn Nielsen: /* Implementing Project Dashboards */

2022-03-17T18:52:35Z

Implementing Project Dashboards

← Older revision		Revision as of 18:52, 17 March 2022
Line 89:		Line 89:

	== Implementing Project Dashboards ==		== Implementing Project Dashboards ==
	When the dashboard has been created and designed accordingly to the project and the primary users, then the dashboard can be implemented. The implementation process must take the specific project circumstances and stakeholders into consideration. Dashboards vary depending on the organization and in some cases the departments. Furthermore, it may not be all stakeholders who are familiar with ~~dash-boards~~. By simply setting up the dashboard there is a risk of the dashboards not being used as intended <ref name=Kerzner/>.		When the dashboard has been created and designed accordingly to the project and the primary users, then the dashboard can be implemented. The implementation process must take the specific project circumstances and stakeholders into consideration. Dashboards vary depending on the organization and in some cases the departments. Furthermore, it may not be all stakeholders who are familiar with dashboards. By simply setting up the dashboard there is a risk of the dashboards not being used as intended <ref name=Kerzner/>.

	Rasmussen et. al argues that to obtain a successful implementation of dashboards it is important to con-sider the people related items and the technical related items. The people related items include identifying responsibility areas and assigning roles regarding the dash-board. This includes identifying the primary users, executive sponsors, implementation teams, KPI and metric responsible <ref name=Rasmussen/>. By having clearly defined and assigned roles and securing these individuals has the capability or gets the necessary training to fulfill the assigned role, then implementation of project dashboard in regard to people related items will be smoother.		Rasmussen et. al argues that to obtain a successful implementation of dashboards it is important to con-sider the people related items and the technical related items. The people related items include identifying responsibility areas and assigning roles regarding the dash-board. This includes identifying the primary users, executive sponsors, implementation teams, KPI and metric responsible <ref name=Rasmussen/>. By having clearly defined and assigned roles and securing these individuals has the capability or gets the necessary training to fulfill the assigned role, then implementation of project dashboard in regard to people related items will be smoother.

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:52:02Z

Creating project dashboard

← Older revision		Revision as of 18:52, 17 March 2022
Line 68:		Line 68:

	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 <ref name=Kerzner/>:		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 <ref name=Kerzner/>:
	~~[[File:implement.png\|400px\|thumb\|centre\| Figure 3: Creating project dashboards steps. Own figure based on <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.		'''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.
Line 74:		Line 73:
	'''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.		'''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.

	~~[[File:Core attributes.png\|250px\|thumb\|Figure 4: Dashboards core attributes <ref name=Kerzner/>]]~~
	'''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.		'''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.

Line 85:		Line 83:

	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.		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.

	== Implementing Project Dashboards ==		== Implementing Project Dashboards ==

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:45:34Z

Creating project dashboard

← Older revision		Revision as of 18:45, 17 March 2022
Line 68:		Line 68:

	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 <ref name=Kerzner/>:		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 <ref name=Kerzner/>:
	[[File:implement.png\|400px\|thumb\|centre\| Figure 3: ~~Project~~ dashboards ~~implementations~~ steps. Own figure based on <ref name=Kerzner/>]]		[[File:implement.png\|400px\|thumb\|centre\| Figure 3: Creating project dashboards steps. Own figure based on <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.		'''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.

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:44:03Z

Creating project dashboard

← Older revision		Revision as of 18:44, 17 March 2022
Line 74:		Line 74:
	'''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.		'''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.

			[[File:Core attributes.png\|250px\|thumb\|Figure 4: Dashboards core attributes <ref name=Kerzner/>]]
	'''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.		'''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.
	~~[[File:Core attributes.png\|250px\|thumb\|Figure 4: Dashboards core attributes <ref name=Kerzner/>]]~~

	'''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.		'''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.

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:43:35Z

Creating project dashboard

← Older revision		Revision as of 18:43, 17 March 2022
Line 68:		Line 68:

	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 <ref name=Kerzner/>:		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 <ref name=Kerzner/>:
	[[File:implement.png\|400px\|thumb\|centre\| Project dashboards implementations steps. Own figure based on <ref name=Kerzner/>]]		[[File:implement.png\|400px\|thumb\|centre\| Figure 3: Project dashboards implementations steps. Own figure based on <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.		'''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.
Line 75:		Line 75:

	'''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.		'''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.
	[[File:Core attributes.png\|250px\|thumb\|Figure 2: Dashboards core attributes <ref name=Kerzner/>]]		[[File:Core attributes.png\|250px\|thumb\|Figure 4: Dashboards core attributes <ref name=Kerzner/>]]

	'''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.		'''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.

Fie Fredshavn Nielsen: /* Creating project dashboard */

2022-03-17T18:42:45Z

Creating project dashboard

← Older revision		Revision as of 18:42, 17 March 2022
Line 68:		Line 68:

	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 <ref name=Kerzner/>:		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 <ref name=Kerzner/>:
	[[File:implement.png\|~~450px~~\|thumb\|centre\| Project dashboards implementations steps. Own figure based on <ref name=Kerzner/>]]		[[File:implement.png\|400px\|thumb\|centre\| Project dashboards implementations steps. Own figure based on <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.		'''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.
Line 75:		Line 75:

	'''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.		'''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.
	[[File:Core attributes.png\|~~200px~~\|thumb\|Figure 2: Dashboards core attributes <ref name=Kerzner/>]]		[[File:Core attributes.png\|250px\|thumb\|Figure 2: Dashboards core attributes <ref name=Kerzner/>]]

	'''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.		'''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.