Continuous Deployment Engineer Product Development SEM 
Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.
Startup Lessons Learned
SEPTEMBER 22, 2008
I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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
SEPTEMBER 2, 2008
Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. and more ► January (6) Lo, my 18891 subscribers, who are you?
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 30, 2008
So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.
Startup Lessons Learned
SEPTEMBER 2, 2008
Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Case Study: Continuous deployment makes releases n.
Expert insights. Personalized for you.
131 
Let's personalize your content