article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. 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.

Agile 111
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168
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: A new version of the Joel Test (draft)

Startup Lessons Learned

There are several ways to make progress evident - the Scrum team model is my current favorite. If you have a true cross-functional team, empowered (a la Scrum) to do whatever it takes to succeed its likely they will converge on the result quickly. There are no customers for that feature, UI issues or no. Do you have a spec?

article thumbnail

Developing Strong Product Owners

SVPG

Knowledge: User/Customer Knowledge (10) - Is the product owner the company acknowledge expert on his target users/customer? Process Skills: Customer Discovery Process (7) - Customer discovery includes customer interviewing skills, opportunity assessments and understanding of customer development programs.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

article thumbnail

Lessons Learned: ScienceDaily: Corporate culture is most important.

Startup Lessons Learned

At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? What is customer development? No departments The Five Whys for Startups (for Harvard Business R.

article thumbnail

Embrace technical debt

Startup Lessons Learned

Unfortunately, customers hated that initial product. For example, at a previous virtual world company , we spent years developing an architecture to cope with millions of simultaneous users. Leverage product development with open source and third parties. How likely will customers ultimately use that feature?