Remove 2006 Remove Continuous Integration Remove Product Management
article thumbnail

AoAD2 Chapter 2: Why Agile?

James Shore

In addition, emphasizing productivity might encourage your teams to take shortcuts and be less rigorous in their work, which could actually harm productivity. 1 See, for example, [Van Schooenderwoert 2006], [Mah 2006], and [Anderson 2006]. Users, stakeholders, domain experts, and product managers.

Agile 59
article thumbnail

AoAD2 Practice: Whole Team

James Shore

Customer skills fall in to several categories, as follows: Product management (aka product ownership). Product management involves managing all aspects of a product’s lifecycle, from the initial business case all the way to product launch and beyond. Iteration Demo. Real Customer Involvement.

Insiders

Sign Up for our Newsletter

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

article thumbnail

The Best Product Engineering Org in the World

James Shore

They also love test-driven development, pairing, continuous integration, and evolutionary design. CIO Magazine, Sep 2006 One of my favorite stories about how this approach fails is the FBIs Virtual Case File system, because there was a US Senate investigation, and we have a lot of details about what happened. for most companies.

article thumbnail

Lean Software Development: The Backstory

LeanEssays

This group has published numerous books and articles on lean thinking, lean manufacturing, and lean product development, including The Toyota Product Development System (Morgan and Liker, 2006), and Lean Product and Process Development (Ward, 2007). Put the tests into a test harness for ongoing code verification.