Feld Thoughts

MARCH 11, 2010

Most of the companies we invest in release software at least once a month. Some release weekly, or even daily. If you are releasing at least monthly, it’s easy to do a full day hackathon at least once a quarter.

Software Review 138

Software Review Wiki Continuous Deployment Agile 138

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. During this period, the Palantir Gotham team grew from five developers to around 35. So what was going on?

Lean 167

Lean Startup Software Engineering Agile 167

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. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

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. Yes, you really can use continuous deployment – even in an SEC regulated environment. Wealthfront CTO Pascal-Louis Perez will show you how.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? February 9, 2009 7:45 PM Joseph Flahiff said.

Lean 68

Lean San Francisco Web Advisory Board 68

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." You can tell a lot about a company from their deployment flow. Usually, whatever is used as a development cycle. How long does the software sit un-deployed?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. One of the sayings I hear from talented managers in product development is, “good enough never is.&#

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 1, 2009

For one, capacity development. Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. What do all those other people do? Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. So, fellow hackers, Id love to hear from you.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuous deployment makes releases n.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JULY 2, 2009

It allows teams to diagnose sources of waste in their development process and continuously improve, reversing the usual trend of teams getting slower over time. These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. My experience is: usually not.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167