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
SEPTEMBER 15, 2008
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
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.
Startup Lessons Learned
OCTOBER 5, 2008
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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Frustration is mounting.
Startup Lessons Learned
NOVEMBER 18, 2008
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.
Startup Lessons Learned
JULY 29, 2009
The human tendency to moralize about debt affects engineers, too. This reverses the standard intuition about what engineering activities add value, which usually concludes that test coverage is a form of necessary waste but a refactoring is value-added work. These kinds of design are mostly orthogonal.
ctotodevelopers.blogspot.com
JULY 11, 2012
The implementation and architecture can also suffer if the team under or over invests engineering time, implementation of standards, or testing discipline in the wrong areas. ► 2010. (14). No Scrum Master? This, in some way, is a byproduct of self organization. ► March. (1). Agile Process Improvement Using.
Expert insights. Personalized for you.
111 
Let's personalize your content