Power makes knowledge sufficient Whether it is civil rights' violations in many countries, whether it is the increasing numbers of unemployed people in our own country, whether it is the homeless we see on our way to work, it isn't as though we don't know. But there is that horrible realization that, while the knowledge of facts may be a necessary condition for action, and we talk about democracy in civic action, it is unfortunately not a sufficient one. While knowledge may be a necessary condition, it may in fact be a less necessary condition that the one that makes that a sufficient condition, and that is access to power. Ursula M. Franklin, Every Tool Shapes the Task power
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair