Cofounder Design San Francisco SCRUM 
Startup Lessons Learned
DECEMBER 14, 2017
Guest Post by Misti Yang, Writer for Lean Startup Co. Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Second, don’t simply hire your buddies. It's amazing.”
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
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. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. April 23, 2010 in San Francisco. No more, no less. September 15, 2008 9:19 PM James said.
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
APRIL 9, 2009
And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. When people ask about how to reconcile metrics with interaction design, usability testing, or in-person customer interviews, this is the issue they are really talking about. Excellent post.
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
SEPTEMBER 10, 2008
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. April 23, 2010 in San Francisco. When its receding, we rescope.
Expert insights. Personalized for you.
245 
Let's personalize your content