This article is about how my team created a URL shortener on Jira, prioritizing and organizing backlogs into sprints, Running scrum ceremonies and more
Every project for a product requires extensive research and team brainstorming to come up with the best strategies and features as the case may be to create the best version of the product.
I started by onboarding the team on Jira software by creating the project on Jira and making the necessary introductions and leading the required conversion for the task.
We proceeded to create an EPIC the team would work on with inputs and suggestions from team members. A user research question was drawn as a questionnaire to get better data for this product. Required questions were created from scratch using a user perspective to get the best response from users. Please note that user research is important to help the team build from the user's view, not assumptions or out-of-market demands
After the EPIC was created, the team was given some time to conceptualize the product and make personal research too. their finding will power the next scrum meeting and determine the kind of features to consider for the product also in consideration to the analysis from the respondent's feedback on the survey sent out.
In the next meeting, the first point of attention was to review the questionnaire sent out in the previous scrum ceremony. From the responses from the survey respondents, We moved over to the Jira Board to iron out what our Epic would be and the accompanying user stories for each epic. This Epic represented different features and functionality created in our URL shortener product.
Many Epics as features were presented and discussed extensively. the team was allowed to retire and come up with at least 5 user stories or issues that will power each Epic
the Epics for our project which we named SUS Project meaning Solo URL Software are:
SIGN-UP/LOGIN
Description:
Create a simple and easy Sign-up/ log-in page for this SUS synchronising the sign-up with a google account.
LINK SHORTENER
Description:
Create a user-friendly interface where users can paste, shorten and copy links.
CUSTOMIZE LINK
Description:
This feature allows users to customise or personalise shortened links to reflect their brands or intentions.
LINK ANALYTICS
Description:
Create an analytics algorithm that allows users to access insights on the use of the shortened link indicating reach, clicks, platforms, dates etc.
QR CODE
Description:
To convert links into QR codes that users can scan using their devices to access the shortened links. b) Ability to customise QR codes with brand logos, frames, colours etc.
TEAM FEATURE
Description:
To create a feature where teams can be added to concurrently work on a project collaboratively.
ONE-CLICK AWAY
Description:
To create a feature that helps users easily shorten or customise their links in one click when copied or highlighted.
Note: we added a description, Label and time frame for the individual epic.
In the next scrum meeting, we were able to review the user stories that were assigned the previous day for the projects Epic. Deliberation, suggestion and adjustment of these user stories were made, especially for those that were not able to entirely meet up. From there, we discussed the next set of steps remaining till the completion of our project which includes running the sprint, completing the sprints and going through the retrospect and reviewing each sprint.