www.vccafe.com

MARCH 11, 2013

Startup Resources (Updated Mar 2013). Venture Capital Cafe > Startup Resources (Updated Mar 2013). VC & Startup Resources. Seed Startups. VC Cafe covers early stage Israeli and European tech & mobile startups. Hundreds of startups featured since 2005, will yours be next? About VC Cafe.

Software Review 53

Software Review Technical Review Startup 53

SVPG

JUNE 5, 2015

” These might be user stories or they might be more like some form of a functional spec but it’s purpose is to communicate with the designers and engineers what needs to be built. Finally the requirements and design specs make it to engineers. This is usually where Agile finally enters the picture.

Product 60

Product Agile Engineer SCRUM 60

Startup Lessons Learned

APRIL 9, 2009

MarkH : Key takeaways from Erics great talk #w2e #leanstartup 1) "building a culture to learn " @ericries Marks point is the one that seems to have had the biggest impact from the talk as a whole: that startups should be built to learn. No engineering team. ericries s talk on Lean Startups absolutely fantastic.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 10, 2008

I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. but I have not seen that dysfunction in any of the startups I advise, so hopefully its behind us. There are several ways to make progress evident - the Scrum team model is my current favorite.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

OCTOBER 5, 2008

But I have a special sympathy for the "product manager" in a startup that is bringing a new product to a new market, and doing their work in large batches. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. And still being a startup means continuing to innovate as well as keep the lights on.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. 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. Side-effects that reduce agility are the most damaging symptoms of technical debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 18, 2008

Its even more critical in lean startups when they need to manage growth. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Once an agreement is reached, the Chief Engineer continually watches to make sure that the functions are following through.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

SVPG

MARCH 10, 2016

For many years, as teams move to Agile methods (they usually start with Scrum), many companies decide to contract with or hire an Agile Coach. They understand the engineering and release side of things, but not the discovery side of things. Discovery Coaches are not unlike Lean Startup Coaches.

Agile 60

Agile SCRUM Lean Engineer 60

Startup Lessons Learned

MAY 25, 2020

So now I'm home-based in Austin, Texas and I'm spending a lot of time with a lot of startups and a lot of CEOs that are trying to scale their companies. So we went back, got our agile teams engaged and in 48 hours, we could put up aerial of people's homes. Be very outcome-driven in the world we're going to. Let's go."

Technical Review 148

Technical Review Balance Sheet Texas Austin 148

ConversionXL

JANUARY 14, 2020

In each case, an extension to the existing solution was shipped in a search engine–friendly way and now drives a lot of organic traffic, while also improving the product. First, they have to be publicly accessible for users and search engines. Unless you’re a small, agile startup, shipping new features isn’t as simple as it sounds.

SEO 159

SEO Framework SCRUM Search 159

sivers.org

JUNE 25, 2010

Nothing essential that I disagree with you in your post, but when read by other people with minimal software engineering experience, they can have too high expectations. I am a Ruby on Rails programmer and have written the first line of code for a few startups. Greg C (2010-06-19) # These are great suggestions.

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84