Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. We picked those numbers by counting up the numbers of friends, family, and relatives we thought we could cajole into buying our early product.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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

Up and Running

JULY 26, 2016

Just for reference, Slidebean is a SaaS presentation software where users can add content, and a finished presentation is designed automatically. 1x hacker in charge of product/development. 1x hipster working with both product and growth. Nov-15: Graphic Designer (growth/product). What do they do?

Revenue 60

Revenue Acquisition Channel Campaign 60

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

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

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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

SEPTEMBER 22, 2008

My favorite instance of this is scheduling software. Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. And wait until you see a "non-technical" designer writing simple code to try and speed up a release.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 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. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

MARCH 13, 2009

In some businesses, especially in certain industries like traditional enterprise software, you simply cannot bring a new product to market on your own. You need to combine your product with others, and this requires partners like OEMs or system integrators. So dont combine your product launch with a marketing launch.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

OCTOBER 7, 2008

Take a look at The App Store after the gold rush - FierceDeveloper : According to a recent BusinessWeek feature , the flood of new games, productivity tools and related iPhone software is making it difficult for the vast majority of apps to crack the consumer consciousness. Acqusition competition is how new apps get new customers.

San Francisco 68

San Francisco Lean Retention SEM 68