Remove 2010 Remove Agile Remove Software Development Remove System Design
article thumbnail

Don’t Separate Design from Implementation

LeanEssays

If detailed requirements are actually design, if features and functions are design, if stories are design, then perhaps we should re-think who is responsible for this design. All too often, detailed requirements lists and backlogs of stories are actually bad system design done by amateurs.

article thumbnail

Friction

LeanEssays

In fact, when software development is done right, speed, quality and low cost are fully compatible. Hundreds of enterprises, including Amazon and Google (whose systems manage billions of dollars of revenue every month), have demonstrated that the safest approach to software development is automated, it is adaptive, and it is fast.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lean Software Development: The Backstory

LeanEssays

The second book summarizes the essence of lean product development this way: Understand that knowledge creation is the essential work of product development. Charter a team of responsible experts led by an entrepreneurial system designer. Manage product development using the principles of cadence, flow, and pull.

article thumbnail

Grown-Up Lean

LeanEssays

See How Google Tests Software , [7] by James Whittaker, Jason Arbon, and Jeff Carollo for more information. The Lean Approach to Software It’s hard to count the many times that someone told me “software development is not like manufacturing.” A production view of software development is fundamentally flawed.