Chapter 2: Agile Methodologies and Approaches
40
Figure 2-10“ The x ’ s next to each line item allow the user to delete the item from their Shopping Cart, ” you explain.Claudia points at the mockup. “ There ’ s something missing. There ’ s no recalculate button. You know,
when they decide they want two of the abc shirts instead of just one. ”“ We ’ ll use AJAX to automatically recalculate the totals without having to do any of that, ” you explain,
which seems to satisfy her. You know that this will make some things easier for you, but it will require
users to have JavaScript enabled. You will need to put in some validation and error checking right before
going live. But something else is still bothering her.“ What about calculating taxes and shipping? Some items are heavier than others. We can ’ t just do a flat
rate. ”“ Since I assume you ’ re using Paypal or Google Checkout to handle payment, let ’ s leave that part until
later, as it ’ s easy enough to integrate. ”Claudia nods and says she ’ s satisfied with the mockups. “Good”, you say, because it ’ s time to share the
product backlog with her and make her a true product owner. Once she knows her way around
the product backlog, it ’ s time to plan the first sprint.Revisiting the Product Backlog
You explain to Claudia that the product backlog is a prioritized list of requirements for her project. She is
the product owner and, as such, creates and maintains the product backlog and uses it as the centralized,
authoritative list of requirements, from which are derived all the tasks that are undertaken in any
individual sprint.