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 customer development Today I read an excellent blog post that I just had to share. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully.
Agile, as the name suggests, is modeled with adaptability in mind. Agile project management and team leadership are best showcased by leading a team of developers in completing software development projects. Agile can also be applied across numerous other industries as an effective project management approach. Agile At A Glance.
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.
Metrics for this depth are rare and only long-term. We might have medium-term goals like “adopting agile methodologies” or “getting everyone on the same page with a project kick-off” as the outcomes for the reader. The metrics for this level are more concrete and objective.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May.
I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better. Expo SF (May.
Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , 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 customer development and agile development is a challenge.
I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. Further feature development does not slow down the development process but as extra information is derived from live metrics, a/b testing becomes possible and the whole game needs to be operated. Being agile.
Social, Agile, and Transformation. I cover several topics including agile software development, software startups, web 2.0, Strategic Agile Thinking: Balancing Value, Innovation and Research. 2) The agile "happy place". Agile teams sprint when value is known, implementation is low risk. and business transformation.
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.
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. Expo SF (May.
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. Expo SF (May.
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?
Crawl your site on a staging environment with freshly deployed features and compare metrics like crawl depth and internal links to similar pages on the live version of your site. In addition to monitoring rankings for targeted query patterns, look at user satisfaction metrics , which depend on the original intent of the query.
Or should it be a part of the development organization or in the Agile development environment? Does that sit into the Agilescrum team? Are they bearing the scrum, bearing the team or everywhere. It would bear a lot of the AB testing expertise into the scrum team, so you can innovate. It’s tricky.
Upon arrival, I incorporated a few elements from my previous stop into this new endeavor, including a battle-tested AgileScrum 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.
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