To pull or not to pull

The Toyota Production System promotes "pull" scheduling to reduce the production of parts that do not comply to what the customer needs. The use of "pull" within software represents a radical change in the way activities are planned. This article gives two examples of the possible application of "pull" within software engineering and de-scribes a measurement tool to assess the current costs and amount of rework within a software development project. The described approach aims to help practitioners to under-stand whether to use "pull" or "push" in their organizations.

[1]  The Challenges of Complex IT Projects , 2004 .

[2]  Victor R. Basili,et al.  Characterizing and Modeling the Cost of Rework in a Library of Reusable Software Components , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[3]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[4]  Sebastian G. Elbaum,et al.  Code churn: a measure for estimating the impact of code change , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).

[5]  Ben Shneiderman,et al.  Tree visualization with tree-maps: 2-d space-filling approach , 1992, TOGS.

[6]  Richard W. Selby.  Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management, and Research , 2007 .

[7]  Farhad Arbab,et al.  Coordination Models and Languages , 1998, Adv. Comput..

[8]  W. Ouchi.  The Relationship Between Organizational Structure and Organizational Control. , 1977 .

[9]  Siew Hock Ow,et al.  QUALPRO-RP - AN ERRORS MANAGEMENT AND REWORK EFFORT MEASUREMENT TOOL , 2002 .

[10]  Hans de Bruin,et al.  Quality-driven software architecture composition , 2003, J. Syst. Softw..

[11]  Markus Pizka,et al.  Goal-Driven Software Development , 2006, 2006 30th Annual IEEE/NASA Software Engineering Workshop.

[12]  Mary Poppendieck,et al.  Lean Software Development: An Agile Toolkit , 2003 .

[13]  Marco Torchiano,et al.  On the effectiveness of the test-first approach to programming , 2005, IEEE Transactions on Software Engineering.

[14]  J. Cutcher-Gershenfeld,et al.  Lean Thinking , 2019, Encyclopedia of Sustainable Management.

[15]  Danilo Valeros Bernardo,et al.  Criteria for Estimating Effort for Requirements Changes , 2008, EuroSPI.

[16]  Luigi Lavazza,et al.  Requirements-Based Estimation of Change Costs , 2000, Empirical Software Engineering.

[17]  Mary Poppendieck,et al.  Lean Software Development , 2007, 29th International Conference on Software Engineering (ICSE'07 Companion).

[18]  Kent L. Beck,et al.  Test-driven Development - by example , 2002, The Addison-Wesley signature series.

[19]  H. Erdogmus.  A cost effectiveness indicator for software development , 2007, ESEM 2007.

[20]  Richard E. Fairley,et al.  Iterative rework: the good, the bad, and the ugly , 2005, Computer.