of people who think it's time for change in the IT industry - time to stop wasting money, time to start delivering great software, and building systems that scale and last. - Stephen Nelson-Smith, 2010 jedi.be/blog/2010/02/12/what-is-this-devops-thing-anyway
whose work you see on the Web, who probably don't know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups. - Tim Bray, 2010 tbray.org/ongoing/When/201x/2010/01/02/Doing-It-Wrong
waste. • Amplify learning. • Decide as late as possible. • Deliver as soon as posible. • Build quality in. • See the whole (system thinking). en.wikipedia.org/wiki/Lean_software_development
problem, express what the problem is in one sentence. date owner who owns the problem? who helps with solving it? problem description why is this a problem? how big is the problem? agree on scope. problem as a gap to a standard. risk for business impact of the problem. priority and importance of the problem. root-cause analysis use the five whys, or a fishbone diagram to find the causes for the problem. countermeasure plan decide on two or three possible causes for the problem. grasp the situation identify point of cause: exact place and reason the process goes wrong. execution plan details the way countermeasures will be effectively implemented, preferably with time frames. checking results instead of moving to something else, carefully check that the problem has been eliminated and solved. measure the effectiveness of the countermeasures and their impact on the overall process. followup and learning points effective solutions have a high chance to be applied elsewhere. weave solutions back into the process for the next cycle. also every problem solved often uncovers other issues which can now be details for further consideration. A3