Remove Agile Remove Document Remove Lean Remove Software Engineering
article thumbnail

Case Study: Lean UX at work

Startup Lessons Learned

Jeff has been promoting the use of Lean UX as an effective method to spur greater innovation, quality and productivity in startups as well as within teams in larger organizations. Lean Startups need to make snap decisions, iterate quickly and pivot when needed. Levels of Agile adoption span the full spectrum across our 6 Scrum teams.

Lean 165
article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

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
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Why Real Learning is Outside the Building, Not Demo Day

Steve Blank

Over the last three years our Lean LaunchPad / NSF Innovation Corps classes have been teaching hundreds of entrepreneurial teams a year how to build their startups by getting out of the building and testing their hypotheses behind their business model. Filed under: Customer Development , Lean LaunchPad , Teaching.

Lean 323
article thumbnail

Lean Startup at Scale

Startup Lessons Learned

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. One good example is the way in which we''ve adjusted the length of different phases of our agile sprints.

Lean 167
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. We owe a lot to this seminal document. How does Set Based Concurrent Engineering help?

article thumbnail

CEO Friday: Why we don’t hire.NET programmers

blog.expensify.com

It is clear that good software engineers avoid you. NOTE: Software engineers are engineers, “programmers” are what you use to control the central heating. Really skillful software engineers do not use.NET. And their open software engineer positions reflect that. Elaine Kenny.

Java 107