This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customerdevelopment Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean SoftwareDevelopment. Labels: customerdevelopment , lean startup 8comments: Amy said.
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. Please leave feedback!) When its receding, we rescope.
So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup?
Thats the essence of so many of the lean startup techniques Ive evangelized: customerdevelopment , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customerdevelopment and agile development is a challenge.
Should you co-found your company with a softwaredevelopment shop? I’ve talked with a number of softwaredevelopment shops who are eager to get into the business of cofounding companies, i.e., getting product revenue and equity instead of just consulting revenue. mentor VCs, e.g., most VCs. Our model at Casual Corp.
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. At IMVU, we found 60 days was just about right.
Let's consider cases: Can you have a piece of software with good product design and bad technical design? In that case, the user experience and system performance might be good, but the cost of future development would be high. Can you have a piece of software with bad product design and good technical design?
Because then you’d miss out on: Whether it’s better experience to build a complete, tiny startup or to do more in-depth customerdevelopment for a meatier problem. So that means stuff like thinking about what a business model might be, it does mean customerdevelopment. So I have a question for you, Jason.
Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. We had all the tools in place but we didn’t actually practice agile development. Scrum reports would come in once a month, nobody was actually responsible for anything.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content