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
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.
In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. But, over the years I’ve realized that the toughest problem - the one that matters most and was consistently the most challenging - was figuring out what the product backlog should be.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. No more, no less.
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuousdeployment, see Just-in-time Scalability.
But that team may also include product marketers or other in-house customers who can give insight into the impact that solution trade-offs might have on customers. Its not good enough to hit product milestones and conduct usability tests. dalelarson : "Metrics are people, too." Register here. May 29 - the Lean Startup Workshop.
Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Unfortunately, customers hated that initial product.
Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.
Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. Case Study: Continuousdeployment makes releases n. Take a look and let me know what you think.
I believe its important that product teams be cross-functional, no matter what other job function the product champion does. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. about what their function needs to do to fully support the product.
I have written recently about how product teams do product discovery in parallel with product delivery. I have also written about how teams sometimes like to time-box their product discovery work. Continuous Delivery is an increasingly popular notion today. Nearly all product teams today do continuous build.
I think today that one of my most useful skills is that after 30 years of working with technology product teams, I am pretty good at spotting talent and potential. I love seeing them creating exceptional products, and leading great organizations of their own. I believe in continuous improvement. I believe in giving back.
We organize all of the trending information in your field so you don't have to. Join 5,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