Remove Continuous Deployment Remove Engineer Remove Product Development Remove SCRUM
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. Labels: customer development , product development 8comments: Sarah Milstein said.

Agile 111
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. For more on continuous deployment, see Just-in-time Scalability.

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: The lean startup

Startup Lessons Learned

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168
article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec. The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. Labels: product development 8comments: Vincent van Wylick said. Nice write-up.

article thumbnail

Lessons Learned: Built to learn

Startup Lessons Learned

No engineering team. So instead of having sales, marketing, and business development, we have a problem team implementing customer development. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. You need a problem team and a solution team."

article thumbnail

Embrace technical debt

Startup Lessons Learned

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. The biggest source of waste in new product development is building something that nobody wants.

article thumbnail

The four kinds of work, and how to get them done: part three

Startup Lessons Learned

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.