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. TheLadders is an eight-year-old company based out of New York City focusing on the $100k+ employment market (both jobseekers and recruiters). Levels of Agile adoption span the full spectrum across our 6 Scrum teams.
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.
Gust
AUGUST 22, 2012
English has become the lingua franca for doing business, while the technical jargon is as familiar (or cryptic) in Alexandria as in Mountain View: Scrum, sprints, Git, Cassandra, Hadoop. Yet in an increasingly globalized, diverse, interconnected world, it would be a mistake to assume that the same players can dominate in all markets.
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.
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 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.
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.
Expert insights. Personalized for you.
165 
Let's personalize your content