Quotes About Efficiency

Most journalists are impatient to get their legwork done and to start the actual writing

The telephone was a sign of being rushed.

The job of the union, he insisted, could be reduced to a simple idea: the protection of the slowest and least efficient worker.

The men were always wary of an officer who took form more seriously than function.

If you use your mobile for work, then it's highly advisable to have a separate mobile for your personal life.

HOMEOPATHS. Save money on petrol by filling up at the water pump. Your car will remember the petrol from the previous fill.

You're better off with a kick-ass half than a half-assed whole.

The answer is not more hours, it's less bullshit.

The physical board had a huge psychological effect compared to anything we got from the electronic tracking tool we used at Microsoft. By attending the standup each day, team members were exposed to a sort of time-lapse photography of the flow of work across the board. Blocked work items were marked with pink tickets, and the team became much more focused on issue resolution and maintaining flow. Productivity jumped dramatically.

It's good business to provide a good work/life balance by never overloading your teams.

if there is no explicit limit to work-in-progress and no signaling to pull new work through the system, it is not a kanban system.

First, how could I protect my team from the incessant demands of the business and achieve what the Agile community now refers to as a "sustainable pace"?

You need slack to enable continuous improvement. You need to balance demand against throughput and limit the quantity of work-in-progress to enable slack.

There should be no grand, centralized choice made in the ivory tower. The minor cost-efficient advantage of the whole staff being trained in one method is far outweighed by the problems created—and the real cost, in ROI terms—by using the wrong process for the job.

Put simply, excessive defects are the biggest waste in software development

encourage teams to inspect code every day for at least 30 minutes.

Reducing the quantity of design-in-progress boosts software quality.

Cumulative Flow Diagram

David J. Anderson

Drum-Buffer-Rope pull system

The Value of Kanban is Counter-Intuitive

Greenhopper for Jira

in real statistical analyses the computer takes over the tedium of arithmetic juggling.

The success combination in business is: Do what you do better... and: Do more of what you do...