A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by arnel nicolas:
If devs is dealing with several projects with several tasks. Is it ok to have one backlog list than to have a separate back log list for every project? If they are in one back log list (ideally), how are they(tasks) ranked? I believe
there will be several product owners who wants their task to get prioritized first.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by arnel nicolas:
- in this context we are not considered as a team, we will be treated as group of individuals doing diffrent project. It becomes project focus not customer focus.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Ilja Preuss:
A backlog, in my strong opinion, should be a task list for *one* team, where all members take joint responsibility for the whole backlog. A backlog can't work when people only feel responsible for parts of it.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Lasse Koskela:
In Scrum terms, where you have a product backlog and a sprint backlog, my strong opinion is that there should be one product backlog for one project and one sprint backlog per one team within that project.
Originally posted by Lasse Koskela:
In Scrum terms, where you have a product backlog and a sprint backlog, my strong opinion is that there should be one product backlog for one project and one sprint backlog per one team within that project.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by arnel nicolas:
But whose going to maintain the product backlog? I believe this should be the product owner.
Originally posted by arnel nicolas:
And the sprint back log which I believe is the collection of tasks from the product backlog where developers can pick from.
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by arnel nicolas:
In connection to this thread, how necessary for developers to rank the list of team backlogs? Or why is it beneficial for the developers to have the backlog list ranked (1,2,3,4....and so on)?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |