Kanban - Revision history

S200120 at 15:23, 27 February 2021

2021-02-27T15:23:06Z

← Older revision		Revision as of 15:23, 27 February 2021
Line 2:		Line 2:

	Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>		Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>



	== '''Big Idea''' ==		== '''Big Idea''' ==
Line 33:		Line 35:
	==== '''Work In Progress (WiP)''' ====		==== '''Work In Progress (WiP)''' ====
	The <span class="plainlinks">[https://en.wikipedia.org/wiki/Work_in_process'''Work in Progress (WiP)''']</span> limit is added to the board to limits the number of simultaneous tasks allowed in the same category. In Figure 2 the board shows the current number of cards and the WiP limit in gray colored numbers for each category. Categories like the ''Ideas'' or ''Done'' do not need a set WiP limit, as the purpose of these categories is sorely to collect the cards. An argument behind the WIP limit is that scientific studies have shown that multitasking heavily decreases productivity and cognitive ability. <ref name=kanbanzone> Kanbanzone. (2021). Why Multitasking Doesn’t Work – And How Kanban Can Help. [https://kanbanzone.com/2017/multitasking-doesnt-work-kanban-can-help/ Available Online]</ref> By setting a WIP limit, fewer work tasks can be processed at the same time, encouraging team members to complete tasks before starting a new one. Setting a WiP limit helps as it results in an overall decrease of lead time for the work tasks, establishing more agile task management. The WIP limits for each category should be defined for each project individually, as the number depends on the type of organization the system is used, the number of people working on a task together and the size and duration an average task takes to complete in the Kanban system.<ref name=kanbanmetrics> Kanban Metrics. (2021). What to Measure and Why: Kanban Metrics. [https://getnave.com/blog/kanban-metrics/ Available Online]</ref>		The <span class="plainlinks">[https://en.wikipedia.org/wiki/Work_in_process'''Work in Progress (WiP)''']</span> limit is added to the board to limits the number of simultaneous tasks allowed in the same category. In Figure 2 the board shows the current number of cards and the WiP limit in gray colored numbers for each category. Categories like the ''Ideas'' or ''Done'' do not need a set WiP limit, as the purpose of these categories is sorely to collect the cards. An argument behind the WIP limit is that scientific studies have shown that multitasking heavily decreases productivity and cognitive ability. <ref name=kanbanzone> Kanbanzone. (2021). Why Multitasking Doesn’t Work – And How Kanban Can Help. [https://kanbanzone.com/2017/multitasking-doesnt-work-kanban-can-help/ Available Online]</ref> By setting a WIP limit, fewer work tasks can be processed at the same time, encouraging team members to complete tasks before starting a new one. Setting a WiP limit helps as it results in an overall decrease of lead time for the work tasks, establishing more agile task management. The WIP limits for each category should be defined for each project individually, as the number depends on the type of organization the system is used, the number of people working on a task together and the size and duration an average task takes to complete in the Kanban system.<ref name=kanbanmetrics> Kanban Metrics. (2021). What to Measure and Why: Kanban Metrics. [https://getnave.com/blog/kanban-metrics/ Available Online]</ref>




	==== '''Lead Time''' ====		==== '''Lead Time''' ====
Line 148:		Line 147:

	'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.		'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.

S200120 at 15:20, 27 February 2021

2021-02-27T15:20:55Z

← Older revision		Revision as of 15:20, 27 February 2021
Line 2:		Line 2:

	Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>		Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>






	== '''Big Idea''' ==		== '''Big Idea''' ==

S200120 at 15:16, 27 February 2021

2021-02-27T15:16:46Z

← Older revision		Revision as of 15:16, 27 February 2021
Line 38:		Line 38:
	==== '''Work In Progress (WiP)''' ====		==== '''Work In Progress (WiP)''' ====
	The <span class="plainlinks">[https://en.wikipedia.org/wiki/Work_in_process'''Work in Progress (WiP)''']</span> limit is added to the board to limits the number of simultaneous tasks allowed in the same category. In Figure 2 the board shows the current number of cards and the WiP limit in gray colored numbers for each category. Categories like the ''Ideas'' or ''Done'' do not need a set WiP limit, as the purpose of these categories is sorely to collect the cards. An argument behind the WIP limit is that scientific studies have shown that multitasking heavily decreases productivity and cognitive ability. <ref name=kanbanzone> Kanbanzone. (2021). Why Multitasking Doesn’t Work – And How Kanban Can Help. [https://kanbanzone.com/2017/multitasking-doesnt-work-kanban-can-help/ Available Online]</ref> By setting a WIP limit, fewer work tasks can be processed at the same time, encouraging team members to complete tasks before starting a new one. Setting a WiP limit helps as it results in an overall decrease of lead time for the work tasks, establishing more agile task management. The WIP limits for each category should be defined for each project individually, as the number depends on the type of organization the system is used, the number of people working on a task together and the size and duration an average task takes to complete in the Kanban system.<ref name=kanbanmetrics> Kanban Metrics. (2021). What to Measure and Why: Kanban Metrics. [https://getnave.com/blog/kanban-metrics/ Available Online]</ref>		The <span class="plainlinks">[https://en.wikipedia.org/wiki/Work_in_process'''Work in Progress (WiP)''']</span> limit is added to the board to limits the number of simultaneous tasks allowed in the same category. In Figure 2 the board shows the current number of cards and the WiP limit in gray colored numbers for each category. Categories like the ''Ideas'' or ''Done'' do not need a set WiP limit, as the purpose of these categories is sorely to collect the cards. An argument behind the WIP limit is that scientific studies have shown that multitasking heavily decreases productivity and cognitive ability. <ref name=kanbanzone> Kanbanzone. (2021). Why Multitasking Doesn’t Work – And How Kanban Can Help. [https://kanbanzone.com/2017/multitasking-doesnt-work-kanban-can-help/ Available Online]</ref> By setting a WIP limit, fewer work tasks can be processed at the same time, encouraging team members to complete tasks before starting a new one. Setting a WiP limit helps as it results in an overall decrease of lead time for the work tasks, establishing more agile task management. The WIP limits for each category should be defined for each project individually, as the number depends on the type of organization the system is used, the number of people working on a task together and the size and duration an average task takes to complete in the Kanban system.<ref name=kanbanmetrics> Kanban Metrics. (2021). What to Measure and Why: Kanban Metrics. [https://getnave.com/blog/kanban-metrics/ Available Online]</ref>




	==== '''Lead Time''' ====		==== '''Lead Time''' ====
Line 150:		Line 153:

	'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.		'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.

S200120 at 15:16, 27 February 2021

2021-02-27T15:16:05Z

← Older revision		Revision as of 15:16, 27 February 2021
Line 2:		Line 2:

	Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>		Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>

S200120 at 15:15, 27 February 2021

2021-02-27T15:15:21Z

← Older revision		Revision as of 15:15, 27 February 2021
Line 2:		Line 2:

	Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>		Kanban has its origin in the late 1940s when Toyota decided to put its efforts in the development of a production control system with the goal of shortening the time required from the start to the completion of a process. The Kanban system is a sign-based scheduling system that helped Toyota to improve production efficiency and eliminate waste, establishing the <span class="plainlinks">[https://en.wikipedia.org/wiki/Just-in-time_manufacturing'''JIT (just-in-time)''']</span> manufacturing system that is a central philosophy of <span class="plainlinks">[https://en.wikipedia.org/wiki/Lean_thinking'''Lean Thinking''']</span>. In recent years the concept of Kanban got widely adopted especially as a project management tool for software development, but it can be applied to just about any industry, either process, production or service-related.<ref name=swkanban> Dos Santos, Paulo Sérgio & Beltrão, Alessandro & Pedraça de Souza, Bruno & Travassos, Guilherme (2018). <i> On the benefits and challenges of using kanban in software engineering: a structured synthesis study </i>. Journal of Software Engineering Research and Development. 6. 10.1186/s40411-018-0057-1. </ref>



Line 147:		Line 148:

	'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.		'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.



	== '''References''' ==		== '''References''' ==

S200120: /* Kanban vs Scrum */

2021-02-27T15:09:39Z

Kanban vs Scrum

← Older revision		Revision as of 15:09, 27 February 2021
Line 117:		Line 117:

	*Kanban systems are limited in size and volume, as working on the same board is not suitable for larger size teams or projects. Scrum on the other hand allows dividing large projects into simpler and manageable sprints.		*Kanban systems are limited in size and volume, as working on the same board is not suitable for larger size teams or projects. Scrum on the other hand allows dividing large projects into simpler and manageable sprints.
			<ref name=atlassian> Atlassian. Kanban vs Scrum - Atlassian. [https://www.atlassian.com/agile/kanban/kanban-vs-scrum Available Online]</ref>

	==== '''Scrumban - Combining Kanban and Scrum''' ====		==== '''Scrumban - Combining Kanban and Scrum''' ====

S200120: /* Getting Started with Kanban */

2021-02-27T15:08:31Z

Getting Started with Kanban

← Older revision		Revision as of 15:08, 27 February 2021
Line 135:		Line 135:
	#'''Improve Collaboratively:''' The concept of continuous improvement and constant learning is a core strategy making the Kanban system a powerful tool in collaborative work. As everyone inside the team has access to the same amount of information about the work process, it becomes much easier for everyone in the team to address and implement improvements.		#'''Improve Collaboratively:''' The concept of continuous improvement and constant learning is a core strategy making the Kanban system a powerful tool in collaborative work. As everyone inside the team has access to the same amount of information about the work process, it becomes much easier for everyone in the team to address and implement improvements.

			<ref name=Kaltenecker2015> Klaus Leopold, Siegfried Kaltenecker (2015). <i> Kanban Change Leadership – Creating a Culture of continuous Improvements</i>. John Wiley & Sohns </ref>

	=== '''Kanban Software''' ===		=== '''Kanban Software''' ===

S200120: /* Workflow Visualization with Cumulative Flow Diagrams (CFD) */

2021-02-27T15:08:00Z

Workflow Visualization with Cumulative Flow Diagrams (CFD)

← Older revision		Revision as of 15:08, 27 February 2021
Line 56:		Line 56:


	Common patterns that can be observed when using CFD as visualization tools for the Kanban: ~~<ref name=kanbanzonecfd> KanbanzoneCFD. (2021). Cumulative Flow Diagram: Your Most Powerful Tool to Create a More Stable & Predictable Flow.~~		Common patterns that can be observed when using CFD as visualization tools for the Kanban:

	*'''Curves Narrow Together:''' No or little space between the lines indicates that the team is not fully utilized, and the available resources exceed the workload		*'''Curves Narrow Together:''' No or little space between the lines indicates that the team is not fully utilized, and the available resources exceed the workload
Line 64:		Line 64:
	*'''Done Curve is a Forecast:''' The done curve can be used as an estimated forecast, indicating when all tasks could be finished if the team can keep up the same speed of delivering tasks		*'''Done Curve is a Forecast:''' The done curve can be used as an estimated forecast, indicating when all tasks could be finished if the team can keep up the same speed of delivering tasks

	[https://kanbanzone.com/2019/power-of-cumulative-flow-diagram/ Available Online]</ref>		<ref name=kanbanzonecfd> KanbanzoneCFD. (2021). Cumulative Flow Diagram: Your Most Powerful Tool to Create a More Stable & Predictable Flow. [https://kanbanzone.com/2019/power-of-cumulative-flow-diagram/ Available Online]</ref>

	Further information about the possible shapes of CFD curves and what the curve implicitly tell about the workflow and processes inside the project team can be found on the project management platform <span class="plainlinks">[https://getnave.com/blog/kanban-cfd-patterns/'''Getnave''']</span>.		Further information about the possible shapes of CFD curves and what the curve implicitly tell about the workflow and processes inside the project team can be found on the project management platform <span class="plainlinks">[https://getnave.com/blog/kanban-cfd-patterns/'''Getnave''']</span>.

S200120: /* Workflow Visualization with Cumulative Flow Diagrams (CFD) */

2021-02-27T15:07:08Z

Workflow Visualization with Cumulative Flow Diagrams (CFD)

← Older revision		Revision as of 15:07, 27 February 2021
Line 56:		Line 56:


	Common patterns that can be observed when using CFD as visualization tools for the Kanban: <ref name=kanbanzonecfd> KanbanzoneCFD. (2021). Cumulative Flow Diagram: Your Most Powerful Tool to Create a More Stable & Predictable Flow. ~~[https://kanbanzone.com/2019/power-of-cumulative-flow-diagram/ Available Online]</ref>~~		Common patterns that can be observed when using CFD as visualization tools for the Kanban: <ref name=kanbanzonecfd> KanbanzoneCFD. (2021). Cumulative Flow Diagram: Your Most Powerful Tool to Create a More Stable & Predictable Flow.

	*'''Curves Narrow Together:''' No or little space between the lines indicates that the team is not fully utilized, and the available resources exceed the workload		*'''Curves Narrow Together:''' No or little space between the lines indicates that the team is not fully utilized, and the available resources exceed the workload
Line 64:		Line 64:
	*'''Done Curve is a Forecast:''' The done curve can be used as an estimated forecast, indicating when all tasks could be finished if the team can keep up the same speed of delivering tasks		*'''Done Curve is a Forecast:''' The done curve can be used as an estimated forecast, indicating when all tasks could be finished if the team can keep up the same speed of delivering tasks

			[https://kanbanzone.com/2019/power-of-cumulative-flow-diagram/ Available Online]</ref>

	Further information about the possible shapes of CFD curves and what the curve implicitly tell about the workflow and processes inside the project team can be found on the project management platform <span class="plainlinks">[https://getnave.com/blog/kanban-cfd-patterns/'''Getnave''']</span>.		Further information about the possible shapes of CFD curves and what the curve implicitly tell about the workflow and processes inside the project team can be found on the project management platform <span class="plainlinks">[https://getnave.com/blog/kanban-cfd-patterns/'''Getnave''']</span>.

S200120: /* Kanban Software */

2021-02-27T15:02:22Z

Kanban Software

← Older revision		Revision as of 15:02, 27 February 2021
Line 137:		Line 137:
	=== '''Kanban Software''' ===		=== '''Kanban Software''' ===

	In the past years digital software tools became increasingly more popular to realize Kanban ~~system~~ even for remote operating teams. The virtual Kanban systems are all powerful tools, as they offer a wide range of customizable features to tailor the board's layout to the project. The measurement and visualization of real-time data of the metrics make digital boards to a great asset for collaborative task planning and execution. The following listed software tools are all established platforms that can be used to manage, and control process flows with the Kanban board and should provide interested readers with software tools on how to get started with setting up a Kanban system. <ref name=Kaltenecker2015> Klaus Leopold, Siegfried Kaltenecker (2015). <i> Kanban Change Leadership – Creating a Culture of continuous Improvements</i>. John Wiley & Sohns </ref>		In the past years, digital software tools became increasingly more popular to realize Kanban systems even for remote operating teams. The virtual Kanban systems are all powerful tools, as they offer a wide range of customizable features to tailor the board's layout to the project. The measurement and visualization of real-time data of the metrics make digital boards a great asset for collaborative task planning and execution. The following listed software tools are all established platforms that can be used to manage, and control process flows with the Kanban board and should provide interested readers with software tools on how to get started with setting up a Kanban system. <ref name=Kaltenecker2015> Klaus Leopold, Siegfried Kaltenecker (2015). <i> Kanban Change Leadership – Creating a Culture of continuous Improvements</i>. John Wiley & Sohns </ref>

	'''<span class="plainlinks">[https://trello.com/'''Trello''']</span>''' Is an intuitive and easy to get started with task management Kanban system that is widely used for various small to medium size applications, ranging from software development to personal Kanban boards. The tool offers a great range of power-ups that can help collaborative teams to automate the processes in their project management Kanban system.		'''<span class="plainlinks">[https://trello.com/'''Trello''']</span>''' Is an intuitive and easy to get started with task management Kanban system that is widely used for various small to medium size applications, ranging from software development to personal Kanban boards. The tool offers a great range of power-ups that can help collaborative teams to automate the processes in their project management Kanban system.

	'''<span class="plainlinks">[https://kanbanize.com/'''Kanbanize''']</span>''' The tool Kanbanize offers great additional functionalities that add value when managing tasks and employees in medium to large scale projects. Features like visualizing the project plan, creating Gantt charts and various forecasting tools make Kanbanize to a valuable asset when managing projects or portfolios.		'''<span class="plainlinks">[https://kanbanize.com/'''Kanbanize''']</span>''' The tool Kanbanize offers great additional functionalities that add value when managing tasks and employees in medium to large-scale projects. Features like visualizing the project plan, creating Gantt charts and various forecasting tools make Kanbanize a valuable asset when managing projects or portfolios.

	'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.		'''<span class="plainlinks">[https://www.atlassian.com/software/jira'''JIRA''']</span>''' Is a very popular project management tool that is widely used to manage complex and larger-scale projects, mainly within the field of software development. The key benefits that Jira can offer on top of the other tools are advanced functionalities to track and visualize performance metrics, like the previously mentioned CFD.

	== '''References''' ==		== '''References''' ==