Continuous Deployment Engineer Management SCRUM 
Startup Lessons Learned
OCTOBER 5, 2008
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.
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.
Startup Lessons Learned
SEPTEMBER 10, 2008
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.
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. Very useful perspective - as a first-time CEO managing a small startup, these ideas are timely and thought-provoking. Less is more. No more, no less.
Startup Lessons Learned
NOVEMBER 18, 2008
Its even more critical in lean startups when they need to manage growth. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Once an agreement is reached, the Chief Engineer continually watches to make sure that the functions are following through.
Startup Lessons Learned
JULY 29, 2009
We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. It is so true, but non-tech managers usually try to ignore the facts away. One last thought.
Startup Lessons Learned
APRIL 9, 2009
No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."
Expert insights. Personalized for you.
158 
Let's personalize your content