article thumbnail

Why Successful Product Management Involves More Than Spectacular Specs

YoungUpstarts

Upon arrival, I incorporated a few elements from my previous stop into this new endeavor, including a battle-tested Agile Scrum process and the corresponding technology. Development teams must build a muscle for reliable estimation and delivery, whether through Scrum velocity metrics or their own approach.

article thumbnail

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

XP and Scrum don’t have much to say - they punt. If you look at the origins of most agile systems, including Scrum and XP , they come out of experiences in big companies. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager". Embedded in that assumption is why startups fail.

Agile 111
Insiders

Sign Up for our Newsletter

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

article thumbnail

The Search For Product Market Fit

Seeing Both Sides

The company is part of a new wave of companies, such as Skillshare, Boston StartUp School and others, to provide "over the top" professional education to help chip away at the skills gap and enhance professional development. I had never tried a spontaneous scrum like this before and it was great fun. Intelligent.ly

Search 46
article thumbnail

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

Startup Lessons Learned

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. At IMVU, we found 60 days was just about right. Amazon PostRank

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. The wise entrepreneur will take this advice seriously in order to distill his ideas down to their essence. No more, no less. September 15, 2008 9:19 PM James said. April 27, 2009 8:59 AM Anonymoussaid.

Lean 168
article thumbnail

You don't need as many tools as you think

Startup Lessons Learned

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. Scrum reports would come in once a month, nobody was actually responsible for anything. We had all the tools in place but we didn’t actually practice agile development. Amazon PostRank

article thumbnail

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

Startup Lessons Learned

There are several ways to make progress evident - the Scrum team model is my current favorite. If you have a true cross-functional team, empowered (a la Scrum) to do whatever it takes to succeed its likely they will converge on the result quickly. When its receding, we rescope. Do you have a spec? Amazon PostRank