Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. The lean startup is an application of Lean Thinking. No more, no less.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

YoungUpstarts

JULY 16, 2019

Have you developed any vision of a product development strategy? And keep in mind that the best option is to develop at least 5 domain names connected to your brand’s name to find an unoccupied domain. Junior engineers cannot deliver a high-quality product. After the production stage, the maintenance period begins.

eCommerce 113

eCommerce Software Developers Software Development Hosting 113

YoungUpstarts

AUGUST 2, 2016

Product managers should also understand the company’s goals. It is one of the most important processes in a product development lifecycle to deliver the product. The product itself can be ideal and work faultlessly, but what really matters is how it enters the market. necessary product. necessary product.

Management 100

Management Product Churn Rate Green 100

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. No vanity metrics should be looked at. No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.

Lean 167

Lean Startup Software Engineering Agile 167

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Professionals Musings

SEPTEMBER 14, 2016

Cash flow is a basic survival metric for every startup. For example, a software development startup raising $250,000 from angel investors better be able to operate on $25,000 per month. This could equate to two technical founders (with a minimal salary), funding two developers for a year.

Burn Rate 120

Burn Rate Hockey Stick Startup Salary 120

ConversionXL

SEPTEMBER 6, 2013

So What is Customer Development? Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process. The core idea behind customer development is that the assumptions you make about a target market are only guesses.

Customer Development 126

Customer Development Conversion Developer Customer 126

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. What causes projects like this to fail in traditional software development is that the solution is unknown. What do you do if the problem itself is unknown?

Agile 111

Agile Customer Development Developer San Francisco 111

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. I used to think that investments in metrics were a form of waste. Labels: product development 4comments: Doug said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? It would be hard to argue against this product development strategy, in general. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

NOVEMBER 4, 2008

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). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

crowdSPRING Blog

OCTOBER 20, 2010

Why marketer misuse of metrics may be an addressable cultural issue – [link]. Legal Contracts for Software Developers Who Hate Contracts (w/free contract template tco use today) – [link]. Amazon’s Approach to Product Development – [link]. 65 Creative Pumpkin Carving Designs – [link].

Social Media 91

Social Media Small Business Design Media 91

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. Does this sound familiar?

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

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." Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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

Women Entrepreneurs Can

OCTOBER 19, 2021

Software development comes with several challenges, huge risks, and a lot of responsibility, which is why there is still a high failure rate amongst many modern software startups. However, if you want your startup to be successful, there are a few important factors that you need to consider.

Software 59

Software Software Developers Software Development Hiring 59

Startup Lessons Learned

JUNE 15, 2009

Why do software developers think this is acceptable? Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. June 22, 2009 10:07 AM Khris said. I should think not. June 24, 2009 8:24 PM Trent Larson said.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23.

Lean 68

Lean San Francisco Web Advisory Board 68

Software By Rob

NOVEMBER 16, 2009

Geoffrey Moore Author of Crossing the Chasm and four other books, Geoffrey Moore has been thinking about high-tech product development longer than most of have been doing anything on a computer. Give your user a better experience out of the box, as they are learning, and once they are experts with your product.

Software Review 47

Software Review Software San Francisco RSS 47

ctotodevelopers.blogspot.com

JULY 11, 2012

I cover several topics including agile software development, software startups, web 2.0, decide on success metrics, measure, and then decide if additional investment is warranted. If the innovation is successful, then the metrics should help drive the enhancement into the top/right "agile happy place" quadrant.

Agile 40

Agile Architecture Offshore Software Developers 40

conversionxl.com

SEPTEMBER 10, 2013

So What is Customer Development? Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process. The core idea behind customer development is that the assumptions you make about a target market are only guesses.

Customer Development 60

Customer Development Conversion Developer Customer 60

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Startup Lessons Learned - the Conference (April 23.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

mashable.com

MAY 24, 2011

May 23, 2011 by Christina Warren 20 Share on Tumblr email share Share on Tumblr email share The Mobile App Trends Series is supported by Sourcebits , a leading product developer for mobile platforms. Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms.

Mobile 90

Mobile Web Social Media Software Review 90

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

maplebutter.com

JANUARY 8, 2013

Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Product 2. Building Metrics / Usage Reports / KPI 3. Product/Metrics (70%/30% time) * Get your product activation (sign-up + meaningful action) to 60% * then, Get your product retention to 20% weekly.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79