Startup Lessons Learned
MAY 19, 2011
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.
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
DECEMBER 6, 2008
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.
Startup Lessons Learned
OCTOBER 5, 2008
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.
Startup Lessons Learned
SEPTEMBER 15, 2008
I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. The wise entrepreneur will take this advice seriously in order to distill his ideas down to their essence. No more, no less. September 15, 2008 9:19 PM James said. April 27, 2009 8:59 AM Anonymoussaid.
Startup Lessons Learned
SEPTEMBER 10, 2008
There are several ways to make progress evident - the Scrum team model is my current favorite. I think the new question needs to be "does the team have a clear objective?" 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.
Startup Lessons Learned
SEPTEMBER 22, 2008
Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. And wait until you see a "non-technical" designer writing simple code to try and speed up a release.
Expert insights. Personalized for you.
165 
Let's personalize your content