Name: The Elements of Scrum
Rating: 4 (101 reviews)
Author: Chris Sims and Hillary Louise Johnson

What’s in it for me? Get agile and flexible, and learn how scrum will help you work better.

Do you think you have the best method for organizing a project? It’s a classic mistake, especially in software development. Each team has its own preferences and conceits: the designers want it one way, the coders another – and in the chaos, the client is left out in the cold.

The bottom line is that there is no set procedure, no perfect path from A to Z in developing great software products. But there are a couple of tricks that will get you as close to perfection as possible.

Today’s teams have to be flexible and agile, ready to bend with the whims and challenges that come their way. You have to make a plan then toss it aside, building another on the fly while keeping your eye on the ultimate goal.

How do you do this? Ditch those old waterfall methods and embrace scrum – an agile, flexible system that will change the way you think and revolutionize your development process.

In these blinks, you’ll learn

why “waterfalls” today will only get you wet;
how a 15-minute daily meeting is your ticket to success; and
why lots of sprints are far more efficient than a long, slow run.

The traditional methods of software development are inefficient and lead to cost overruns.

Tradition may have its charm, but it has few fans when it comes to technology development. Technology needs to be constantly updated to remain relevant; in fact, being current is essential not only to technology but also to the processes used to create it.

One system of development is called the waterfall method, which is a finish-to-start process for producing software. In such a system, a software team would typically compile requirements, make a design, write code, test and then deliver a finished product.

The “finish-to-start” aspect of the process is crucial. Activity A must be completed before work on activity B can start. For instance, you can’t begin testing a design until you’ve finished coding.

Why do people and organizations like this method?

By separating each development step, scheduling and planning is made easier. Managers often prefer a waterfall approach as they believe it allows them greater accuracy in scheduling and allocating budgets.

But the waterfall method isn’t very reliable. Software is often too complicated a product to be fully designed before production starts. Therefore, if you demand a perfectly designed product, you’ll be left with little wiggle room for change during production.

So while it’s possible for a perfect design to seamlessly transition to a perfect production process, this usually only occurs when you’re producing a static object, like a car. In this example, you’d design every element in the car, then follow those design directions to the letter during manufacturing.

But software production, in contrast, is just too complex.

So, while designers may come up with what they think is a perfect product, complications are sure to arise when designs are applied. The numbers tell the tale: only 16 percent of waterfall-method projects meet completion deadlines, while 31 percent are cancelled and 53 percent go over budget!

How do you avoid such a pitfall in your own projects? Read on to learn more.

The four core values of agility pave the way to a streamlined, efficient and successful process.

You’re driving along your usual route to work when you see that an accident is blocking the intersection ahead. What do you do? Would you wait for the accident to clear, or turn down an unfamiliar road to explore a way around?

If you said turn and explore, you’ve already got one of the four key values of agility. Each value represents a priority, or a choice between different approaches.

Sprints revolve around the experience and stories of your users.

A crucial aspect of every sprint planning meeting is coming up with a great user experience. But how do scrums incorporate this element in the process? Through user stories.

Stories are a simple way to show how people actually use a product. They’re called user stories to ensure a team keeps its attention on the end customer and not the product owner, designer or coder.

Incorporate the three types of scrum meetings to ensure the responsiveness and agility of the sprint.

So your team just launched a new project, and everyone says they’re clear on scope and expectations and is hard at work. A month passes, and you gather to share notes – and then the trouble starts.

Three teammates have finished their tasks, two are stuck mulling a problem and can’t finish and one guy took it upon himself to change his task in a way that messes up everyone else’s work.

Kernaussagen in The Elements of Scrum

Worum geht es in The Elements of Scrum?

The Elements of Scrum (2011) explains how outmoded software development processes are holding companies back in an ever-changing market. Today’s successful teams need to be agile and flexible; and the best companies do this by adopting a methodology called scrum. This book gives you everything you need to know to start a scrum-based process in your own organization.