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.
While I am currently a passionate advocate of methodologies like Agile, Lean, Design Thinking, CustomerDevelopment and more, I try very hard not to get too attached to, or to be too closely associated with, any particular school of thought or technique. And especially of the techniques and methods that I advocate to others.
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuousdeployment, youd better be able to certify that build too, which brings us to. For more on continuousdeployment, see Just-in-time Scalability. Can you make a build in one step?
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuousdeployment. Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. One last thought. Eric, great post.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See CustomerDevelopment Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the CustomerDevelopment process.
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? Case Study: Continuousdeployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.
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.
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: Continuousdeployment makes releases n.
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.
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup? Case Study: Continuousdeployment makes releases n. What is customerdevelopment?
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