Hearpreneur

AUGUST 20, 2024

Use Agile Practices: Adopting agile methodologies has promoted faster development and ongoing innovation at both my companies. It sounds silly, but this is what the root of our company is about because myself and my co-founder thrive in these sorts of spaces. Thanks to Moxin Reza, Investor Partner Group ! #4-

Entrepreneur 139

Entrepreneur Technical Review Operations Cofounder 139

Steve Blank

JULY 29, 2013

There’s been a lot written about the individual characteristics of what makes a great founder , but a lot less about what makes a great founding team and how that’s different from a great founding CEO. In doing so we’ve failed to help founders understand what it takes to build a great founding team. Founders – the idea.

Cofounder 335

Cofounder Advisory Board Customer Development Leadership 335

Steve Blank

AUGUST 27, 2012

What I saw reminded me of some of the best and worst things I did as a founder. We’re building the wrong product!” Tossing their agile development process and at times their entire business model in the air, the company would go into fire-drill mode and engineering would start working on whatever his latest insight was.

Founder 323

Founder Cofounder Advisory Board Burn Rate 323

Up and Running

MAY 23, 2016

“If you can fix a problem for someone and do it better, quicker, and/or cheaper than your competitor, you’re off to a good start.” – Gabriel Kuperman, founder and CEO of CuePin. We created UpKeep to fill this void—a cloud-based solution that was affordable for any size business.” – Ryan Chan, founder of UpKeep.

Software Review 74

Software Review Software Delaware Forecast 74

YoungUpstarts

MAY 3, 2013

by Mike Broderick, co-founder and CEO of Turning Technologies. In addition to giving our customers the power to generate and aggregate audience response data in real time, Turning Technologies has been able to collect and use customer feedback to hone our product development efforts. They are correct.

Cofounder 230

Cofounder Entrepreneur Ohio Aggregator 230

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

Austin Startup

MARCH 5, 2019

Boost Biomes CEO and co-founder Jamie Bacher The Forrest Four-Cast: March 5, 2019 Fifty diverse startups will aim to impress a panel of judges and a live audience with their skills, creativity and innovation at SXSW Pitch Presented by Cyndx. The biggest challenges have generally been around product development in a biotech product.

Technical Review 48

Technical Review Harvest Startup San Francisco 48

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

ReadWriteStart

JUNE 20, 2012

Customer discovery turns founders’ initial hypotheses about their market and customers into facts. These visionary customers will give the company the feedback necessary to add features to the product over time. Enthusiasts who spread the good news about your product to friends, family or co-workers are often called evangelists.

Customer 119

Customer Advisory Board Cofounder Engineer 119

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 6, 2011

The finished book will come out on September 13, featuring an amazing cover designed by my IMVU co-founder Marcus Gosling and refined and tested by so many of you. It enables a company to shift directions with agility, altering plans inch by inch, minute by minute. them back to my publisher. I am incredibly proud of the result.

Lean 167

Lean Startup Metrics Private Equity 167

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. 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.

San Francisco 146

San Francisco Lean Agile Java 146

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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

He blogs to 10,000 web entrepreneurs at Software by Rob and co-hosts the podcast Startups for the Rest of Us. A virtual assistant (VA) is a remote worker hired to complete tasks you should not be doing as the founder of a startup. Agile Development, meet Agile Business. After your product launch.

Software Review 284

Software Review Startup Technical Review Hosting 284

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. October 13, 2008 6:47 PM Luke G said. Eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Labels: product development 15comments: mukund said. I always assumed I wouldnt manage anybody.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Thats why its so essential to have a co-equal problem team.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 1, 2009

For startups that are tempted to mimic this behavior, I suggest reading the great account of the early Apple in Founders at Work.) Also SJ's obsession with better taste (positively) contributes to the overall product development process. Regardless, they must cull a lot of bad ideas for every one that we hear about.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. We didnt even practice TDD across our whole team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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

Startup Lessons Learned

NOVEMBER 7, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

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

FEBRUARY 22, 2010

One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Our mystery keynote is now revealed and I couldnt be more excited. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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

OCTOBER 5, 2009

In other words, a principled way to combine agility with stability. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. In other words, a principled way to combine agility with stability. Expo SF (May.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133