Waterfall vs. Pull Processes - Revision history

Tkokotas at 17:10, 16 November 2018

2018-11-16T17:10:33Z

← Older revision		Revision as of 17:10, 16 November 2018
Line 1:		Line 1:
			''Developed by Johannes Eckert''


	There are many different methodologies of project management, all of them are defined by different principles and processes.<ref name="standard">Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref> A traditional, sequential methodology, is the waterfall model. Within this model, the tasks of the project plan are sequenced and conducted in a linear way, one task must be completed before the next one begins - the process is smooth and continuous, like a waterfall.<ref name="wrike">Project Management Methodologies, https://www.wrike.com/project-management-guide/methodologies/ </ref> Therefore, this model is one of the simplest methods.<ref name="wrike"/> However, the pull process-based methodologies are used to create the whole project plan more efficient and effective, it was created to eliminate confounding factors within the project and to avoid aimless work. Hence, the pull processes are used in the management style of Lean Project Management, typical pull processes can be find in the Scrum and Kanban methodologies.<ref name="wrike"/> This article provides an introduction to the waterfall methodology, to understand the processes within a project plan in a better way. However, the article provides a comparison of the waterfall process (push process) and the pull process. Therefore, no other methodologies e.g. Scrum and Kanban are explained. After the introduction into both processes, pros and cons are described and the relevance for the practical usage demonstrated. At the end of the article and the comparison section, a short guidance about the right selection of the processes is provided.		There are many different methodologies of project management, all of them are defined by different principles and processes.<ref name="standard">Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref> A traditional, sequential methodology, is the waterfall model. Within this model, the tasks of the project plan are sequenced and conducted in a linear way, one task must be completed before the next one begins - the process is smooth and continuous, like a waterfall.<ref name="wrike">Project Management Methodologies, https://www.wrike.com/project-management-guide/methodologies/ </ref> Therefore, this model is one of the simplest methods.<ref name="wrike"/> However, the pull process-based methodologies are used to create the whole project plan more efficient and effective, it was created to eliminate confounding factors within the project and to avoid aimless work. Hence, the pull processes are used in the management style of Lean Project Management, typical pull processes can be find in the Scrum and Kanban methodologies.<ref name="wrike"/> This article provides an introduction to the waterfall methodology, to understand the processes within a project plan in a better way. However, the article provides a comparison of the waterfall process (push process) and the pull process. Therefore, no other methodologies e.g. Scrum and Kanban are explained. After the introduction into both processes, pros and cons are described and the relevance for the practical usage demonstrated. At the end of the article and the comparison section, a short guidance about the right selection of the processes is provided.

Johannes: /* Waterfall vs. Pull */

2018-02-28T19:45:38Z

Waterfall vs. Pull

