Austin Startup

SEPTEMBER 18, 2017

They will manage the steps necessary to identify, select, and integrate your software and IT vendors, including third party product dependencies, email, network, wiki, intranet, project management, and telecommunications. They will review and negotiate all related contracts.

Fractional CTO 54

Fractional CTO CTO Hire CTO Technical Review 54

Startup Lessons Learned

APRIL 4, 2010

► 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering. Otherwise it's a great idea.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

www.chubbybrain.com

SEPTEMBER 28, 2011

After a thorough analysis of those 32 start-up post-mortems, we have determined the common reasons founders gave to compile this list of the top 20 ways to have your startup fail. If getting VC or angel money is one of the ways that will help you avoid failure, why not check out the free Funding Recommendation Engine here ? #20

Cofounder 89

Cofounder Startup Technical Cofounder CTO Hire 89

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Yet talent organized improperly can lead to failure. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JUNE 22, 2009

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. Although I wish I could take credit for these pivots, the reality is that they were not caused by my singular insight or that of my other co-founders.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way. Bring your questions.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I always assumed I wouldnt manage anybody. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 13, 2008

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. Nothing is more demoralizing to an engineering team. Ive been there: is it me or my cofounder thats crazy? jellytheory : Ask WHY?

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

SEPTEMBER 2, 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills.

San Francisco 146

San Francisco Lean Agile Java 146

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 24, 2011

My co-hosts were Bob Walsh and Patrick Foley , hosts of the well-known Startup Success Podcast. How cofounders can collaborate without going crazy. Is that true or is there some engine there I’m not familiar with? So if I were you I would say, ‘That is not a viable engine.’ Ryan: C-H-E-X-T.

Cofounder 208

Cofounder Technical Review Software Review Differentiation 208

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. In response to Five Whys that noticed that not all new engineers were reading the list, we expanded it into a new engineer curriculum. We never set out to build a world-class engineering-training process.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

► 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Practice five whys.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

SEPTEMBER 10, 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Seth Godin: How often should you publish?

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Every time an engineer checks in code, they are batching up a certain amount of work. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Seth Godin: How often should you publish? Bring your questions.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

MARCH 16, 2009

In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Thats why I prefer to think of them as two co-equals: the problem team and the solution team.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 28, 2010

Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. “Some people weren’t comfortable because it wasn’t as fun, and one senior engineer thought we’d be losing the part of kaChing that was an enabler for anyone who wanted to make it as a pro,&# Rachleff recalls.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

MARCH 25, 2010

► 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

SEPTEMBER 12, 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

MARCH 22, 2010

For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. Similarly, 24% of all the patents filed in the US in 2006 had a foreign resident as inventor or co-inventor. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

OCTOBER 28, 2008

whos on the engineering team? Most important slide: demo (if the product solves an obvious problem), engineering resumes (if the product is nearly impossible to build), " day in the life of a customer " (if neither of the above) Breakthrough technology Key questions: who owns the patents? how do you know anyone would want it?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 2, 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Seth Godin: How often should you publish?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

OCTOBER 5, 2008

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. ► 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. Frustration is mounting.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JANUARY 30, 2009

After years of engineering effort, changing these assumptions was incredibly hard. I know of at least five former employees that went on to become startup founders. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. We can accurately predict the future. February 5, 2009 5:43 PM Chris Lunt said.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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.) Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 5, 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Seth Godin: How often should you publish?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 8, 2008

Instead, we do everything possible to validate the founders belief. Most people cant sustain more than a few of these iterations, and the founders rarely get to be involved in the later tries. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified.

Customer Development 168

Customer Development Developer San Francisco Customer 168