Kanban: a project management framework - Revision history

Guilleroigp at 21:55, 27 March 2022

2022-03-27T21:55:20Z

← Older revision		Revision as of 21:55, 27 March 2022
Line 1:		Line 1:
			''Made by Guillermo Roig Pitarch (s212754)''

	Over the last decades important new approaches have appeared in operations planning and control of production systems.<ref name="Bouch">R.J. Boucherie, X. Chao and M. Miyazawa. (2001). "Arrival first queueing networks with applications in kanban production systems".</ref> Kanban (看板, meaning ''‘signboard’'' in Japanese)<ref name="KANBANTOOL">Kanban tool, History of Kanban. Last visited 3rd of March 2022, https://kanbantool.com/es/guia-kanban/historia-de-kanban</ref> is a visual system whose first purpose was to gain control in processes and make their workflow more manageable. The efficiency of daily activities within industrial processes represent a challenge for every production company. In fact, this tool is not only applicable to production processes, but also to every [[Wikipedia:project management\|'''project management''']] taking place in almost every business function (operations, marketing, recruitment, business expansion, among others).		Over the last decades important new approaches have appeared in operations planning and control of production systems.<ref name="Bouch">R.J. Boucherie, X. Chao and M. Miyazawa. (2001). "Arrival first queueing networks with applications in kanban production systems".</ref> Kanban (看板, meaning ''‘signboard’'' in Japanese)<ref name="KANBANTOOL">Kanban tool, History of Kanban. Last visited 3rd of March 2022, https://kanbantool.com/es/guia-kanban/historia-de-kanban</ref> is a visual system whose first purpose was to gain control in processes and make their workflow more manageable. The efficiency of daily activities within industrial processes represent a challenge for every production company. In fact, this tool is not only applicable to production processes, but also to every [[Wikipedia:project management\|'''project management''']] taking place in almost every business function (operations, marketing, recruitment, business expansion, among others).

Guilleroigp: /* Annotated bibliography */

2022-03-27T21:52:04Z

Annotated bibliography

← Older revision		Revision as of 21:52, 27 March 2022
Line 211:		Line 211:
	=Annotated bibliography=		=Annotated bibliography=
	There are some references suggested for a further reading regarding Kanban as a project management framework:		There are some references suggested for a further reading regarding Kanban as a project management framework:


	* Eric Brechner (2015) ''Agile Project Management with Kanban (Developer Best Practices)''		* Eric Brechner (2015) ''Agile Project Management with Kanban (Developer Best Practices)''

Guilleroigp: /* Annotated bibliography */

2022-03-27T21:51:34Z

Annotated bibliography

← Older revision		Revision as of 21:51, 27 March 2022
Line 211:		Line 211:
	=Annotated bibliography=		=Annotated bibliography=
	There are some references suggested for a further reading regarding Kanban as a project management framework:		There are some references suggested for a further reading regarding Kanban as a project management framework:


			* Eric Brechner (2015) ''Agile Project Management with Kanban (Developer Best Practices)''

			:-This is an interesting reading written by Eric Brechner, who is the development manager working for Microsoft's Xbox Engineering Services. This manager has used Kanban during years with different teams. This book offers a guide full of content which has the objective on helping the reader achieve more productive environments. It is also centered in the obtention of results, focusing in the evolution from more traditional approaches to new ones. Also, an it is explained how Kanban could experiment an integration in a large project.

			* Mashal Alqudah, Rozilawati Razali (2017) ''A comparison of scrum and Kanban for identifying their selection factors''

			:-For a better and more deep understanding of both methodologies Kanban and Scrum and to visualize in which situation is better use them, this reading could serve as a proper guide. It is focused from a software engineering perspective, and it offers all the factors that need to be considered to choose the correct methodology, depending on the results to be obtained.

	* Marko Ikonen, et al. (2011) ''On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation''		* Marko Ikonen, et al. (2011) ''On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation''
Line 219:		Line 228:

	:-This reading offers an interesting approach about how useful the Kanban methodology is, all around the 12 principles included in the Agile Manifesto. This study is done because there is not many historical data that offers a real image of how enrichful applying this methodology to projects within school project teams. The study finds that there are two key agile principles having a clear impact on the way teams work. These results can help those who want to consider applying this methodology in school projects to decide among other agile methodologies.		:-This reading offers an interesting approach about how useful the Kanban methodology is, all around the 12 principles included in the Agile Manifesto. This study is done because there is not many historical data that offers a real image of how enrichful applying this methodology to projects within school project teams. The study finds that there are two key agile principles having a clear impact on the way teams work. These results can help those who want to consider applying this methodology in school projects to decide among other agile methodologies.

	* Eric Brechner. (2015) ''Agile Project Management with Kanban (Developer Best Practices)''

	:-This is an interesting reading written by Eric Brechner, who is the development manager working for Microsoft's Xbox Engineering Services. This manager has used Kanban during years with different teams. This book offers a guide full of content which has the objective on helping the reader achieve more productive environments. It is also centered in the obtention of results, focusing in the evolution from more traditional approaches to new ones. Also, an it is explained how Kanban could experiment an integration in a large project.

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