← Older revision		Revision as of 19:45, 28 February 2018
Line 158:		Line 158:
	If the stakeholder expectations are clear, like in the common way of a construction of physical objects, the look, the material, the functions, the aim in general is definite, the work with waterfall processes should be preferred. The tradition sequential relationship between the phases would be beneficial due to the clear structure and the define connection between the different working steps.		If the stakeholder expectations are clear, like in the common way of a construction of physical objects, the look, the material, the functions, the aim in general is definite, the work with waterfall processes should be preferred. The tradition sequential relationship between the phases would be beneficial due to the clear structure and the define connection between the different working steps.
	If the product itself is not really defined until the end of the project and especially the design and function phase is a flowing process through the project, like in a software product, an app or even a service, a more flexible project plan with pull processes are needed. However, when the development itself is the main factor for choosing the right process, the amount of workload and the associated time and money is the reason why for especially minimum viable products the pull processes are preferred.		If the product itself is not really defined until the end of the project and especially the design and function phase is a flowing process through the project, like in a software product, an app or even a service, a more flexible project plan with pull processes are needed. However, when the development itself is the main factor for choosing the right process, the amount of workload and the associated time and money is the reason why for especially minimum viable products the pull processes are preferred.

	[[File:Push vs. Pull Workload.jpg\|thumb\|Push vs. Pull workload<ref name="workload">Own image, according to: Understanding Lean Project Management, https://project-management.com/understanding-lean-project-management/ </ref>]]

	Secondly, the consideration of the project team, how many people, how qualified they are and in which way they are used to work within a project, is an important factor for choosing the right processes.		Secondly, the consideration of the project team, how many people, how qualified they are and in which way they are used to work within a project, is an important factor for choosing the right processes.

Johannes: /* Waterfall vs. Pull */

2018-02-28T19:44:47Z

Waterfall vs. Pull

← Older revision		Revision as of 19:44, 28 February 2018
Line 156:		Line 156:

	Firstly, it is important to have a look to the requirements, the aims of the project and the objectives. In addition, the look and the benefits of the final deliverable take into account.		Firstly, it is important to have a look to the requirements, the aims of the project and the objectives. In addition, the look and the benefits of the final deliverable take into account.
	If the stakeholder expectations are clear, like in the common way of a construction of physical objects, the look, the material, the functions, the aim in general is definite. ~~In this case a~~ tradition sequential relationship between the phases would be beneficial due to the clear structure and the define connection between the different working steps.		If the stakeholder expectations are clear, like in the common way of a construction of physical objects, the look, the material, the functions, the aim in general is definite, the work with waterfall processes should be preferred. The tradition sequential relationship between the phases would be beneficial due to the clear structure and the define connection between the different working steps.
	If the product itself is not really defined until the end of the project and especially the design and function phase is a flowing process through the project, like in a software product, an app or even a service, a more flexible project plan with pull processes are needed. However, when the development itself is the main factor for choosing the right process, the amount of workload and the associated time and money is the reason why for especially minimum viable products the pull processes are preferred.		If the product itself is not really defined until the end of the project and especially the design and function phase is a flowing process through the project, like in a software product, an app or even a service, a more flexible project plan with pull processes are needed. However, when the development itself is the main factor for choosing the right process, the amount of workload and the associated time and money is the reason why for especially minimum viable products the pull processes are preferred.

Johannes: /* Pull Process */

2018-02-28T19:42:02Z

Pull Process

← Older revision		Revision as of 19:42, 28 February 2018
Line 118:		Line 118:

	The common definition of the pull process is, that the customer pulls the value from the project team, but not just the customer is pulling, the subsequent is pulling as well. Thereby, the subsequent is giving the impulse and states in this way when the next phases is starting. Typical pull processes can find in the Kanban or in the Scrum methodology and make those models more flexible and reduces the waste.		The common definition of the pull process is, that the customer pulls the value from the project team, but not just the customer is pulling, the subsequent is pulling as well. Thereby, the subsequent is giving the impulse and states in this way when the next phases is starting. Typical pull processes can find in the Kanban or in the Scrum methodology and make those models more flexible and reduces the waste.
	In total the pull processes avoid delivering value before the customer or a colleague ~~request~~ it.<ref name="attrup"/> In addition, the pull processes avoid the provision of more than the agreed initial scope, it allows the implementation of a just-in-time system.		In total the pull processes avoid delivering value before the customer or a colleague requests it.<ref name="attrup"/> In addition, the pull processes avoid the provision of more than the agreed initial scope, it allows the implementation of a just-in-time system.

	As distinguished from the push process, ~~where~~ the team leader is "pushing" the tasks to his team members, and put in this way work on a "to-do" list, pull processes allow the team members doing the work when they are ready. Hence, pull processes prevents team members from stress and work on results which will be eliminate in a later stage. A big benefit for the project work is, that tasks or items can be prioritized.<ref name="attrup"/> In this way the project manager can work with his team on the right tasks at the right time while reducing wasted time or effort.		As distinguished from the push process, whereby the team leader is "pushing" the tasks to his team members, and put in this way work on a "to-do" list, pull processes allow the team members doing the work when they are ready. Hence, pull processes prevents team members from stress and work on results which will be eliminate in a later stage. A big benefit for the project work is, that tasks or items can be prioritized.<ref name="attrup"/> In this way the project manager can work with his team on the right tasks at the right time while reducing wasted time or effort.

Johannes: /* Waterfall Process */

2018-02-28T19:38:45Z

Waterfall Process

← Older revision		Revision as of 19:38, 28 February 2018
Line 82:		Line 82:


	With the waterfall model, the different sequences and the sequential relationship in mind, it is important to know that in this flow of processes, the tasks are pushed by the team leader to the project team members. Although it's resulting in a higher amount of workload, the tasks are handled step-by-step, even when the result is not used in the next phase anymore~~. This work method is attributed to the planning in the early stage of the project~~.		With the waterfall model, the different sequences and the sequential relationship in mind, it is important to know that in this flow of processes, the tasks are pushed by the team leader to the project team members. Although it's resulting in a higher amount of workload, the tasks are handled step-by-step, even when the result is not used in the next phase anymore.

	[[File:Push Process.png\|frame\|Push Process<ref name="malik"/>]]		[[File:Push Process.png\|frame\|Push Process<ref name="malik"/>]]

Johannes: /* Waterfall Process */

2018-02-28T19:37:12Z

Waterfall Process

← Older revision		Revision as of 19:37, 28 February 2018
Line 49:		Line 49:
	[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]		[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]

	The waterfall model is preferred when the product or service to be delivered is well understood ~~and the~~ following ~~processes~~ describe the waterfall model.		The waterfall model is preferred when the product or service to be delivered is well understood.
			The following phases describe the waterfall model:

Johannes: /* Waterfall Process */

2018-02-28T19:35:36Z

Waterfall Process

← Older revision		Revision as of 19:35, 28 February 2018
Line 45:		Line 45:
	=Waterfall Process=		=Waterfall Process=

	The waterfall model (also known as predictive life cycle or fully plan-driven)<ref name="standard"/> is made of a waterfall process, which is defined by sequential relationships. A phase, consisting generally all five process groups, starts only when the previous phase is complete. ~~(image no.1)~~ This approach reduces uncertainty within the project life cycle, but it requests a high amount of tasks. As a result, this process is defined by a huge workload. In addition, the project scope, and the time and the cost required to deliver that scope, are determined at the beginning of the project life cycle. Therefore, the project is inflexible and changes are related to high costs.<ref name="standard"/>		The waterfall model (also known as predictive life cycle or fully plan-driven)<ref name="standard"/> is made of a waterfall process, which is defined by sequential relationships. A phase, consisting generally all five process groups, starts only when the previous phase is complete. This approach reduces uncertainty within the project life cycle, but it requests a high amount of tasks. As a result, this process is defined by a huge workload. In addition, the project scope, and the time and the cost required to deliver that scope, are determined at the beginning of the project life cycle. Therefore, the project is inflexible and changes are related to high costs.<ref name="standard"/>

	[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]		[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]

Johannes: /* Waterfall Process */

2018-02-28T19:35:16Z

Waterfall Process

← Older revision		Revision as of 19:35, 28 February 2018
Line 45:		Line 45:
	=Waterfall Process=		=Waterfall Process=

	The waterfall model (also known as predictive life cycle or fully plan-driven)<ref name="standard"/> is made of a waterfall process, which is defined by sequential relationships. A phase, consisting generally all five process groups, starts only when the previous phase is complete. This approach reduces uncertainty within the project life cycle, but it requests a high amount of tasks. As a result, this process is defined by a huge workload. In addition, the project scope, and the time and the cost required to deliver that scope, are determined at the beginning of the project life cycle. Therefore, the project is inflexible and changes are related to high costs.<ref name="standard"/>		The waterfall model (also known as predictive life cycle or fully plan-driven)<ref name="standard"/> is made of a waterfall process, which is defined by sequential relationships. A phase, consisting generally all five process groups, starts only when the previous phase is complete. (image no.1) This approach reduces uncertainty within the project life cycle, but it requests a high amount of tasks. As a result, this process is defined by a huge workload. In addition, the project scope, and the time and the cost required to deliver that scope, are determined at the beginning of the project life cycle. Therefore, the project is inflexible and changes are related to high costs.<ref name="standard"/>

	[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]		[[File:The waterfall process.jpg\|frame\|The waterfall sequential model<ref name="own">Own image, according to: Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>]]

Johannes: /* Importance for Project Management */

2018-02-28T19:34:10Z

Importance for Project Management

← Older revision		Revision as of 19:34, 28 February 2018
Line 39:		Line 39:

	With this description of the characteristics of a project life cycle, we can have a look to the different life cycles, which are designed for different purposes.<ref name="attrup"/> The main difference of the waterfall model and the pull processes is the influence of the stakeholder and the degree of flexibility.		With this description of the characteristics of a project life cycle, we can have a look to the different life cycles, which are designed for different purposes.<ref name="attrup"/> The main difference of the waterfall model and the pull processes is the influence of the stakeholder and the degree of flexibility.
	Adaptive life cycles keep stakeholders in the loop and let them influence the project in a higher degree than a predictive life cycle (waterfall). Since, the project plan within a adaptive life cycle is more flexible the costs of changes are lower.<ref name="standard"/>		Adaptive life cycles keep stakeholders in the loop and let them influence the project in a higher degree than a predictive life cycle (waterfall). Since, the project plan within an adaptive life cycle is more flexible, the costs of changes are lower.<ref name="standard"/>

	The importance to think about the way how to execute the project and how flexible and influenceable it should be is enormous. Therefore, the following chapters will provide some clarity about the choose of process ~~styles~~.		The importance to think about the way how to execute the project and how flexible and influenceable it should be is enormous. Therefore, the following chapters will provide some clarity about the choose of the right type of process.

	=Waterfall Process=		=Waterfall Process=

Johannes: /* Importance for Project Management */

2018-02-28T19:31:11Z

Importance for Project Management

← Older revision		Revision as of 19:31, 28 February 2018
Line 21:		Line 21:


	The project manager has to combine those groups and phases into a flow and take into account the product or service, his team and the customer.<ref name="attrup">Attrup et al (2015). Power in Projects, Programs and Portfolios: Achieve project excellence and create change with strategic impact 1st Edition, Djoef Publishing Inc </ref> To establish a real customer value the project should set up a scope baseline control, build a communication plan to improve the information flow, asses stakeholder needs and get the commitment of the internal stakeholder.<ref name="standard"/> As a result, there are many factors which have to be intertwine to each other. Thus, project managers are inclined to overlook something at the beginning of the project and this is when project wastes start building. It is important to align with the customers to establish the customer value, but if the customer ~~is deflect~~ the project team members it will be end in scope creep. As an interim conclusion, the project planning has to consider a lot of things simultaneously, but it is also very important to ponder in which way and rate the steps are executed.<ref name="attrup"/>		The project manager has to combine those groups and phases into a flow and take into account the product or service, his team and the customer.<ref name="attrup">Attrup et al (2015). Power in Projects, Programs and Portfolios: Achieve project excellence and create change with strategic impact 1st Edition, Djoef Publishing Inc </ref> To establish a real customer value the project should set up a scope baseline control, build a communication plan to improve the information flow, asses stakeholder needs and get the commitment of the internal stakeholder.<ref name="standard"/> As a result, there are many factors which have to be intertwine to each other. Thus, project managers are inclined to overlook something at the beginning of the project and this is when project wastes start building. It is important to align with the customers to establish the customer value, but if the customer deflects the project team members it will be end in scope creep. As an interim conclusion, the project planning has to consider a lot of things simultaneously, but it is also very important to ponder in which way and rate the steps are executed.<ref name="attrup"/>
	[[File:Impact_of_Variable_Based_on_Project_Time.png\|frame\|Impact of Variable Based on Project Time<ref name="standard"/>]]		[[File:Impact_of_Variable_Based_on_Project_Time.png\|frame\|Impact of Variable Based on Project Time<ref name="standard"/>]]