Information for

Request for

Send us an email Microsoft Partner Network membership
Microsoft BizSpark Startup member
VMWare member
Valid XHTML 1.0 Transitional Valid CSS!

Postcode Anywhere

PayPal for Business

Home -> Development -> Scrum Product Backlog
ATL - Scrum Product Backlog

Scrum Product Backlog

The Product Backlog is the master list of all functionality desired in the product. When using Scrum, it is not necessary to start a project with a lengthy, upfront effort to document all requirements. Typically, a Scrum team and its product owner begin by writing down everything they can think of easily. This is almost always more than enough for a first sprint. The Product Backlog is then allowed to grow and change as more is learned about the product and its customers.

Product backlog items can be technical tasks ("Refactor the Login class to throw an exception") or more user-centric ("Allow undo on the setup screen"). My preference is to express the product backlog in the form of user stories, which are a technique borrowed from Extreme Programming, another agile process.

The product owner shows up at the sprint planning meeting with the prioritized product backlog and describes the top items to the team. The team then determines which items they can complete during the coming sprint. The team then moves items from the Product Backlog to the Sprint Backlog. In doing they expand each Product Backlog item into one or more Sprint Backlog tasks so they can more effectively share work during the Sprint. Conceptually, the team starts at the top of the prioritized Product Backlog list and draws a line after the lowest of the high priority items they feel they can complete. In practice it is not unusual to see a team select, for example, the top five items and then two items from lower on the list but that are associated with the initial five.

An example Product Backlog from a real project appears as the following:

  Item # Description Est By
Very High
  1 Finish database versioning 13 RL
  2 Removed unnecessary C# database procedures and tables 5 TG
    Manage licending    
  3 - User licensing 8 PW
  4 - Environment licensing 3 PW
  5 - Application licensing 7 PW
    Solution Analysis    
  6 - Check any existing format changes 140 AH
  7 - Add new format 120 AH
  8 - Round-trip Analyses 120 AH
    Enforce unique names    
  9 - In main application 20 RL
  10 - In import 28 RL
    Analysis Management    
  11 - When items removed from admin site, they should not show up again in the pick list 12 YN
  12 - When new items is added to admin site, they should show up in the pick list 10 YN
  13 - Support wildcards query string 25 GW
  14 - Support keyword query string 20 GW
  15 - User profile check 20 GW
  16 - Sorted order by result 12 GW
  17 - Error handling 32 GW
    Bowser Check    
  18 - Launch IE synchronisation (only show queries/analydes or logged in users 8 AK
  19 - Remove IE settings 2 AK
  20 - Launch Google Chrome synchronisation (only show queries/analydes or logged in users 8 AK
  21 - Remove Google Chrome settings 1 AK
  22 - Launch Firefox synchronisation (only show queries/analydes or logged in users 8 AK
  23 - Remove Firefox settings 1 AK
  24 - Launch Apple Safari synchronisation (only show queries/analydes or logged in users 8 AK
  25 - Remove Apple Safari settings 1 AK

This Excel spreadsheet shows each product backlog item assigned a general priority (Very High, High, etc.) by the Product Owner. Estimates have been developed by the developers but it is understood that they are very imprecise and are useful only for rough assignments of tasks into the various sprints.

-> Abstract Technology's Offshore Development Center
-> Abstract Technology software development process
-> Abstract Technology free pilot trial

Home | Contact us | Site map | Terms of use | Privacy | Resources | Newsletter subscription | FAQ
© 2004 - Abstract Technology Ltd. Online payment enabler and integrator and outsource and offshore development