Guilleroigp: /* Annotated bibliography */

2022-03-27T21:46:46Z

Annotated bibliography

← Older revision		Revision as of 21:46, 27 March 2022
Line 219:		Line 219:

	:-This reading offers an interesting approach about how useful the Kanban methodology is, all around the 12 principles included in the Agile Manifesto. This study is done because there is not many historical data that offers a real image of how enrichful applying this methodology to projects within school project teams. The study finds that there are two key agile principles having a clear impact on the way teams work. These results can help those who want to consider applying this methodology in school projects to decide among other agile methodologies.		:-This reading offers an interesting approach about how useful the Kanban methodology is, all around the 12 principles included in the Agile Manifesto. This study is done because there is not many historical data that offers a real image of how enrichful applying this methodology to projects within school project teams. The study finds that there are two key agile principles having a clear impact on the way teams work. These results can help those who want to consider applying this methodology in school projects to decide among other agile methodologies.

			* Eric Brechner. (2015) ''Agile Project Management with Kanban (Developer Best Practices)''

			:-This is an interesting reading written by Eric Brechner, who is the development manager working for Microsoft's Xbox Engineering Services. This manager has used Kanban during years with different teams. This book offers a guide full of content which has the objective on helping the reader achieve more productive environments. It is also centered in the obtention of results, focusing in the evolution from more traditional approaches to new ones. Also, an it is explained how Kanban could experiment an integration in a large project.

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

Guilleroigp: /* Agile in Project Management */

2022-03-27T21:36:38Z

Agile in Project Management

← Older revision		Revision as of 21:36, 27 March 2022
Line 82:		Line 82:

	=== Agile in Project Management ===		=== Agile in Project Management ===
	[[File:Pm_agile.png\|thumb\|right\|1500px\|'''Figure 4: Waterfall vs. Agile''' <ref name=figure4>Mark C. Layton, Steven J. Ostermiller, Dean J. Kynaston. (2020). “Agile project management for dummies”. </ref>]]		[[File:Pm_agile.png\|thumb\|right\|1500px\|'''Figure 4: Waterfall vs. Agile.''' <ref name=figure4>Mark C. Layton, Steven J. Ostermiller, Dean J. Kynaston. (2020). “Agile project management for dummies”. </ref>]]

	Over the last decades, project management has been changing from a more linear approach to an environment in which[[Wikipedia:agile\| agile''']] is dominating. This linear approach was followed through the [[Wikipedia:waterfall methodology\| waterfall methodology''']], where deadlines and objectives of every project are based on fixed estimations or assumptions, so companies drive their projects missing the changing environment that surrounds it. This waterfall methodology that companies use are proven to be inefficient in changing environments, as projects are supposed to follow clear steps which are not designed to be re-thinked or re-designed, so it can be very costly and time. <ref name="Dos">Andrew Stellman, Jennifer Greene, "Learn Agile: Understanding Scrum, XP, Lean and Kanban", 2015</ref>		Over the last decades, project management has been changing from a more linear approach to an environment in which[[Wikipedia:agile\| agile''']] is dominating. This linear approach was followed through the [[Wikipedia:waterfall methodology\| waterfall methodology''']], where deadlines and objectives of every project are based on fixed estimations or assumptions, so companies drive their projects missing the changing environment that surrounds it. This waterfall methodology that companies use are proven to be inefficient in changing environments, as projects are supposed to follow clear steps which are not designed to be re-thinked or re-designed, so it can be very costly and time. <ref name="Dos">Andrew Stellman, Jennifer Greene, "Learn Agile: Understanding Scrum, XP, Lean and Kanban", 2015</ref>

Guilleroigp: /* Agile in Project Management */

2022-03-27T21:36:12Z

Agile in Project Management

