article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

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.

article thumbnail

Case Study: Lean UX at work

Startup Lessons Learned

This article is a guest post by Jeff Gothelf, Director of User Experience at TheLadders in New York City. Jeff has been promoting the use of Lean UX as an effective method to spur greater innovation, quality and productivity in startups as well as within teams in larger organizations.

Lean 165
Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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.

Agile 111
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

In recent years, weve also got great new options all up and down the stack, in particular things like Amazon EC2 and RightScale (none of which would be possible without the free software movement). The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development.

Lean 168
article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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. I think the new question needs to be "does the team have a clear objective?"

article thumbnail

Lessons Learned: ScienceDaily: Corporate culture is most important.

Startup Lessons Learned

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.

article thumbnail

Behind Every Great Product

SVPG

Article: Behind Every Great Product. I titled the paper, “Behind Every Great Product” and it was inspired by the classic Good Product Manager / Bad Product Manager by Ben Horowitz. The paper proved popular and helped many teams to get a better understanding of just what product was all about.

Product 60