Project Dashboards - Revision history

Tummasm: /* Implementation Process for Project Dashboards */

2021-03-04T22:36:11Z

Implementation Process for Project Dashboards

← Older revision		Revision as of 22:36, 4 March 2021
Line 227:		Line 227:
	:<span style="font-size:110%">'''4. Plan practical use and gain support'''</span>		:<span style="font-size:110%">'''4. Plan practical use and gain support'''</span>

	::When the data collection and dashboards are in place, it is time to plan the practical use of the dashboard – this is where the actual value is gained for the project. Without planning its practical use, it is likely that the project dashboard will not facilitate improvements and hereby will not increase performance. It is therefore paramount that the [change management] within the execute and control phase of the project is developed, and that the role of the dashboard is clearly established.		::When the data collection and dashboards are in place, it is time to plan the practical use of the dashboard – this is where the actual value is gained for the project. Without planning its practical use, it is likely that the project dashboard will not facilitate improvements and hereby will not increase performance. It is therefore paramount that the [http://wiki.doing-projects.org/index.php/Management_of_Project_Change change management] within the execute and control phase of the project is developed, and that the role of the dashboard is clearly established.

	::Another key aspect of preparing the dashboard for use is to ensure support and engagement across all levels of the project organization. Stakeholder management and engagement is a key part of this step. Since this article will not go into depth regarding this topic, it is recommended that the project manager revises and adopts appropriate methods from [http://wiki.doing-projects.org/index.php/Stakeholder_Management stakeholder management] theory.		::Another key aspect of preparing the dashboard for use is to ensure support and engagement across all levels of the project organization. Stakeholder management and engagement is a key part of this step. Since this article will not go into depth regarding this topic, it is recommended that the project manager revises and adopts appropriate methods from [http://wiki.doing-projects.org/index.php/Stakeholder_Management stakeholder management] theory.

Tummasm: /* Annotated Bibliography */

2021-03-03T12:38:16Z

Annotated Bibliography

← Older revision		Revision as of 12:38, 3 March 2021
Line 263:		Line 263:

	''' American National Standard, ANSI/PMI 99-001-2004, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd Edition'''		''' American National Standard, ANSI/PMI 99-001-2004, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd Edition'''
	This book desribes a standardized method to project management. It is recommended that project managers use this book to understand the monitoring and control processes and their context within the project work. This is an important foundation to understand how dashboards can properly be integrated into these. ~~One important thing to mentione, is that the~~ same applies for other project management frameworks, e.g. PRINCE2.		This book desribes a standardized method to project management. It is recommended that project managers use this book to understand the monitoring and control processes and their context within the project work. This is an important foundation to understand how dashboards can properly be integrated into these. The same applies for other project management frameworks, e.g. PRINCE2.

	==References==		==References==
	<references />		<references />

Tummasm: /* Annotated Bibliography */

2021-03-03T12:37:32Z

Annotated Bibliography

← Older revision		Revision as of 12:37, 3 March 2021
Line 263:		Line 263:

	''' American National Standard, ANSI/PMI 99-001-2004, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd Edition'''		''' American National Standard, ANSI/PMI 99-001-2004, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd Edition'''
	This book desribes a standardized method to project management. It is recommended that project managers use this book to understand the monitoring and control processes and their context within the project work. This is an important foundation to understand how dashboards can properly be integrated into these.		This book desribes a standardized method to project management. It is recommended that project managers use this book to understand the monitoring and control processes and their context within the project work. This is an important foundation to understand how dashboards can properly be integrated into these. One important thing to mentione, is that the same applies for other project management frameworks, e.g. PRINCE2.

	==References==		==References==
	<references />		<references />

Tummasm: /* Implementing Project Dashboards */

2021-03-02T15:08:51Z

Implementing Project Dashboards

← Older revision		Revision as of 15:08, 2 March 2021
Line 130:		Line 130:
	== Implementing Project Dashboards ==		== Implementing Project Dashboards ==

	===Implementation Process of Project Dashboards===		===Implementation Process for Project Dashboards===

	The idea of dashboards sounds simple enough but it is actually a quite challenging to implementing them successfully. It is key that systematic approach is employed when planning and implementing project dashboards. Initially, there are two main points that need to be addressed: '''(1) the target audience for the dashboard''' and '''(2) the type of dashboard to be used'''<ref>Harold, Kerzner, Project Management Metrics, KPIs, and Dashboards, 2001, Wiley & Sons</ref>. It is very important that these points are addressed properly beforehand since they influence every ensuing implementation step. Having addressed these, the implementation process can proceed by following the five steps:		The idea of dashboards sounds simple enough but it is actually a quite challenging to implementing them successfully. It is key that systematic approach is employed when planning and implementing project dashboards. Initially, there are two main points that need to be addressed: '''(1) the target audience for the dashboard''' and '''(2) the type of dashboard to be used'''<ref>Harold, Kerzner, Project Management Metrics, KPIs, and Dashboards, 2001, Wiley & Sons</ref>. It is very important that these points are addressed properly beforehand since they influence every ensuing implementation step. Having addressed these, the implementation process can proceed by following the five steps:

Tummasm: /* The Pitfalls of Project Dashboards */

2021-03-02T14:50:28Z

The Pitfalls of Project Dashboards

← Older revision		Revision as of 14:50, 2 March 2021
Line 246:		Line 246:

	:*'''Lack of focus:''' with the vast opportunities at hand, it is easy to go overboard and lose focus when implementing project dashboards. This will result in unfocused and convoluted dashboards that do not properly communicate key insights at a glance. Furthermore,		:*'''Lack of focus:''' with the vast opportunities at hand, it is easy to go overboard and lose focus when implementing project dashboards. This will result in unfocused and convoluted dashboards that do not properly communicate key insights at a glance. Furthermore,

	:*'''Lack of relevancy:''' a dashboard can be perfectly designed and implemented but if it does not relate to the real problem it is trying to solve, the efforts ultimately become futile. This can often happen over time as the context changes – hence making the dashboard less relevant. Furthermore, project dashboards often suffer the fate of not being properly aligned with the strategy.

	:*'''Lack of relevancy:''' a dashboard can be perfectly designed and implemented but if it does not relate to the real problem it is trying to solve, the efforts ultimately become futile. This can often happen over time as the context changes – hence making the dashboard less relevant. Furthermore, project dashboards often suffer the fate of not being properly aligned with the strategy.		:*'''Lack of relevancy:''' a dashboard can be perfectly designed and implemented but if it does not relate to the real problem it is trying to solve, the efforts ultimately become futile. This can often happen over time as the context changes – hence making the dashboard less relevant. Furthermore, project dashboards often suffer the fate of not being properly aligned with the strategy.

Tummasm: /* What are Dashboards? */

2021-02-28T22:07:31Z

What are Dashboards?

← Older revision		Revision as of 22:07, 28 February 2021
Line 35:		Line 35:
	:*'''Dashboards are used to monitor information at a glance'''		:*'''Dashboards are used to monitor information at a glance'''

	::A significant feature of a dashboard is that it should convey critical information at a glance. Therefore, the information it displays needs to be specific, clear, and concise. A dashboard should only display information that is key in achieving the objectives, which often can be measured quantitatively in the form of KPIs ~~(reference)~~. The information displayed on a dashboard is therefore often a set of KPIs. Since more specific details related to the KPIs cannot be monitored at a glance, they should not be included in a dashboard – it is very important to keep this distinction clear.		::A significant feature of a dashboard is that it should convey critical information at a glance. Therefore, the information it displays needs to be specific, clear, and concise. A dashboard should only display information that is key in achieving the objectives, which often can be measured quantitatively in the form of KPIs. The information displayed on a dashboard is therefore often a set of KPIs. Since more specific details related to the KPIs cannot be monitored at a glance, they should not be included in a dashboard – it is very important to keep this distinction clear.

	Overall, a dashboard gathers key information on the progression of achieving the objectives that it monitors. It often does this by monitoring a set of KPIs, hereby communicating the most important aspects that contribute to the achieving of the objectives. By monitoring these KPIs, a dashboard highlights any worrying trends that are occurring, and thus enables the users to address the related issues immediately.		Overall, a dashboard gathers key information on the progression of achieving the objectives that it monitors. It often does this by monitoring a set of KPIs, hereby communicating the most important aspects that contribute to the achieving of the objectives. By monitoring these KPIs, a dashboard highlights any worrying trends that are occurring, and thus enables the users to address the related issues immediately.

Tummasm: /* Implementation Process of Project Dashboards */

2021-02-28T22:06:49Z

Implementation Process of Project Dashboards

← Older revision		Revision as of 22:06, 28 February 2021
Line 213:		Line 213:
	::Dashboard design might seem simple but there is actually more to it than one might think. Very often, the effectiveness of dashboards is significantly diminished by poor dashboard design. The following list will outline some of the main best-practice considerations to keep in mind when designing dashboards<ref>Stephen, Few, Information Dashboard Design, 2006, O'Reilly</ref>:		::Dashboard design might seem simple but there is actually more to it than one might think. Very often, the effectiveness of dashboards is significantly diminished by poor dashboard design. The following list will outline some of the main best-practice considerations to keep in mind when designing dashboards<ref>Stephen, Few, Information Dashboard Design, 2006, O'Reilly</ref>:

	[[File: Well designed dashboard.PNG \|600px\|thumb\|right\|top\|Figure 5: Example of good dashboard design. Based on ...]]		[[File: Well designed dashboard.PNG \|600px\|thumb\|right\|top\|Figure 5: Example of good dashboard design. Based on visuals from Stephen Few, Information Dashboard Design, 2006, O'Reilly.]]

	:::*'''Organize data in groups:''' It is very important to keep data organized into sensible groups, based on for example functions, process, or knowledge area. The organizing of the data should be based on how the dashboard will be used in order to best serve this use case.		:::*'''Organize data in groups:''' It is very important to keep data organized into sensible groups, based on for example functions, process, or knowledge area. The organizing of the data should be based on how the dashboard will be used in order to best serve this use case.

Tummasm: /* Annotated Bibliography */

2021-02-28T22:04:57Z

Annotated Bibliography

← Older revision		Revision as of 22:04, 28 February 2021
Line 264:		Line 264:
	This book describes best-practices regarding designing proper dashboards. It is quite technical but can still be useful to a project manager who wishes to understamd what makes a project dashboard work and what does not.		This book describes best-practices regarding designing proper dashboards. It is quite technical but can still be useful to a project manager who wishes to understamd what makes a project dashboard work and what does not.

	'''~~2010 R. Meredith Belbin.~~, Management ~~Teams: Why They Succeed or Fail - Third~~ Edition~~, Taylor & Francis Ltd~~'''		''' American National Standard, ANSI/PMI 99-001-2004, A Guide to the Project Management Body of Knowledge (PMBOK Guide), 3rd Edition'''
	This book~~, written by Dr. Belbin himself, offers~~ a ~~comprehensive description of the Team Roles, their origin and background~~. It ~~further describes~~ the ~~consideration a manager should do before constructing a team~~ and ~~which benefits could~~ be ~~obtained by utilizing the different roles~~.		This book desribes a standardized method to project management. It is recommended that project managers use this book to understand the monitoring and control processes and their context within the project work. This is an important foundation to understand how dashboards can properly be integrated into these.

	==References==		==References==
	<references />		<references />

Tummasm: /* The Pitfalls of Project Dashboards */

2021-02-28T22:01:30Z

The Pitfalls of Project Dashboards

← Older revision		Revision as of 22:01, 28 February 2021
Line 250:		Line 250:

	:*'''Lack of relevancy:''' a dashboard can be perfectly designed and implemented but if it does not relate to the real problem it is trying to solve, the efforts ultimately become futile. This can often happen over time as the context changes – hence making the dashboard less relevant. Furthermore, project dashboards often suffer the fate of not being properly aligned with the strategy.		:*'''Lack of relevancy:''' a dashboard can be perfectly designed and implemented but if it does not relate to the real problem it is trying to solve, the efforts ultimately become futile. This can often happen over time as the context changes – hence making the dashboard less relevant. Furthermore, project dashboards often suffer the fate of not being properly aligned with the strategy.


	Following the implementation process described in section 3.1 will significantly reduce the chance of falling victim to these pitfalls.		Following the implementation process described in section 3.1 will significantly reduce the chance of falling victim to these pitfalls.

Tummasm: /* The Pitfalls of Project Dashboards */

2021-02-28T22:01:17Z

The Pitfalls of Project Dashboards

← Older revision		Revision as of 22:01, 28 February 2021
Line 239:		Line 239:
	===The Pitfalls of Project Dashboards===		===The Pitfalls of Project Dashboards===

	Project dashboards can be highly useful tool within project management when implemented correctly, but in order to do so one needs to be aware of some of the common pitfalls related to using project dashboard. The main ones are outlined below (Project Management Metrics, KPIs, and Dashboards):		Project dashboards can be highly useful tool within project management when implemented correctly, but in order to do so one needs to be aware of some of the common pitfalls related to using project dashboard. The main ones are outlined below<ref>Harold, Kerzner, Project Management Metrics, KPIs, and Dashboards, 2001, Wiley & Sons</ref>:

	:*'''Garbage in – garbage out:''' a dashboard and the insights it provides can only ever be as good as the input data it is provided. Often, suboptimal data collection, preparation, and quality results in unreliable dashboards that cannot serve their purpose properly.		:*'''Garbage in – garbage out:''' a dashboard and the insights it provides can only ever be as good as the input data it is provided. Often, suboptimal data collection, preparation, and quality results in unreliable dashboards that cannot serve their purpose properly.