Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. They just assumed it was the way software companies worked. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Were a software company, so what we do everyday is turn ideas into code.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 4, 2008

As Ive written previously , lean startups are built upon three main trends: Technology commoditization. It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO).

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." How long does the software sit un-deployed? Software is generally always getting better or getting worse. How fast do they iterate? Does it require weeks of QA?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. For software, we have many - you can enjoy a nice long list on Wikipedia. Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. Hey Someone else who is extending the agile/lean approach beyond just developing software. Labels: events 2comments: Andrew Meyer said.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

MAY 27, 2009

Im going to be speaking on June 3rd at an event sponsored by the Technology Entrepreneurs Exchange (TeXchange), "the premier networking organization in Texas for business executives and entrepreneurs to meet, exchange ideas and share experiences." It uses principles of agile software development, open source and web 2.0,

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 29, 2009

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. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) I’ve been in the software industry for a long time. Thoughts on scientific product development Lo, my 5 subscribers, who are you? That’s all fine and dandy. Is that mass all that critical?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Here in Tampa, our biggest challenge is convincing the regions technology "leadership" that grassroots economic development is a good thing. January 2, 2009 11:54 AM Daniel Davie said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. There are too many products clamoring for attention. I’ve met a lot of gatekeepers in the past few months.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

SEPTEMBER 18, 2008

Its enourmously helpful when you need to generate new ideas about what to do, or when you face a product problem you dont know how to solve. For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. Seth Godin: How often should you publish?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

AUGUST 20, 2009

Heres the excerpt: Today’s high-tech entrepreneurs have at their command more than just the ability to invent new technologies — they have mastered the discipline and the methodology required to harness those technologies in order to serve customers. Revisiting the Software Design Manifesto (and what.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 11, 2008

Its an academic treatise that tries to answer a seemingly straightforward question: after World War II, why did Silicon Valley become the undisputed leader of the technology world, while Bostons Route 128 corridor did not. Worldwide developments based on this research led to modern radio communication, television, and the electronics age.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Every single great Apple product on the market today is not something incredibly innovative. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

AUGUST 8, 2009

Heres the pitch: a group of 10 companies would meet once a month for six months to develop their capacity to run lean. Each company would enroll two leaders in the series, one on the technology side, one on the business side. Revisiting the Software Design Manifesto (and what. Take a look and let me know what you think.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Brands are so pervasive that even those people who want to make a statement against it (do you build all your own software from source?) have to invest substantial time avoiding it, which is just another kind of premium. Expo (and a call for he.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

VC Cafe

NOVEMBER 11, 2011

ARRIS, headquartered in Suwanee, Georgia, USA, specializes in the design, engineering and supply of technology supporting triple- and quad-play broadband services for residential and business customers around the world. The approved projects involve innovations in the areas of life sciences, healthcare IT, electronics, software and energy.

Peru 96

Peru Technical Review North America 96

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. A really good technology executive can notice problems like the ones Im talking about today and address them proactively. At the end of the day, the product development team of a startup (large or small) is a service organization.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 19, 2008

This wasnt an education product - it was a pretty surprising group to find using it. What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. Thirdly, revamp how intellectual property rights are applied to software and code. September 10, 2009 4:37 AM Dale B.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

FEBRUARY 22, 2010

Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. Accurate - if youve ever been managed by task-tracking software, youll relate to the feeling that you either have to spend ludicrous amounts of time posting updates or the information goes stale. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

mashable.com

SEPTEMBER 12, 2011

After all, high-quality open source software is free, the cloud makes computer power far less expensive, and anyone with an Internet connection can learn Ruby and CSS. For example, my company decided early on to hire a UI designer, which has helped tremendously with our product development. Publisher Platform (P3). startupcto

Startup 79

Startup Social Media RSS Social Network 79

mashable.com

MARCH 7, 2011

Billion View Comments How HTML5 Is Aiding in Cross-Platform Development February 22, 2011 by Christina Warren View Comments email share email share The Mobile App Trends Series is sponsored by Sourcebits , a leading product developer for mobile platforms. Follow Sourcebits on Twitter for recent news and updates. Let us know.

Developer 93

Developer HTML API Ruby 93

VC Cafe

JULY 2, 2012

has acquired Israeli face recognition technology developer Face.com for $100 million. The two companies have collaborated for a long time, with Facebook using Face.com’s technology to help users tag the faces of friends in pictures they upload on the social network with Face.com’s Photo Tagger service. Facebook Inc.

Latvia 109

Latvia Lithuania Russia 109

techcrunch.com

OCTOBER 23, 2010

Tech Gadgets Mobile Enterprise GreenTech CrunchBase TechCrunch TV Disrupt SF More TechCrunch TV Beta Invites Crunchies Elevator Pitches Gillmor Gang Podcasts TechCrunch Europe TechCrunch Trends TechCrunch France TechCrunch Japan Whats Hot: Android Apple Facebook Google Microsoft Twitter Yahoo Zynga Subscribe: From Nothing To Something.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84