Austin Startup

MARCH 20, 2017

The software development landscape has changed a lot in that time, but time-honored principles remain so. Here’s my take on an updated Joel Test for 2017, based on my career experience and how we build software at VidiGuard. Without a doubt, some of my changes draw from Agile methodologies (a good idea, but a terrible religion).

Software Review 48

Software Review Database Agile Software Developers 48

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

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. Now Adriana has an epiphany?:

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

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. Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software? Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Heck, thats what it says right there in the agile manifesto. Luckily, Chad Austin has recently weighed in with an excellent piece called 10 Pitfalls of Dirty Code. It seems like it should be the amount of correctly-working code weve written.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. November 5, 2008 10:13 AM spanky said.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Austin Startup

MARCH 17, 2017

Staying ahead of the curve in a competitive world Written by: Farouk Dossa , Senior Account Executive SXSW is a film, interactive media, and music festival and conference held in Austin, Texas that draws thousands of people from all over the world. I believe the most important deciding factor is delivering a solution that feels natural.

Texas 54

Texas Software Engineering Austin Engineer 54

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Revisiting the Software Design Manifesto (and what. Thank you. I know it's going to help me immensely!

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. For software, the easiest batch to see is code. When something goes wrong with production software, its almost always because of an unintended side-effect of some piece of code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. I know many people who think that software works like magic, but to me it actually was magic. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Please leave feedback!) Can you make a build in one step? Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. All customers will see the new software as soon as it’s deployed.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. Hey Someone else who is extending the agile/lean approach beyond just developing software. February 9, 2009 7:45 PM Joseph Flahiff said.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

MAY 31, 2010

Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. His characteristic humility and clear thinking were on display as he casually demolished one sacred cow after another. Of course ideas have to evolve and change.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JANUARY 18, 2010

This case presents a further complication: desktop software. Without being able transparently modify the software in situ, is it still possible to deploy on a continuous basis? Continuous Deployment is a process by which software is released several times throughout the day – in minutes versus days, weeks, or months.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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. Were a software company, so what we do everyday is turn ideas into code. Labels: agile , listening to customers 3comments: hauteroute said. Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 5, 2008

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. When we build products, we use a methodology. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Hearpreneur

SEPTEMBER 15, 2021

These days, medical practitioners can meet through video communication on software built for this specific purpose. Thanks to Lisa Lacey, Lisa Buys Austin Houses ! #18- Long gone are the days when visits to the doctor had to be in person, even for the slightest things like sore throats and stomach upsets. 13- Home security.

Artificial Inteligence 110

Artificial Inteligence Entrepreneur Technical Review Security 110

Steve Blank

MAY 3, 2022

They know this and know that weapons that can be built at a fraction of the cost and upgraded via software will destroy their existing business models. that can make 1,000’s of extremely low cost, attritable systems – “ the small, the agile and the many.” In the U.S., ” Acquire at Speed.

Ukraine 287

Ukraine China Private Equity Russia 287

Startup Lessons Learned

NOVEMBER 13, 2008

Best of luck, Your Software." (OK, Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. I picked up on the 5 whys from Joel on Software earlier this year. Stevey's Blog Rants: Good Agile, Bad Agile Learning from Obama: maneuver warfare on the campa. Good stuff. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

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." How long does the software sit un-deployed? Software is generally always getting better or getting worse. . You can tell a lot about a company from their deployment flow.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 26, 2009

Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what. I was really overwhelmed this time. There used to be a ton of storage startups here. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JULY 29, 2009

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. Combining agile development with customer developm. Expo SF (May.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Austin Startup

NOVEMBER 27, 2017

As our agile coach mentioned when he started working with our team, he was super attuned to the fact we were all women and then realized that it really shouldn’t be any more unique than the teams he’s worked with that were all men. Like many other great teams, we got a lot done, worked well together and had fun throughout it all.

Engineer 63

Engineer Conversion Agile PR 63

Startup Lessons Learned

AUGUST 1, 2009

We might be a ways away from the reality of a Chief Engineer or Product Director role commonly in software development, but ultimately it's going to be a matter of getting the culture right so that people stick around long enough to develop not only the tactical skills, but also the honed instincts and senses. Expo SF (May.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166