article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

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.

Agile 111
article thumbnail

Lightspeed is growing our Consumer Investing team

Lightspeed Venture Partners

Since then, as a team, we’ve been fortunate enough to invest behind the vision of the founders of some tremendous consumer companies across messaging, social media, e-commerce, Internet of Things, marketplaces and gaming. Today, I’m even more thrilled as we have added two new people to our consumer team.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Sprint Like An Egyptian: A Tech Entrepreneurship Revolution in Alexandria

Gust

Internet connectivity is still sparse but mobile phones are everywhere, with major players and familiar brands aggressively pursuing new markets. Perhaps most importantly, IT and Internet business are simply a breed of their own. Silicon Arabia has engineers in Russia as well as Egypt.)

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. No more, no less.

Lean 168
article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. There are several ways to make progress evident - the Scrum team model is my current favorite. At IMVU, our rule was that a new engineer needed to push code to production on their first day.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Each iteration takes longer than the previous one. Frustration is mounting.

article thumbnail

Lessons Learned: ScienceDaily: Corporate culture is most important.

Startup Lessons Learned

At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Thus the power of the Chief Engineer is very large even though he (and they are all men so far) has no direct reports other than a secretary and a few assistants who are themselves being trained to be chief engineers.