Engineer Management Product Development 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. Frustration is mounting.
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. Its by far the hardest part of the puzzle of shipping successful products and both recommend that you get a customer in the room and ask them to clarify what they want as you go. Labels: customer development , product development 8comments: Sarah Milstein said.
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. Please leave feedback!) Do you fix bugs before writing code?
Startup Lessons Learned
SEPTEMBER 15, 2008
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. 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.
Startup Lessons Learned
JULY 29, 2009
The human tendency to moralize about debt affects engineers, too. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants.
Startup Lessons Learned
NOVEMBER 18, 2008
Its even more critical in lean startups when they need to manage growth. I believe its important that product teams be cross-functional, no matter what other job function the product champion does. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner.
ctotodevelopers.blogspot.com
JULY 11, 2012
I cover several topics including agile software development, software startups, web 2.0, social networking, SaaS, content management, media, enterprise 2.0 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.
Expert insights. Personalized for you.
158 
Let's personalize your content