ProjectManager.com

APRIL 25, 2024

Learn more History of Kanban Kanban was first introduced in Japan as a lean manufacturing approach pioneered by Taiichi Ohno in the late 1940s. The book laid out the principles of lean manufacturing, which focuses on reducing waste, creating customer value and seeking continuous process improvement, and kanban.

Manufacturing 359

Manufacturing 2004 Software Review 2009 359

Herding Cats

DECEMBER 16, 2017

Software Sizing and Estimating: Mk II FPA , Charles Symons, John Wiley & Sons, 1991. Estimating Software Costs: Bringing Realism to Estimating , Second Edition, Capers Jones, 2007. Software Cost Estimation with COCOMO II , Barry Boehm, et. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006. Prentice Hall, 2000.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Herding Cats

MARCH 11, 2017

Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. McMahon, Cross Talk: The Journal of Defense Software Engineering , July/August 2015, pp. Architecting Large Scale Agile Software Development: A Risk–Driven Approach,” Ipek Ozkaya, Michael Gagliardi, Robert L. Kirkeboen, G., &

2003 46

2003 2014 2011 2015 46

Herding Cats

MAY 7, 2019

61, September 2004. Effort Estimation of Use Cases for Incremental Large-Scale Software Development,” Pareastoo Mohagheghi, Bente Anda, and Reidat Conradi, Proceedings of the 27th international conference on Software engineering. Patnail, International Journal of Software Engineering, IJSE, 8.1,

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

MAY 10, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 920, November 2004. Software Engineering Institute, January 1996.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 920, November 2004. México, 1 al 3 de Febrero de 2006. De Meyer, C. Loch, and M.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

NOVEMBER 7, 2016

The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ‒ Steve McConnell. Software quality measurement,” Magne Jørgensen, Advances in Engineering Software 30 (1999) 907–912.

Estimate 64

Estimate 2006 2005 2012 64