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. Ive had at least three conversations this week about the relationship between agile methodologies and customer development. Just a thought.
Startup Lessons Learned
MAY 25, 2020
The stories he told me during our conversation, somber as they are, show the truth of that belief. You can listen to our conversation on Apple podcasts , Google podcasts , or wherever you like to download. Here's my conversation with Carl Liebert. He shared his reflections on why these approaches work.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JULY 29, 2009
Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. " And, as I tried to outline in the article, process improvements that reduce overall batch size might be a better choice. July 30, 2009 1:29 PM jkorotney said. Things like "where is the design time?"
Startup Lessons Learned
DECEMBER 6, 2008
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. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. At IMVU, we found 60 days was just about right.
A Smart Bear: Startups and Marketing for Geeks
OCTOBER 24, 2011
” Introduced a few months ago as an Austin event, I’m now doing this live audio advice column to the web, taking phone calls from startups around the country. So be sure to make a free user account and participate in the offline conversation there. Which is similar, it has less of a SCRUM-my feel to it.
Expert insights. Personalized for you.
111 
Let's personalize your content