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.
Startup Lessons Learned
MAY 25, 2020
13:58) Advice for companies who think it's too late to start looking for new ways to operate, including some examples from Austin, Texas. (15:55) So now I'm home-based in Austin, Texas and I'm spending a lot of time with a lot of startups and a lot of CEOs that are trying to scale their companies.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
DECEMBER 6, 2008
For starters, theres whole volumes that need to be written about how to actually find and hire the people your startup needs. But most startups succeed in hiring, one way or another, and are still left with the problems of organizing the people that rapid growth brings in. At IMVU, we found 60 days was just about right.
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
APRIL 9, 2009
Looks like Ill be at TiEcon 2009 in mid-may, and at an event to be announced in Austin in early June. I have been using various forms of Agile development -- mainly XP and Scrum -- for many years, but only recently came across "customer development" which makes a whole lot of sense to me. Labels: slides 7comments: Hazem Awad said.
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. When its receding, we rescope. Do you have a spec?
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. We had all the tools in place but we didn’t actually practice agile development.
Expert insights. Personalized for you.
111 
Let's personalize your content