Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

YoungUpstarts

APRIL 21, 2013

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Customer development (the understanding of customer needs) must be married to agile development (a process which drives waste out of product development).

Lean 193

Lean Technical Review North America Startup 193

YoungUpstarts

MARCH 12, 2020

One of the major benefits of using a SOM approach is that product development costs are drastically decreased and technical risk is also reduced. Other advantages of production-ready SOMs include more CPU choices and a smaller footprint. Use Product differentiation If You’re Small.

SCRUM 147

SCRUM Software Review Technical Review Differentiation 147

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Labels: product development 15comments: mukund said. But a good day looked like this.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

The Next Web

MARCH 6, 2014

Successful collaboration between a company’s business development and product development requires mutual understanding and purpose. Practice Agile Development. Matt Ehrlichman , Porch. Consider Using a Liaison. Make an effort to share the reasons and motives of each side with the other. Andrew Thomas , SkyBell.

Technical Review 129

Technical Review Development Team Review Developer Agile 129

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. Joel said it: "Top notch development teams dont torture their programmers."

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

NOVEMBER 8, 2008

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Steve Blank

MAY 6, 2015

Waterfall Development. While it sounds simple , the Build Measure Learn approach to product development is a radical improvement over the traditional Waterfall model used throughout the 20 th century to build and ship products. cost structure resulting from the business model. Lessons Learned.

Lean 120

Lean Agile Business Model Customer Development 120

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. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

Ideally, by the time I code it up, we'll have many customers using the platform which means I'll be working on a product I know is viable, and that's paying for the time I'm spending to automate it. Agile Development, meet Agile Business. After your product launch. Point #1: Developing a Proof of Concept.

Software Review 284

Software Review Startup Technical Review Hosting 284

ReadWriteStart

MAY 26, 2022

If you’re not already, adopt an agile methodology not only for software development, but also for communication improvements. There’s a reason 70% of all acquisitions fail : When leaders feel pressure to grow for growth’s sake, their focus on results (no matter the cost) isn’t sustainable in the long run.

Software 171

Software Japan Agile Employee 171

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

The Startup Magazine

JUNE 4, 2024

Investment in Growth: Allocate funds strategically to areas that promote growth, such as marketing, product development, and talent acquisition. Cost Control: Implement cost-saving measures without compromising on quality or customer experience. These channels offer cost-effective ways to engage with customers.

Technical Review 146

Technical Review Agile Audience Employee 146

Startup Lessons Learned

NOVEMBER 13, 2008

This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Id like to point out something else about the example above. Five whys helps us keep our cool.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market. Agile software development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MARCH 27, 2009

While some cost-cutting measures reduce that number, others increase it. In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Otherwise, cutting costs just leads to going out of business a little slower. Getting started with split-testing and the one-line split-test.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 13, 2008

We ran ad campaigns against every single product we could think of in an adjacent market space to ours. Since we were only paying per click, it didnt cost us anything to cast a wide net. We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JUNE 15, 2009

In practice, how developers respond to this dilemma is determined by their incentives, which are driven by the culture of their team. Who will ultimately bear the cost of their mistakes? One of the distinctions that has helped at the executive level is to stress that you're reducing the COST of failure, rather then its PROBABILITY.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

The Startup Magazine

SEPTEMBER 20, 2019

In the past, it has been incredibly challenging to determine what customers really want from a business or the products or services they purchase. However, there is no better source than the actual customer using the product in the present. Agility, Adaptiveness, and Responsiveness. Let’s dive deeper. To Round It Up.

Software Review 125

Software Review Management Early Stage Startup 125

YoungUpstarts

JULY 30, 2019

This solution is a philosophy, and this philosophy is AGILE. Agile is a manifesto that has been put forth by a bunch of people and to implement it. As its official website suggests, it is a better way of building products. Moreover, scrum and agile aren’t the same thing. We use SCRUM. Why SCRUM for startups?

SCRUM 113

SCRUM Software Review Hiring Agile 113

Startup Lessons Learned

JULY 2, 2009

Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Remember that the cost of the solutions is proportional to the problem caused. In fact, even the investigation itself is considered too much work.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

ConversionXL

OCTOBER 7, 2021

However, on a more granular graph, the introduction phase would be preceded by a product development stage. This stage is used to determine the viability of your product and confirm when it should go to market. Therefore, marketing strategies revolve around product price and promotion, with four possible options: 1.

Product 142

Product Marketing Software Review Social Media 142

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. In this post I want to talk about the nuts and bolts of how to integrate continuous integration into your team, and how to use it to create two important feedback loops. Expo SF (May.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. For me, it's a live example of agile and sustainable business. It cuts production time and costs in half without compromising functionality or style. Thanks to Christina Giaquinto, Modular Closets !

Technical Review 139

Technical Review Entrepreneur Software Review SEO 139

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Sure, it seems efficient. Expo SF (May.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The result is a profound democratization of the digital means of production. [.] We will not lose on their products -- after all, most of them are global.

San Francisco 121

San Francisco Indiana Lean Startup 121

ConversionXL

SEPTEMBER 5, 2019

The first, according to Dr. David Travis at UserFocus , was agile development : Dr. David Travis: “‘Development’ teams morphed into ‘design’ teams. To use the agile terminology, design teams wanted to get a ‘shared understanding’ of their users and they were suspicious of any attempt to set requirements in concrete.”.

Software Review 115

Software Review Design Agile Analytics 115

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. I’ve met a lot of gatekeepers in the past few months. Is that a lot? Is that good? ideas (e.g.

San Francisco 113

San Francisco Lean Technical Review Distribution 113