Below you will find pages that utilize the taxonomy term “scrum”
Measures of size
This post is a slightly updated version of the one published earlier Measurement is fundamental to any engineering discipline and the planning of a software creation work is no different. Whenever you plan to make or renew a piece of software the most important metric as the workload size. Measure of size is important because knowing the amount of work to do and the team skills (i.e. velocity) you can easily derive the work costs and duration.
This post is a slightly updated version of the one published earlier Product backlog always lists items adding value for the customer. It includes functional requirements and non-functional requirements. It can also include items required by the team, but only the ones that will eventually bring value to the customer, e.g. taking into use a continuous integration server in order to guarantee the continuous end product quality. Product backlog cannot include concrete low level tasks and requests for building the intermediate artifacts.
Simple Product Backlog
Want to try handling your Scrum product backlog in just Excel? Here is a template with lots of comments and a video on how to use it.