tag:blogger.com,1999:blog-2171806952755238008.post5038586163150328685..comments2023-10-31T09:23:54.559-07:00Comments on Leaning Towards Agility: One Story FlowSkip Angelhttp://www.blogger.com/profile/09579974445836730481noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2171806952755238008.post-58441290660875675042007-05-09T09:38:00.000-07:002007-05-09T09:38:00.000-07:00Ilja,We actually have a team smaller than this and...Ilja,<BR/><BR/>We actually have a team smaller than this and are making it work. As long as you don't assign stories to developers ahead of time, and make sure that the team is determining the tasks for each story you should be in good shape. If those things happen, then developers can "sign up" for the tasks for the highest priority story if they believe they can fulfill the work. Sometimes this will be challenging because the particular developer may not have the right skills. <BR/><BR/>Because of this, developers tend to try and specialize in particular technical areas and become the "go-to" people. This is a BAD thing because it creates dependencies that will not allow you to be successful in "One Story Flow". The team should always work towards sharing knowledge and gaining skills so that each developer can understand any part of the system to be able to grab tasks/stories based solely on customer value, This is the ultimate goal that you want to obtain.Skip Angelhttps://www.blogger.com/profile/09579974445836730481noreply@blogger.comtag:blogger.com,1999:blog-2171806952755238008.post-74134889561228133822007-05-09T08:55:00.000-07:002007-05-09T08:55:00.000-07:00Very thoughtprovoking, thanks!What would be your a...Very thoughtprovoking, thanks!<BR/><BR/>What would be your advice to a team of seven developers, with story sizes of 4 to 24 person hours, that is interested in giving it a try?Anonymousnoreply@blogger.com