Sankey Diagram
| Line 30: | Line 30: | ||
As many companies have transitioned from a traditional Waterfall methodology where actions are dependent on other actions to an Agile methodology where actions can be done in parallel, a new terminology like Epics and User Stories have been introduced <ref>"[https://www.atlassian.com/agile/project-management/epics-stories-themes#:~:text=Stories%2C%20also%20called%20%E2%80%9Cuser%20stories,drive%20toward%20a%20common%20goal.]", Rehkopf, M. (2022). Stories, epics, and initiatives. 20 February 2022</ref>: | As many companies have transitioned from a traditional Waterfall methodology where actions are dependent on other actions to an Agile methodology where actions can be done in parallel, a new terminology like Epics and User Stories have been introduced <ref>"[https://www.atlassian.com/agile/project-management/epics-stories-themes#:~:text=Stories%2C%20also%20called%20%E2%80%9Cuser%20stories,drive%20toward%20a%20common%20goal.]", Rehkopf, M. (2022). Stories, epics, and initiatives. 20 February 2022</ref>: | ||
| − | *'''Stories''', "also called "User Stories," are short requirements or requests written from the perspective of an end user." | + | *'''Stories''', "also called "User Stories," are short requirements or requests written from the perspective of an end-user." |
*'''Epics''', "are large bodies of work that can be broken down into a number of smaller tasks (called stories)." | *'''Epics''', "are large bodies of work that can be broken down into a number of smaller tasks (called stories)." | ||
*'''Milestones''', "are collections of epics that drive toward a common goal." | *'''Milestones''', "are collections of epics that drive toward a common goal." | ||
| Line 36: | Line 36: | ||
| − | In a Technology Portfolio, the head of the portfolio must be able to assess the status of all projects within the portfolio at any given time. This means that all activities must be accounted for and must align with at least one of the milestones of the portfolio. Tasks that do not align with a milestone do not add value and therefore are considered a waste of resources. At the same time, a Portfolio Manager can compare the planned vs actual resource allocation as well as in what direction each Scrum Team is benefiting the bottom line of the portfolio. In the technology example, each Scrum Team works in individual User Stories, | + | In a Technology Portfolio, the head of the portfolio must be able to assess the status of all projects within the portfolio at any given time. This means that all activities must be accounted for and must align with at least one of the milestones of the portfolio. Tasks that do not align with a milestone do not add value and therefore are considered a waste of resources. At the same time, a Portfolio Manager can compare the planned vs actual resource allocation as well as in what direction each Scrum Team is benefiting the bottom line of the portfolio. In the technology example, each Scrum Team works in individual User Stories, and the combination of the User Stories makes up an Epic. Meaning that even though each team works separately at the User Stories level they might be working together at an Epic level. From a manager's point of view, the diagram can raise red flags visually when User Stories or Epics are not getting the attention needed from the Scrum Teams. This red flag can create an alert for management that more resources are needed in a specific area. These resources could be the need for more Scrum Teams as the workload demands more people or that guidance from upper management is needed to steer the team towards the right direction. In many cases, as portfolios are so big and made up of many platforms with their own subdivisions, a clear view of what the portfolio is collectively working toward is unclear. A Sankey Diagram can serve as an overview dashboard for Portfolio Managers to quickly assess the status of the Portfolio and be able to make decisions for the future quarters. These decisions can be in increasing the workload as the teams can produce more, forecasting the number of people that need to be hired to meet deadlines, and refocusing on the milestones with the highest priority for the quarter. |
Revision as of 18:49, 20 February 2022
By Sonia Guerra Loji (s203379)
The article's aim is to highlight the usefulness of the Sankey diagram in a project & portfolio management context. The article includes a discussion of the diagram's pros and cons from the Managements perspective.
Contents |
Abstract
Within project & portfolio management it has become even more important that leadership is able to visualize where resources are being allocated and used. This is in terms of simple supervision over the projects, but also to optimize the limited resources an organization has. The Sankey diagrams are a graphical way of visualizing the flow of resources in a team, project, process, company, etc. Resources mapped in a Sankey diagram can be anything from materials, monetary funds, people allocation, activities, etc.
Beginning in 1898, the Sankey diagram was first used by an Irish captain named Matthew Henry Phineas Riall Sankey. This first implementation of the diagram showed the energy efficiency of a steam engine. [2] Nowadays there are four main implementations of the Sankey diagram. First, to analyze flow, flow being whatever has movement (like resources) in the scope defined by the diagram. Second, to analyze time-based patterns, this type can visualize the behavioral change of a specific persona, group, thing, over a specific time-lapse. Third, to analyze hierarchy type data, this is used when there are connected relations between the data but a hierarchy between the data has been defined. This hierarchy defines the order in which the data will be split and mapped in the diagram. And finally, the "quick trick" to replace Machine-learning, the Sankey diagram can be used to find and understand patterns in the data instead of using machine learning. [3] All four applications of the Sankey diagram can produce valuable insights to data in a visual and straightforward way to understand.
Correct application and automation of the Sankey diagram can provide fast and easy access to complicated data. The purpose of the article is to dive further into the possible applications and key characteristics of the Sankey diagram, as well as the benefits and limitations it can bring to upper management when making decisions in terms of resources and strategy.
Elements of the diagram
As mentioned previously the resources can be anything from money, human labor, materials, etc. The system as a whole can represent the flow of a process like a steam engine to the circulation of a global economy. For this reason, it is important to identify the origin points (where the system begins) and the endpoints (where the system ends). In the case of the example diagram, the origin points are nodes A and B, while the endpoints are nodes R, S, and T. In general terms the system flow should be read from left to right, and therefore when mapping the system's nodes the origin points should be towards the left extreme and the endpoints towards the right extreme. The Sankey Diagram can also show the equality or inequality between the inputs and outputs of the nodes. In the example diagram, it can be seen that node Z receives and gives the same flow, but nodes X and Y have a higher input than output. These visualizations of types of inequalities can help decision-makers notice areas of improvement faster. Depending on the program and style used to create the visualization, features like the color of the flow waves can be changed to resemble the color of the node it is originating from. Other more advanced features can be added to the code to create a more self-explanatory diagram, for the purpose of this article only the basic features are mentioned.
Types of Application
Example in Portfolio Management
As many companies have transitioned from a traditional Waterfall methodology where actions are dependent on other actions to an Agile methodology where actions can be done in parallel, a new terminology like Epics and User Stories have been introduced [4]:
- Stories, "also called "User Stories," are short requirements or requests written from the perspective of an end-user."
- Epics, "are large bodies of work that can be broken down into a number of smaller tasks (called stories)."
- Milestones, "are collections of epics that drive toward a common goal."
In a Technology Portfolio, Scrum Teams are formed to tackle the Stories and Epics. A Scrum Team is "typically between five to nine individuals, who work toward completing projects and delivering products. The fundamental scrum team comprises one Scrum Master, one Product Owner, and a group of developers."[5].
In a Technology Portfolio, the head of the portfolio must be able to assess the status of all projects within the portfolio at any given time. This means that all activities must be accounted for and must align with at least one of the milestones of the portfolio. Tasks that do not align with a milestone do not add value and therefore are considered a waste of resources. At the same time, a Portfolio Manager can compare the planned vs actual resource allocation as well as in what direction each Scrum Team is benefiting the bottom line of the portfolio. In the technology example, each Scrum Team works in individual User Stories, and the combination of the User Stories makes up an Epic. Meaning that even though each team works separately at the User Stories level they might be working together at an Epic level. From a manager's point of view, the diagram can raise red flags visually when User Stories or Epics are not getting the attention needed from the Scrum Teams. This red flag can create an alert for management that more resources are needed in a specific area. These resources could be the need for more Scrum Teams as the workload demands more people or that guidance from upper management is needed to steer the team towards the right direction. In many cases, as portfolios are so big and made up of many platforms with their own subdivisions, a clear view of what the portfolio is collectively working toward is unclear. A Sankey Diagram can serve as an overview dashboard for Portfolio Managers to quickly assess the status of the Portfolio and be able to make decisions for the future quarters. These decisions can be in increasing the workload as the teams can produce more, forecasting the number of people that need to be hired to meet deadlines, and refocusing on the milestones with the highest priority for the quarter.
Using Sankey diagram to map what resources (people/teams) are working in which user stories, how those user stories go into an Epic and how the epic is directed into a Milestone for the portfolio. If that complete link is not done that the resource should not be conducting the action.
Programing
References
- ↑ "[1]", Kennedy, A. B. W.; Sankey, H. R. (1898). The Thermal Efficiency of Steam Engines. 12 February 2022
- ↑ "[2]", Kennedy, A. B. W.; Sankey, H. R. (1898). The Thermal Efficiency of Steam Engines. 12 February 2022
- ↑ "[3]", Dave P. (2020). 4 use-cases for Sankey Charts. 13 February 2022.
- ↑ "[4]", Rehkopf, M. (2022). Stories, epics, and initiatives. 20 February 2022
- ↑ "[5]", Indeed Editorial Team. (2021). A Guide to Scrum Teams. 20 February 2022
- ↑ "[6]", Google Charts. Sankey Diagram. 20 February 2022
