The IIL Blog

MAY 17, 2023

My Keynote Presentation is about the development of project management and project managers in the Bosch Group. I will focus on two selectively chosen business units that have already gone through the agile transformation: ETAS (Bosch’s Software Development Subsidiary) and Bosch Power Tools.

Agile 88

Agile 2011 2016 2019 88

Digite

JANUARY 7, 2018

hours, Published February 2nd, 2011 by Createspace Independent Publishing Platform). If you want to improve or create the flow in your product development process start with this book! This book also covers the relevant bits of theory on Kanban before presenting the case studies. Personal Kanban: Mapping Work – Navigating Life.

Lean 79

Lean Software Review 2010 2014 79

Agilemania

JANUARY 24, 2022

These frameworks also encourage you to use Lean principles to optimize your flow. In 2011, Dean Leffingwell codified SAFe, the Scaled Agile Framework , to help bring the success that small teams have enjoyed with various agile methodologies such as Scrum or XP but scaled to the enterprise. What is SAFe?

Agile 98

Agile Lean 2011 SCRUM 98

Scrum.org

JANUARY 6, 2022

Of course, this list changes with the markets, but if you compare that to 2011, the list is 60% different. Scrum, agile thinking, modern software development working practices are synonymous with Digital Technology and have evolved out of the fundamentally different characteristics of the opportunity presented by technology.

Underperforming Technical Team 218

Underperforming Technical Team Innovation 2001 2011 218

Herding Cats

MARCH 11, 2017

The notion (as suggested in the quote) of shifting from accurate (what ever that means) ways of estimating to reliability shipping be a date is not physically possible since the irreducible and reducible uncertainties are always present. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E.

2003 46

2003 2014 2015 2011 46

Herding Cats

MAY 10, 2019

IEEE Transactions on Software Engineering , Vol. 5, September/October 2011. Project risk management: lessons learned from software development environment,” Young Hoon Kwak and Jim Stoddard,” Technovation , 24(11), pp. Combination of the Earned Value and Present Value Methods,” Barbara G?adysz 3, March 2002.

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. IEEE Transactions on Software Engineering , Vol.

Risk Management 35

Risk Management Risk Technical Review 2002 35