YoungUpstarts

JULY 30, 2019

This waterfall methodology follows a few consecutive steps, including analysis, designing, coding, testing, deployment, and maintenance. So, when you build software, it is almost like building a house of cards. Second is that you really can’t make any changes to your code phase. And here comes the role of scrum master.

SCRUM 113

SCRUM Software Review Hiring Agile 113

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

The Startup Magazine

APRIL 12, 2017

From marketing to product development, to new software tools and communications, the list is almost endless as to the digital transformations taking place. The team at Everypixel asked designers, editors and experienced stock photographers to help them generate a training dataset as an example.

Technical Review 74

Technical Review Agile Software Review Algorithm 74

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. Do you fix bugs before writing code?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

The Startup Magazine

SEPTEMBER 20, 2019

Detractors – who are unhappy users that may damage your brand through negative reviews. An NPS software surveys users at an automatic schedule of your choosing and tracks the users’ journey for behavioral insights in addition to the customer feedback survey. Agility, Adaptiveness, and Responsiveness. To Round It Up.

Software Review 105

Software Review Management Early Stage Startup 105

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. The current code is spaghetti, but the new code will be elegant.

Software Review 164

Software Review Engineer Management Technical Review 164

Hearpreneur

SEPTEMBER 22, 2021

The reason for its success is due to not holding ‘compromises’ as an option. Teams under Tesla wanted to make an “electric car” without compromises, which is why the Tesla Roadster is designed to beat a gasoline sports car like a Porsche or Ferrari in a head-to-head showdown. Thanks to Christina Giaquinto, Modular Closets !

Technical Review 122

Technical Review Entrepreneur Software Review SEO 122

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 argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Hearpreneur

JANUARY 26, 2022

To prevent hackers from gaining access to your business's checking account, use low-cost software and dual controls to strengthen your payment processes. Press releases are becoming less successful, partly due to the difficulty of obtaining earned media. Thanks to Oliver Andrews, OA Design Services ! #19- 3- Multimedia spending.

Software Review 122

Software Review Technical Review Artificial Inteligence Entrepreneur 122

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?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

crowdSPRING Blog

MAY 11, 2012

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! How to Increase Trust for a Landing Page Design – [link]. Better Agile Than Smart – [link]. Six Myths of Product Development – [link].

Social Media 92

Social Media Small Business Design Media 92

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. But there is more to technical debt than just the interest payments that come due.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Both Sides of the Table

NOVEMBER 1, 2009

We spent time out in the marketplace talking with customers, looking at their solutions, comparing ourselves with our competition and then squirreling ourselves away in our offices designing our next set of features. They communicated this to product management who looked at all of the internal requirements we had generated (e.g.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

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. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

Still, every article I read turns the creative process of business and product design into Vulcanian objectivity. My first product at Smart Bear had a non-optimal, floating-in-win invention called the "mini-viewer." Code Historian was my first product. It was always a high point in product reviews.

Software Review 226

Software Review Metrics Lean Algorithm 226

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. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

ConversionXL

JUNE 13, 2017

Agile marketing may not be a phrase you hear often, but it’s becoming increasingly popular and important. Traditionally associated with development and product management, agile is a lightweight and, well, agile framework for software development and bringing features and products to market.

SCRUM 112

SCRUM Agile Marketing Development Team Review 112

femgineer.com

JULY 18, 2010

HOME About the Femgineer Speaking Engagements Reading List Recruiting Startup Engineers With the startup market taking off, there is always a clamor to find good engineers, developers, and designers. We like sitting at home or in coffee shops on our laptops coding away fun projects. Or do you just want a code monkey?

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Kent Beck is deservedly famous for his many contributions in the software industry. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. We changed our model to B2B and adopted Agile around 2002. May 15, 2009 5:59 PM Eric said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

AUGUST 26, 2009

Im also excited to share two long-form reviews from actual attendees. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. That meant getting designers, programmers, and QA folks to cross-train and work together as peers. I was really overwhelmed this time.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. For example, the best book reviewers only review books published by the best publishers, which only accept manuscripts from the best agents. And how could they possibly review a blog? Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

ConversionXL

OCTOBER 7, 2021

These are the four stages of a product we’ll be focusing on. . However, on a more granular graph, the introduction phase would be preceded by a product development stage. This stage is used to determine the viability of your product and confirm when it should go to market. Image source.

Product 142

Product Marketing Software Review Social Media 142

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

No wait, I forgot, actually the question is: What happens when employee #2 makes off with your code and roadmap and marketing data and customer list, moves to Bolivia, and starts selling your stuff world-wide at one-tenth the price? But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

ConversionXL

SEPTEMBER 5, 2019

Customer personas are often talked about in marketing and product design, but they’re almost never done well. This post will outline the entire process, giving code examples, data analysis examples, survey questions—the whole thing. This post contains video, click to play]. Instead, they wanted conversation starters.

Software Review 115

Software Review Design Agile Analytics 115

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136