The IIL Blog

JANUARY 24, 2024

LEAN processes emerged in 1991, with the Agile Manifesto launched by a group of software engineers in 2001. ITIL v2 followed this in 2001, ITIL v3 in 2007, and ITIL 4 in 2019. As ITSM evolved, so did the ways of delivering Information Technology services. Service Integration and Management, aka SIAM, was developed in 2005.

2007 78

2007 2001 Information Technology 2024 78

LiquidPlanner

JUNE 1, 2016

We didn’t really realize it at the time, but we built and launched the company using many of the concepts that Eric Ries later elegantly defined in his 2008 book The Lean Startup. This spirt of gathering customer research, prototyping a minimum viable product, deploying and iterating lives on. So if you fit this bill, we’re hiring !

2006 74

2006 2008 Software Engineering Engineering 74

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. Nord, CrossTalk: The Journal of Defense Software Engineering , May/June 2013. Risk: The Final Agile Frontier,” Troy Magennis, Agile 2015.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 7, 2019

“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. Software Development Effort Estimation using Fuzzy Bayesian Belief Network with COCOMO II,” B. 9, Issue 3, No.

Estimate 40

Estimate Software Review Software 2012 40

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

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. Software Engineering Institute, January 1996. De Meyer, C. Loch, and M.

Risk Management 38

Risk Management Risk Technical Review 2002 38