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
13:58) Advice for companies who think it's too late to start looking for new ways to operate, including some examples from Austin, Texas. (15:55) So now I'm home-based in Austin, Texas and I'm spending a lot of time with a lot of startups and a lot of CEOs that are trying to scale their companies.
” Introduced a few months ago as an Austin event, I’m now doing this live audio advice column to the web, taking phone calls from startups around the country. Which is similar, it has less of a SCRUM-my feel to it. It’s Episode 3 my little “ Loveline for startups. That’s just how it’s gonna be.
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.
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?
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.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. (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. Take a look and let me know what you think.
Looks like Ill be at TiEcon 2009 in mid-may, and at an event to be announced in Austin in early June. 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. Labels: slides 7comments: Hazem Awad said.
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.
Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. " 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. Things like "where is the design time?"
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.
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. I believe its important that product teams be cross-functional, no matter what other job function the product champion does. Take a look and let me know what you think.
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