This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
We use Extreme Programming as our model of how to develop software. They also love test-drivendevelopment, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. This is what test-drivendevelopment is all about, and its an amazing way to work.
Customer skills fall in to several categories, as follows: Productmanagement (aka product ownership). Productmanagement 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.
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 productmanagers.
Coffin 2006] describes an experience with two nearly identical teams: one that didn’t include users’ perspective and one that did. An Optimizing team needs business expertise, but they don’t necessarily need a traditional productmanager. If you can’t get the business, customer, or user expertise you need.
This group has published numerous books and articles on lean thinking, lean manufacturing, and lean productdevelopment, including The Toyota ProductDevelopment System (Morgan and Liker, 2006), and Lean Product and Process Development (Ward, 2007). and James E. Heppelmann.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content