Continuous Deployment Naming SCRUM Search 
Startup Lessons Learned
MARCH 16, 2009
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.
Startup Lessons Learned
SEPTEMBER 22, 2008
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. Simply put, we upload all the tasks and assign a name to each task. 1 comments: Josh Moore said.
Startup Lessons Learned
JULY 29, 2009
To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. So far, this is all an academic exercise in naming - but I think it has an important real-world effect. One last thought.
Expert insights. Personalized for you.
111 
Let's personalize your content