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
Agile Scrum daily meetings have become a commonplace solution for development teams to hit and exceed targets. One Teams app in particular can be a godsend to teams forced into adopting remote work as standard and still maintain a working scrum methodology. ScrumGenius.
Now that could be a private Wiki, that could be pretty much dozens and dozens of different products, but the key thing is you need to be able to just put something there and your co-partner has the expectation that that’s where they go to see what’s going on. Which is similar, it has less of a SCRUM-my feel to it.
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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.
I would add -- think of your development and running your business like a PM/Developer uses Agile or Scrum in software development. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. The wise entrepreneur will take this advice seriously in order to distill his ideas down to their essence.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create.
Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. " And, as I tried to outline in the article, process improvements that reduce overall batch size might be a better choice. Bring your questions.
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. Bring your questions.
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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. link] April 11, 2009 10:24 PM Daniel Prager said.
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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.
A group of Seedcamp entrepreneurs started a startup tools wiki for that purpose, and we thought it would be well suited here. Github -Â Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs. Banana Scrum â?? A tool simple as Scrum itself. Legal Wiki â?? Acunote â??
At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. I believe its important that product teams be cross-functional, no matter what other job function the product champion does.
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