Best practices for Login Page

Tariq_lpxt2m

Hi,

 

This is the first time I am using any kind of project management software and I wanted to know if this was the correct way to do things. I am creating a web application and I am designing it, another team member is converting my designs to html and then another developer is taking that html and pushing it to live for me to test. There are so many steps in a login page such as for got password, set new password etc and I was wondering would the correct way to be put them all under one epic? There is also a sign up page that I have to too so I just want to learn the best practices for something like this. Thank you. 

Walter Buggenhout

Hi @Tariq,

Imagine how complicated things could get if your web application is about managing a web shop, or for playing video content on demand!

Rather than thinking about al the technical steps you need to take, take a step back and think about the customer journey here. What features / value do you want to offer to your customer?

Write these - from the customer perspective - in user stories. Traditionally, they could be written like this:

As a customer,

I want to login to application

So I can order a pizza

Or for another use case:

As a customer,

I want to reauest a new login

So I can access the system again when I was so silly to forget my old one

Leave it up to the designers / developers to determine how they should implement this technically. They will be grateful that they can think for themselves. If multiple people need to work on these items, they can still create sub-tasks if they should work simultaneously on parts of the solution, or you can model the different steps of development and testing in your story's workflow.

Adding all the use cases that relate to the login experience under 1 epic called Login is definitely a good idea.

I would recommend you to do some research on how to write proper stories and do story mapping. It will help you draft a good backlog of items to consider, but with the customer in mind. If you split up the work in too many technical details, you have a chance of delivering parts of features to your customers, as it becomes unclear what belongs together or needs to be done first.

Hope this helps!