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
I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. April 23, 2010 in SanFrancisco. 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.
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.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. April 23, 2010 in SanFrancisco. (Eventually, they may abolish specs altogether) Theres much more this team can do to eliminate waste in the way that they work and thereby iterate faster. Bring your questions.
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. April 23, 2010 in SanFrancisco. When its receding, we rescope.
Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. April 23, 2010 in SanFrancisco. " And, as I tried to outline in the article, process improvements that reduce overall batch size might be a better choice. July 30, 2009 1:29 PM jkorotney said. " It all seems so clear to me.
I have been using various forms of Agile development -- mainly XP and Scrum -- for many years, but only recently came across "customer development" which makes a whole lot of sense to me. April 23, 2010 in SanFrancisco. Inspired me to expand on the "whiteboard iteration" idea with some similar lessons that ive 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. April 23, 2010 in SanFrancisco. Bring your questions.
Editor’s Note: We wrapped up the 2017 Lean Startup Week in SanFrancisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Guest Post by Misti Yang, Writer for Lean Startup Co. We tried to define the best for us, and then we started practicing.”
English has become the lingua franca for doing business, while the technical jargon is as familiar (or cryptic) in Alexandria as in Mountain View: Scrum, sprints, Git, Cassandra, Hadoop. Yet in an increasingly globalized, diverse, interconnected world, it would be a mistake to assume that the same players can dominate in all markets.
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. April 23, 2010 in SanFrancisco. Bring your questions. Take a look and let me know what you think.
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. April 23, 2010 in SanFrancisco. I believe its important that product teams be cross-functional, no matter what other job function the product champion does. Bring your questions. Amazon PostRank
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