Remove Agile Remove Design Remove New York 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.

Agile 111
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 will also be joining us on stage at Startup Lessons Learned 2011 , where he will be presenting a case study on his experience blending design, Lean Startup, and large company culture.

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: 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. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168
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. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

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. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?