Root Cause Analysis and People Factors in the Theory of Constraints
In this third post about how to improve risk management in the Kanban Method via the Theory of Constraints we look in the tools of TOC that can be used to perform Root Cause Analysis and how they can impact the opinions and support of the people in the organization.
Buffer Management and Risk Management in the Theory of Constraints
In this second post about how to improve risk management in the Kanban Method via the Theory of Constraints we discover what is and how to use Buffer Management
Critical Chain Project Management in the Theory of Constraints
The cross-pollination of two different schools of thought — the Kanban Method and the Theory of Constraints — generate innovative ways to manage projects, enhance risk management, and continuously improve your software engineering processes. Learn how with this first of a series of posts on the topic.
Theory of Constraints and Software Engineering
Explore how the Theory of Constraints and Throughput Accounting can be used to make better software engineering management decisions.
Agility as an Expression of Empiricism
It is in the layers of of middle management that fortresses of rationalism, determinism, and command-and-control mentality still have the strongest foothold.
Software Hyper-productivity and Function Points
While Function Points are a weak tool for estimating project, they do present this apparently interesting use case: after the fact assessments with Function Points give us a crude way to compare different projects.
Story Points Are NOT Function Points
When we critique Function Points and happen to mention Story Points in the same context, it is frequent to receive the objection that Story Points are like Function Points. The similarity is only superficial. In this post we examine the differences.
Function Points Are Fantasy Points
Function Points are a relic of the past; they are based on perceptions and opinions; they use many magic numbers and correction factor; they do not consider technology and its consequences on the project delivery life-cycle; they discount user experience and its development; they ignore the expert opinion of programmers; they are not based on math or real metrics. In short: Function Points are Fantasy Points!
Friction Is Feedback
Friction is like training: it prepares the company for the real race – the race that happens in the marketplace.
Software Craftsmanship Management
That is an oxymoronic title, with the words “Craftsmanship” and “Management” side by side! Isn’t the essence of craftsmanship skilled individuality? While management is the process of controlling people? Is there not a contradiction of terms here? What is this all about?