Remove Design Remove Lean Remove Product Development Remove SCRUM
article thumbnail

[Interview] Michael K. Levine, Author Of “People Over Process: Leadership for Agility”

YoungUpstarts

I was an early adopter in financial operations and software of lean operational and product development techniques that originated at Toyota, and then of agile as it was promulgated in the Manifesto. I was one of four leaders of an enormous failed development project at Wells Fargo around 2007.

Agile 113
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168
Insiders

Sign Up for our Newsletter

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

article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

XP and Scrum don’t have much to say - they punt. Its by far the hardest part of the puzzle of shipping successful products and both recommend that you get a customer in the room and ask them to clarify what they want as you go. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup.

Agile 111
article thumbnail

Minimum Viable Persona – Get To Know Your Customers All Over Again

YoungUpstarts

Instead, we need to streamline and accelerate our processes by borrowing techniques from the world of lean and agile product development. With this data we can begin to create messaging designed to resonate with this person. That’s the power of the MVP, and of lean and agile approaches in general.

SCRUM 162
article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

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. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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. He wrote it in 2000, and as far as I know has never updated it.

article thumbnail

Embrace technical debt

Startup Lessons Learned

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.