← Older revision		Revision as of 21:36, 27 March 2022
Line 89:		Line 89:

	Regarding project management, the application of agile can be addressed to different areas, such as software development, processes improvement or in any kind of project management. It was first used in the IT industry, where companies found in agile a great solution to solve the traditional problems found in software development processes. There is a mindset around the concept of agile consisting of a good flow of information between the stakeholders involved in order to bring more value to the customer while making progressive and meaningful steps. <ref name="ATL"> Atalassian Agile Coach. Last accessed 3rd March 2022, https://www.atlassian.com/es/agile/kanban/boards.</ref>		Regarding project management, the application of agile can be addressed to different areas, such as software development, processes improvement or in any kind of project management. It was first used in the IT industry, where companies found in agile a great solution to solve the traditional problems found in software development processes. There is a mindset around the concept of agile consisting of a good flow of information between the stakeholders involved in order to bring more value to the customer while making progressive and meaningful steps. <ref name="ATL"> Atalassian Agile Coach. Last accessed 3rd March 2022, https://www.atlassian.com/es/agile/kanban/boards.</ref>

			An example of the implementation of Kanban in a Software development project is shown in the next video. It shows how different principles are applied in a real case by the use of a digital Kanban tool:

			{{#ev:youtube\|https://www.youtube.com/watch?v=_QXlU8eMODE&ab_channel=KanbanTool}}

	====What is Scrum?====		====What is Scrum?====

Guilleroigp: /* Kanban Principles: implementation */

2022-03-27T21:35:58Z

Kanban Principles: implementation

← Older revision		Revision as of 21:35, 27 March 2022
Line 69:		Line 69:
	#'''Service level agreement [[Wikipedia:Service Level Agreement\|(SLA)]] and policies:''' to guarantee a good service level resultant from a project, minimum standards are stablished. This standards policies involve, for example, the assignment of tasks to the different project members or the momentum a task can be transferred to the next stage. These standards are stablished by the expectations of members involved in the project or affected by its outcomes.		#'''Service level agreement [[Wikipedia:Service Level Agreement\|(SLA)]] and policies:''' to guarantee a good service level resultant from a project, minimum standards are stablished. This standards policies involve, for example, the assignment of tasks to the different project members or the momentum a task can be transferred to the next stage. These standards are stablished by the expectations of members involved in the project or affected by its outcomes.
	#'''Models to identify improvement opportunities:''' project teams should work together and make an effort to analyze the current process and examine continuously what can be improved. This can be done by the application of models such as the Theory of Constraints or Value Stream mapping [[Wikipedia:Value Stream Mapping\|(VSM)]], for instance. <ref name="SANTOS"> P. Santos, A. Caetano, B. D. Souza, G. Travassos. (2018). “On the benefits and challenges of using Kanban in software engineering: a structured synthesis study”.</ref>		#'''Models to identify improvement opportunities:''' project teams should work together and make an effort to analyze the current process and examine continuously what can be improved. This can be done by the application of models such as the Theory of Constraints or Value Stream mapping [[Wikipedia:Value Stream Mapping\|(VSM)]], for instance. <ref name="SANTOS"> P. Santos, A. Caetano, B. D. Souza, G. Travassos. (2018). “On the benefits and challenges of using Kanban in software engineering: a structured synthesis study”.</ref>

	An example of the implementation of Kanban in a Software development project is shown in the next video. It shows how different principles are applied in a real case by the use of a digital Kanban tool:

	~~{{#ev:youtube\|https://www.youtube.com/watch?v=_QXlU8eMODE&ab_channel=KanbanTool}}~~

	=== Project measurement ===		=== Project measurement ===

Guilleroigp: /* Annotated bibliography */

2022-03-27T21:33:53Z

Annotated bibliography

← Older revision		Revision as of 21:33, 27 March 2022
Line 216:		Line 216:
	:-Study which reflects the real impact of applying Kanban on software development. A real case is presented centered in an experimental Research and Development (R&D) real software software. Different theoretical perspectives are considered, which reflect how Kanban is affecting the efficiency and motivation of workers.		:-Study which reflects the real impact of applying Kanban on software development. A real case is presented centered in an experimental Research and Development (R&D) real software software. Different theoretical perspectives are considered, which reflect how Kanban is affecting the efficiency and motivation of workers.

	:-		* Jeffrey Saltz, Robert Heckman (2020) ''Exploring Which Agile Principles Students Internalize When Using a Kanban Process Methodology''

			:-This reading offers an interesting approach about how useful the Kanban methodology is, all around the 12 principles included in the Agile Manifesto. This study is done because there is not many historical data that offers a real image of how enrichful applying this methodology to projects within school project teams. The study finds that there are two key agile principles having a clear impact on the way teams work. These results can help those who want to consider applying this methodology in school projects to decide among other agile methodologies.

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

Guilleroigp: /* Annotated bibliography */

2022-03-27T21:20:10Z

Annotated bibliography

← Older revision		Revision as of 21:20, 27 March 2022
Line 212:		Line 212:
	There are some references suggested for a further reading regarding Kanban as a project management framework:		There are some references suggested for a further reading regarding Kanban as a project management framework:

	* Marko Ikonen, et al. (2011) '''On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation'''		* Marko Ikonen, et al. (2011) ''On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation''

			:-Study which reflects the real impact of applying Kanban on software development. A real case is presented centered in an experimental Research and Development (R&D) real software software. Different theoretical perspectives are considered, which reflect how Kanban is affecting the efficiency and motivation of workers.

			:-

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

Guilleroigp: /* Anotated bibliography */

2022-03-27T21:14:19Z

Anotated bibliography

← Older revision		Revision as of 21:14, 27 March 2022
Line 209:		Line 209:
	<ref name="WISDOM"> Wisdom Plexus. Last accessed 7th March 2022, https://wisdomplexus.com/blogs/pros-cons-kanban/</ref><ref name="BRECHNER">Brechner. Eric. (2015). Agile Project Management with Kanban (Developer Best Practices).</ref>		<ref name="WISDOM"> Wisdom Plexus. Last accessed 7th March 2022, https://wisdomplexus.com/blogs/pros-cons-kanban/</ref><ref name="BRECHNER">Brechner. Eric. (2015). Agile Project Management with Kanban (Developer Best Practices).</ref>

	=~~Anotated~~ bibliography=		=Annotated bibliography=
			There are some references suggested for a further reading regarding Kanban as a project management framework:

			* Marko Ikonen, et al. (2011) '''On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation'''

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