Home > Articles > Software Development & Management > Agile

  • Print
  • + Share This

An Expensive Story

Many of the stories fit nicely into the existing active server page implementation, so it was not necessary to convert the entire Web site to servlets. Our intention was to write only the registration system in servlets.

However, Lowell wrote one user story that was much more complicated. User Story 4.5: Smart Site Header affects every page. To implement it, we either had to write a lot more ASP code or change every page to servlets and JSPs.

The site header (i.e., on all pages) should indicate if the user has not logged in and offer them a button to log in (similar to a shopping cart). Show name or e-mail if logged in.

Five days

User Story 4.5: Smart Site Header


The site header is the banner that appears on all our Web pages. It gives our pages a consistent look and feel, and provides common navigation links to the other parts of our site. Lowell wanted a small icon to appear in this header if the user had not logged in. Clicking on that icon would trigger the login mechanism. If the user was logged in, the icon would show the user's e-mail address or name if he or she had given it to us.

The estimate on this story is high—five perfect days—because it would force us to remove the ASP code from every page in the system and replace it with JSPs or servlets.

  • + Share This
  • 🔖 Save To Your Account

Related Resources

There are currently no related titles. Please check back later.