Tree visualization with tree-maps: 2-d space-filling approach
ACM Transactions on Graphics (TOG)
Characterizing and modeling the cost of rework in a library of reusable software components
ICSE '97 Proceedings of the 19th international conference on Software engineering
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Test Driven Development: By Example
Test Driven Development: By Example
Requirements-Based Estimation of Change Costs
Empirical Software Engineering
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit
Code Churn: A Measure for Estimating the Impact of Code Change
ICSM '98 Proceedings of the International Conference on Software Maintenance
Quality-driven software architecture composition
Journal of Systems and Software - Special issue on: Software architecture - Engineering quality attributes
On the Effectiveness of the Test-First Approach to Programming
IEEE Transactions on Software Engineering
ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
Goal-Driven Software Development
SEW '06 Proceedings of the 30th Annual IEEE/NASA Software Engineering Workshop
Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management, and Research (Practitioners)
A cost effectiveness indicator for software development
ESEM '07 Proceedings of the First International Symposium on Empirical Software Engineering and Measurement
The dark side of agile software development
Proceedings of the ACM international symposium on New ideas, new paradigms, and reflections on programming and software
Hi-index | 0.00 |
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.