Gust

APRIL 27, 2014

Software Development Process via Wikipedia. This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Funding process.

Startup 187

Startup Institutional Investors Angel Investor Bootstrapping 187

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

Burn Rate 120

Burn Rate Hockey Stick Startup Salary 120

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. No BS, no vanity metrics, no launches, no PR. If you’re still kicking yourself for missing him last year, do yourself a favor and don’t make the same mistake again.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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

ConversionXL

SEPTEMBER 6, 2013

Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customer development problem. Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process.

Customer Development 126

Customer Development Conversion Developer Customer 126

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. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

ctotodevelopers.blogspot.com

JULY 11, 2012

I cover several topics including agile software development, software startups, web 2.0, Left on its own, product owners and development teams just may make debatable and sometimes questionable decisions on priorities or implementation strategy. Social, Agile, and Transformation. and business transformation.

Agile 40

Agile Architecture Offshore Software Developers 40

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. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

crowdSPRING Blog

OCTOBER 20, 2010

Product or Service Features Are Rarely A Competitive Advantage – [link]. Product or Service Features Are Rarely A Competitive Advantage – [link]. Why marketer misuse of metrics may be an addressable cultural issue – [link]. Amazon’s Approach to Product Development – [link].

Social Media 91

Social Media Small Business Design Media 91

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. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 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

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

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. Geoffrey also talked through the product adoption cycle, but this was less applicable to the products I deal with as a Micropreneur.

Software Review 47

Software Review Software San Francisco RSS 47

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. Startup Lessons Learned - the Conference (April 23.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0, Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo (and a call for help) Ive been asked to speak this year at the Web 2.0

Lean 68

Lean San Francisco Web Advisory Board 68

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. November 25, 2009 9:54 AM Danny Wong said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Sorry about this being out of context but I wonder if youve read "What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services". Labels: events 3comments: Alexandre Gomes said.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JUNE 15, 2009

This condition makes it much easier for teams to innovate, experiment, and achieve sustained productivity. One large source of waste in development is “double-checking.&# One is used by engineers to refer to the process of getting code fully integrated into production. Continuous deployment also acts as a speed regulator.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. During this period, the Palantir Gotham team grew from five developers to around 35. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches.

Lean 167

Lean Startup Software Engineering Agile 167

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. that justify decisions already made. Pretty soon we ran out of friends.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g. At best, they could copy. Our advantage was speed.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

conversionxl.com

SEPTEMBER 10, 2013

Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customer development problem. Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process.

Customer Development 60

Customer Development Conversion Developer Customer 60

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

FEBRUARY 10, 2009

This also literally can’t catch every problem, because your test sandboxes or test clusters will never be exactly like the production system. But I will tell you not to have too little or too much, because those definitely ruin the food or product. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 1, 2009

He doesnt put out crappy, buggy products and then ask for feedback. My normal answer is that I dont really think thats how Apple products are built. Thats what so many techniques that I advocate are all about: customer validation , minimum viable product , vision pivots , and even throwing away working code. It just wasnt great.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JULY 2, 2009

Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&# The net effect of all this was to make new engineers incredibly productive right away – in most cases, we’d have them deliver code to production on their very first day.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

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. The "just fix it" mentality is counter-productive here. At the end of the day, the product development team of a startup (large or small) is a service organization.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. The work product is a more realistic test, although it requires much more work on the part of the candidate. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

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. Lets start with the most important thing you can do to help product teams succeed: make them cross-functional.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. They have a product that has a moderate number of customers. Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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