The IIL Blog

FEBRUARY 14, 2024

The Four Aspects of Innovation How can an organization effectively reinvent itself overnight? The longer answer requires understanding how the DVMS CPD model Innovate capability enables organizations to adapt to a new paradigm. Now everyone “walks the walk.” Well, the short answer is it can’t.

2005 78

2005 2015 Innovation Certification 78

Herding Cats

DECEMBER 16, 2017

The estimating of software development is both straightforward and complex. Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. Software Metrics: A Rigorous and Practical Approach, Thord Edition , Norma Fenton and James Bieman.

Software Developers 46

Software Developers Software Development Estimate 2006 46

Digite

AUGUST 14, 2017

Be it the “software development process” or the “employee onboarding process” or “the procurement process” – agility is rapidly becoming a cornerstone of our digital world. The first Kanban system at Microsoft in 2005 produced productivity gains of 230%. The method wars. Getting to “pull” is a paradigm shift.

Agile 94

Agile Lean 2005 Risk Management 94

Herding Cats

MAY 10, 2019

Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Kadane, and Anthony O’Hagan, Carnegie Mellon University, Statistics & Data Science, January 5, 2005. Elsevier, 2005. 15 July 2005. 255, April 2010. 920, November 2004.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. Elsevier, 2005. 255, April 2010. Kwak and J.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Wrike

AUGUST 14, 2020

Anderson is often credited as being the first to implement Kanban in software development in 2005. Innovation and ideas for improvement should be promoted at all levels. It wasn’t until the early 2000s that Kanban started to take root in project management. Encourage leadership.

Software Review 36

Software Review Technical Review 2005 SCRUM 36

Rebel’s Guide to PM

SEPTEMBER 26, 2016

We are attracted to the latest cool application, with the potential to jeopardise the software environment. This could be a reaction to old structured and inflexible systems but pushing an agenda of continuous innovation without a tangible, declared objective could be even worse.

Software Review 150

Software Review Software Technical Review PMI 150