YoungUpstarts

OCTOBER 19, 2017

by Steve Owens, Founder and CTO of Finish Line Product Development Services. The lean start-up movement has been based on a single insight – which the purpose of a start-up is to discover a business model that works. Reducing product turn time. The Lean Start-Up Environment. Extending the runway.

Product Development 153

Product Development Lean Developer Product 153

Startup Lessons Learned

NOVEMBER 20, 2014

Guest post by Lisa Regan, writer for The Lean Startup Conference Eleven months in the making, the full schedule for The Lean Startup Conference is at last complete, and we can’t wait to show you around! For first-time attendees, this conference offers a complete introduction to Lean Startup.

Lean 156

Lean Programming San Francisco CTO Hire 156

ReadWriteStart

JANUARY 16, 2020

Being relatively a new service trend in today’s tech-driven world, CTO-as-a-Service (CaaS) is notably gaining its momentum. Though CTO as a traditional full-time position exists for decades, some companies do not feel they need a technology executive. Ideal scenario assumes there’s a CTO in house. Early-stage startups.

Fractional CTO 85

Fractional CTO CTO CTO Hire Part-Time VPE 85

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. Ive founded and self-funded a (lean) startup on my own.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 11, 2017

Guest post by Jennifer Maerz, Program Chair of Lean Startup Co. For eight years, our flagship conference has focused on sharing stories and lessons of putting Lean Startup’s entrepreneurial methodology into practice. Lean Startup Week (Oct. 31 ( limited to the first 200 Gold Passholders.)

Lean 108

Lean Programming San Francisco Cofounder 108

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MAY 7, 2009

They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place. Initially, IMVU sought to quickly build a product that would prove out the soundness of their ideas and test the validity of their business model.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Just change it. All is not lost, though.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. chatted five times?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

This is going to be BIG.

APRIL 27, 2010

This is the case when the requirements of these events don’t actually include building a real business or product. We spend way too much time, particularly in and around the New York area, teaching fundraising versus company or product building. How does the average Lean Startup Meetup get event space at a school?

New York 121

New York CTO Hire Technical Review New York City 121

Both Sides of the Table

FEBRUARY 16, 2015

Here is where I see this really play out: Product Management. Most CEOs fancy their own product skills and like to weigh in on priorities. At times I wanted the engineering team to produce features to support our sales efforts to I occasionally leaned on them a bit. CEOs often meddle in products and dev teams hate it.

Startup 150

Startup CTO Hire Sales PR 150

blog.chrisomeara.com

OCTOBER 23, 2010

Chris OMeara Main | Probing Code Quality » 01/31/2010 Startup CTO: Could It Work? A CEO friend of mine recently asked my opinion about Tony Karrers Startup CTO or Developer article. I think the part time CTO could work. A few had the title CTO but they all fit the technical rock star and hacker profile.

Fractional CTO 40

Fractional CTO CTO Hire Startup Cofounder 40

konamoxt.com

OCTOBER 23, 2010

January 21, 2009 Why Your Startup Can’t Afford To NOT Hire a CTO As I mentioned in my last post, one of the many things I do as an entrepreneur is to advise other start up companies. One of the common requests I get as an adviser is the help interview and vet potential CTO candidates. This is critical!

CTO Hire 40

CTO Hire CTO Hiring Engineer 40

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 2, 2008

The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0 Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

The Next Web

OCTOBER 10, 2013

Hire everyone you need as an employee. After being part of a team of five that co-founded a fairly successful company and still have the original team together after half a decade, here’s what I learned about having cofounders. Shoulder – not to cry on, but to lean on. Skills – I do product, business, marketing.

Cofounder 143

Cofounder Technical Cofounder Kenya Dilution 143

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Steve Blank

OCTOBER 5, 2009

A Phone Call After I left MIPS Computers I was in New York tagging along with a friend (a computer architect whose products at Apple a decade later would change the shape of personal computing) who was consulting for a voice recognition startup. Wasn’t he a CTO or something? (He Only then did I realize we both forgot to ask.

North Carolina 133

North Carolina Silicon Valley Fractional VPE Part-Time VPE 133

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 18, 2008

You can find out what it would take for them to adopt your product, and then follow up a week later and see if they did. Same with finding out what it would take to get them to recommend your product to a friend. Lean Start-up SlideShare prez at Web 2.0 You can even meet the friend. can I talk to them?" What would I like to see?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. You cant do science and be defensive at the same time. By starting a new product off with as few features as possible (1?),

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. The store determines which products sit on which shelves, and which yours sits next to. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

The Next Web

DECEMBER 4, 2013

These categories came from Yonder conference , a conference held to discuss just such challenges and solutions: hiring and onboarding. In short, these are the top 10 remote team management lessons I have learned: Find a way to meet at the same time. Hire those you trust. Biggest future challenge: hiring. legal issues.

Management 152

Management SCRUM CTO Hire Distribution 152

Steve Blank

JULY 30, 2009

As the (very junior) product marketing manager I got a call from our local salesman that someone at Apple wanted more technical information than just the spec sheets about our new (not yet shipping) chip. Therefore the first step is to figure out whether customers know about the need for a product like yours – is there a market.

Silicon Valley 146

Silicon Valley RSS California Customer Development 146

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

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. These tests are written by the engineers themselves, and they must all pass every time. Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. You have customers, they are using your product, and you are trying to help them. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? But then what? And fix the ones from before. And polish them more.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Up and Running

MAY 23, 2016

Noah has been a key figure in the making of LivePlan, our own SaaS product. Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods. The business model.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

SEPTEMBER 29, 2008

Question 1: When youre adding features to a product used by an existing user base, do you still do split testing to determine usage patterns? Existing customers already have an expectation about how your product works, and its important to take this into consideration when adding or changing features. Absolutely, yes.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. for Harvard Business Revie.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. For readers concerned about the chasm, I recommend reading Seth Godin's thoughts on "Being remarkable" and finding a unique edge/twist for your products and marketing (edgecraft). The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 22, 2008

If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68