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). Read the rest.

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

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. February 9, 2009 7:45 PM Joseph Flahiff said.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 30, 2008

What does your Chief Technology Officer do all day? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Just what is the CTO supposed to do?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Very few startups fail for lack of technology.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

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. Were a software company, so what we do everyday is turn ideas into code. Labels: agile , listening to customers 3comments: hauteroute said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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." You can tell a lot about a company from their deployment flow. I havent met anyone who would do a day-long deployment every day. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

YoungUpstarts

APRIL 25, 2019

Adding the right tools and automation, teams can design, test, build, and deploy software more agilely. An integrated workflow supports rapid deployment and flexible workflows. There are plenty of open source software and commercial software solutions that DevOps teams are using to accelerate app development.

Java 127

Java XML Open Source Continuous Deployment 127

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. 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.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Case Study: Continuous deployment makes releases n. Its this second point I want to emphasize. Expo SF (May. Expo (and a call for he.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

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. . Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

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. Case Study: Continuous deployment makes releases n. But Seth Godin is a great writer, so I dont see why I cant crib from him whenever. Expo SF (May.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

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. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 18, 2008

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. The webcast is free with registration and will include a live Q&A with attendees. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

AUGUST 8, 2009

Each company would enroll two leaders in the series, one on the technology side, one on the business side. In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. . Case Study: Continuous deployment makes releases n. Expo SF (May.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 11, 2009

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?) Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Case Study: Continuous deployment makes releases n. Thank you. August 13, 2009 3:43 AM Robert said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

OnlyOnce

AUGUST 6, 2015

If your organization still does software development through a waterfall process or has separate and distinct development, QA, and IT/Operations teams, I’d say you should run, not walk, to get this book. It just uses storytelling techniques to make its points and give color and examples for more memorable learning.

Phoenix 48

Phoenix Continuous Deployment Agile Software Developers 48

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. We need to work hard, as previous generations did, to balance the needs of everyone in our ecosystem.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

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. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 19, 2008

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. Case Study: Continuous deployment makes releases n. Expo SF (May.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. Any advice? Excellent post. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

AUGUST 1, 2009

We might be a ways away from the reality of a Chief Engineer or Product Director role commonly in software development, but ultimately it's going to be a matter of getting the culture right so that people stick around long enough to develop not only the tactical skills, but also the honed instincts and senses. Expo SF (May.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. Thats the ultimate task for the companys technology leadership. Hire a CTO or VP Engineering. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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. So should copyrights and patents on software code.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

For example, trying to make server software more scalable. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. When we started IMVU in 2004, we could rely on a staggering amount of open source software that jumpstarted our initial product offering. As always, Paul is right. Nice article. Expo SF (May.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Mission synchronization If an organization is changing on a daily basis how is it that it doesnt look "erratic" yet feels "agile." Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84