Home > Articles > Software Development & Management > Agile

  • Print
  • + Share This

Combining Stories

As we began talking about how users log in, Lowell wrote User Story 4.6: Login Story. During the discussion, this story brought forth several issues. For example, how would we know whether the user was already a member? If users are already members, do they need to log in or would we log them in automatically? Lastly, should we allow access to people who do not want to become members?

When the login is triggered, and the site cannot detect that the user is a member, the user is transferred to a login page, which asks for their username and password and explains the login process & philosophy of the site.

Two days

User Story 4.6: Login Story


several issues. For example, how would we know whether the user was already a member? If users are already members, do they need to log in or would we log them in automatically? Lastly, should we allow access to people who do not want to become members?

The answer to the first question, how we know whether the user is already a member, turned out to be straightforward: We could store a "cookie" in the user's browser. However, some users do not allow server sites to store cookies. So Lowell wrote User Story 4.7: Cookies, to allow the user to select whether or not a cookie would be stored.

The "create member page" should allow the user to specify whether a cookie is stored on their computer.

 

User Story 4.7: Cookies


For some people the login process is a distraction. Lowell wanted to allow people to bypass the login and still have access to the site without the benefits of membership. So he wrote User Story 4.8: Guest Login, which allows users the ability to log in as a guest.

The login window must allow the user to skip the login, which logs them in as a guest.

 

User Story 4.8: Guest Login


Finally, Lowell did not want users who had already registered, and who had allowed us to write a cookie, to have to log in every time they visited our site. So, he wrote User Story 4.9: Transparent Login.

When the login mechanism is triggered and the person is already a member, detectable by the site, the person is sent to the page that they requested.

"TRANSPARENT"

 

User Story 4.9: Transparent Login


During these discussions, we started drawing a picture of what the login screen might look like. This picture evolved as shown in Figure 4.2. This picture captures all the issues in the four previous user stories, so we clipped them all together with a paperclip and estimated them as a single user story.

Figure 4.2 Create member page

  • + Share This
  • 🔖 Save To Your Account

Related Resources

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