Remove Customer Development Remove Design Remove SCRUM
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

The Lean LaunchPad Goes to Middle School

Steve Blank

By Tuesday morning, students fleshed out what they believed to be their value proposition and customer segments. Scrum boards went up detailing everything they needed to accomplish by Friday afternoon. Tuesday afternoon they got out of the building and headed to a local mall to begin the customer validation and development process.

Lean 312
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: 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
article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

To begin with, see if you can get designers, programmers, and QA on the same team together. The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. At IMVU, we found 60 days was just about right.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

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. When its receding, we rescope. Do you have a spec? Do you do hallway usability testing?