The rate that we were now building the product at had our team estimating we would have something out after the date in the contract.
The rate that we were now building the product at had our team estimating we would have something out after the date in the contract.
We learned that keeping the backlog sized is priceless and that reassigning points is useless.
We asked around if people wanted to pair and most were not interested.
Top 10 pages visited on the site.
Is the Product Backlog a list of prioritized “stuff to do”? Does it include defects, tasks and feature requests? What else?
I recently received an email from a senior-level manager, who raises a valid question about all the meetings associated with Scrum.
If there are multiple teams working off of one Product Backlog, how best to reflect and close the iteration?
Attempting to increase collaboration, and reduce competition.
What is absolutely necessary to do for Scrum and Sprints? A check-list like this will have a prescribed, controlling feel of enforcement.
