By 2001, the software industry was in trouble—more projects were failing than
Customers began demanding contracts with penalties, and increasingly
sending work offshore. Some software developers, though, had increasing success with
a development process known as “lightweight.” Almost uniformly, these processes were
based on the well-known iterative, incremental process.
In February of 2001, these developers issued a manifesto—the Agile Manifesto.
The Manifesto called for Agile software development based on 4 principle values and
12 underlying principles. Two of the principles were 1.) to satisfy customers through
early and continuous delivery of working software, and 2). to deliver working software
frequently, from a couple of weeks to a couple of months, with a preference to the
By 2008, the Scrum Agile process was used predominantly. A simple framework, it
provided an easily adopted iterative incremental framework for software development.
It also incorporated the Agile Manifesto’s values and principles. The two authors of
Scrum, Jeff Sutherland and myself, also were among the authors of the Agile Manifesto.
I had anticipated some of the difficulties organizations (and even teams) would
face when they adopted Scrum. However, I believed that developers would bloom in
a Scrum environment. Stifled and choked by waterfall, developers would stand tall,
employing development practices, collaboration, and tooling that nobody had time to
use in waterfall projects.
PCs All-in-One Desk Reference For Dummies
What’s the definition of a reference book? Well, I like to think of this
book as a snapshot. Sure, it’s a very heavy photograph, weighing in
at over 700 pages — but nevertheless, it captures the current state of
today’s PCs, including hardware, the most popular applications, and of
course, the latest and...
Becoming Immortal: Combining Cloning and Stem-Cell Therapy
Expecting to relax during a routine flight home, I casually glanced through
the contents of the airline’s magazine and practically suffered a heart attack.
The first feature article was entitled, “How to Live Forever”! Believing for
a moment that Becoming Immortal had been scooped, I tore through the
magazine... Enterprise Service Computing: From Concept to Deployment
The developed economy is shifting from being manufacturing based to services based. Different from the traditional manufacturing business, the services business is more complicated and dynamic, and end-user driven rather than product driven. To stay competitive, an enterprise thus has to rethink its business strategies and revamp its...
Embedded Software: The Works "This one book has an amazing breadth of coverage, undertaking all the key subjects embedded engineers need to understand in order to succeed." - eg3.com, November 2005
Embedded software needs have grown exponentially over the past quarter century. In 1975 writing 10,000 lines of assembly code was a considered a...