Scrum: The Art of Doing Twice the Work in Half the Time
Rate it:
23%
Flag icon
there’s a hardwired limit to what our brain can hold at any one time.
23%
Flag icon
The first is the time it takes to bring people up to speed.
23%
Flag icon
The number of communication channels increases dramatically with the number of people, and our brains just can’t handle it.
23%
Flag icon
everyone on a Scrum team has to know what everyone else is doing. All the work being done, the challenges faced, the progress made, has to be transparent to everyone else.
23%
Flag icon
intense focus on the goal,
23%
Flag icon
radical collaboration—arms
23%
Flag icon
hunger to crush—anything
23%
Flag icon
universal exc...
This highlight has been truncated due to consecutive passage length restrictions.
24%
Flag icon
It was the Scrum Master’s job to guide the team toward continuous improvement—to
24%
Flag icon
“What can we change about how we work?” and “What is our biggest sticking point?”
24%
Flag icon
“Fundamental Attribution Error.”
24%
Flag icon
Processes of Inference, Learning, and Discovery, by John H. Holland
24%
Flag icon
We all perceive ourselves as responding to a situation, while we see others as motivated by their character.
27%
Flag icon
Time is the ultimate limiter of human endeavor, affecting everything from how much we work, to how long things take, to how successful we are.
27%
Flag icon
The sooner you give things to your customers, the quicker they can tell you if you’re making something they need.
30%
Flag icon
The meeting was held at the same time every day, and everyone had to be there.
30%
Flag icon
the meeting couldn’t last more than fifteen minutes.
30%
Flag icon
third rule was that everyone had to actively participate.
30%
Flag icon
I want aggressive teams—ones that come out of the daily meeting knowing the most important thing they need to accomplish that day.
30%
Flag icon
team has to demand greatness from itself.
31%
Flag icon
Demo or Die. At the end of each Sprint, have something that’s done—something that can be used (to fly, drive, whatever).
31%
Flag icon
Everyone Knows Everything. Communication saturation accelerates work.
32%
Flag icon
He used the Japanese words: Muri, waste through unreasonableness; Mura, waste through inconsistency; and Muda, waste through outcomes. These ideas are highly aligned with Deming’s PDCA cycle, which I wrote about earlier: Plan, Do, Check, Act. Plan means avoid Muri. Do means avoid Mura. Check means avoid Muda. Act means the will, motivation, and determination to do all that.
34%
Flag icon
Quality Software Management by Gerald Weinberg:
34%
Flag icon
The “Loss to Context Switching” column is pure waste.
34%
Flag icon
“Dual Task Interference.”
34%
Flag icon
a certain amount of effort is involved in “packing up” one process, reaching into your memory and pulling out another, and then running that job. And each time you switch tasks, that process takes time.
34%
Flag icon
They don’t change how big the project is, or what’s involved in creating it, but just by doing one thing exclusively before moving on, the work takes a little more than half as much time.
35%
Flag icon
multitasking not only wastes your time but makes you stupid.
35%
Flag icon
the mean IQ scores of the subjects dropped by more than ten points when in distracting environments.
35%
Flag icon
Doing half of something is, essentially, doing nothing.
35%
Flag icon
that “Done” implies a complete, deliverable product that can be used by a customer.
35%
Flag icon
If something is half done at the end of the Sprint, you’re worse off than if you hadn’t started at all.
35%
Flag icon
It might have been better to create something smaller—something that really works.
36%
Flag icon
too much inventory is pretty much the same thing as work in process. If you’re tying up a huge amount of value in things that aren’t delivering value, you won’t have those resources to do other things—such
36%
Flag icon
The Machine That Changed the World.
36%
Flag icon
The idea is that the process is being continuously improved, and that the right moment to fix a problem is when it is observed, not after the fact.
37%
Flag icon
It took twenty-four times longer. If a bug was addressed on the day it was created, it would take an hour to fix; three weeks later, it would take twenty-four hours.
37%
Flag icon
if you do make a mistake—and we all make them—fix it as soon as you notice it.
37%
Flag icon
Work too long, he said, and you get less done.
38%
Flag icon
The peak of productivity actually falls at a little bit less than forty hours a week.
38%
Flag icon
working late wasn’t a sign of commitment; it was a sign of failure.
38%
Flag icon
“A lot of companies don’t practice [work-hour limits],” says Scott. “But there is a direct correlation. You get more done. You are happier. And you have higher quality.”
38%
Flag icon
Working less helps you get more done with higher quality.
39%
Flag icon
So there’s a limited number of sound decisions you can make in any one day, and as you make more and more, you erode your ability to regulate your own behavior.
39%
Flag icon
measure output. Who cares how many hours someone worked on something? All that matters is how fast it’s delivered and how good it is.
39%
Flag icon
“Absurdity.” You want to give your team challenging goals—to push them to reach for more. But you don’t want them striving for absurd, impossible goals.
39%
Flag icon
“Unreasonable Expectations.”
39%
Flag icon
A team that depends on regular heroic actions to make its deadlines is not working the way it’s supposed to work.
39%
Flag icon
“Overburden.”