Remove Agile 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. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully. Enter Jims post.

Agile 111
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

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

Startup Lessons Learned

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better.

article thumbnail

Embrace technical debt

Startup Lessons Learned

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

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

This I Believe

SVPG

While I am currently a passionate advocate of methodologies like Agile, Lean, Design Thinking, Customer Development and more, I try very hard not to get too attached to, or to be too closely associated with, any particular school of thought or technique. Then of the people and teams I work with. Or Six Sigma.

SCRUM 60