Creating A Simple To-do App

Table of contents

No heading

No headings in the article.

HOW TO CREATE A SIMPLE TO-DO APP

This is the second week of our Bootcamp, we have just been assigned a project to create a To-do app on Jira, prioritize and organize our backlog into sprints, run scrum ceremonies and more, all within Jira Software.

After our first scrum meeting to conceptualize and discuss the project assigned, we went over to Jira software to see what it looked like. It was more like an advanced project mgt /development software. It was initially strange but then, my team and I were determined to learn and get the task done.

This second task was not attained by just myself, Ajibike Abisola, Iyade Spencer, but this time, the entire team was on board which made it easier and fun due to the multiplicity of ideas and amazing contributions coming from them.

Jira software is new to us but that is our only tool for this project so we recommended some videos on youtube for everyone, and followed the tutorial guide shared by Damilare our facilitator to maximise it. In that first meeting, we mapped out in detail what we need to do including user research and other research that will help us get the job done.

Before we started creating Epics, crafting user stories and running sprints, we carried out user research to understand the user needs and perspectives. the responses helped us finalise a decision on a new feature we wanted to add which will distinguish the To-do App.

In PM, research is very important to understand the market analysis, users' perspective, product competition etc. That is one way you can stay ahead and develop a market valuable product; leveraging on data available to fine-tune your ideas.

By days two and three, we were able to come up with 4 sprints and 20 user stories;

  1. SIGN UP/ LOGIN

Description:

The creation of an easy-to-use sign-up/login process using emails, social platforms and collaborative tools e.g Slack, JIRA, MIRO, and Whimsical.

2. TASK SCHEDULING.

Description:

Create a simple scheduling where users can add tasks, prioritize tasks, cancel tasks, delete tasks or reschedule tasks and synchronize with Google, Apple and Outlook calendars for notification of dates and times.

3. NOTIFICATION

Description:

Build a notification service where users can easily get notified when a scheduled task is due. Notification serves as reminders such as 30mins, 1 hour, 2 hours etc. via email, in-app, and pop-up.

By day 4, we reviewed the sprints and user stories created by the team. Kelechi leads the session by firstly bringing Nkechinyere alongside Stanley who was not in the previous meetings on what the team has done thus far. He commended Chisom, on the creation of the Google Forms about the questionnaires for potential users' preference for a To-Do app.

Upon the review of the Epic and user stories, It was found that some of them don't quite fit into certain Epics, so we had to rearrange them from the user stories previously created on Days 2 and 3 while the unnecessary ones were removed. The Epic was concluded after the collaborative effort of everyone else.

For us to create a realistic To-do app, we need the full contribution of the team we had and with that, we leveraged the user research to create user stories and assign tasks.

When we finished the 3 sprints which we classified as our MVP, we worked on the fourth Epic which supposes to be our USP. because of the limitation of time, we could not run the 4  sprints.

BackLog

Using the backlog on Jira, we were able to create issues or user stories under each Epic to run the sprints. this feature allows you to further describe in detail what you mean by your User stories. the description can be the acceptance criteria for the user stories created

The Board

this is a column-like table that helps Pms track the task assigned from to do, progress, done to even reviews according to the date assigned. Here you can monition the movement of issues created as they are being executed

Road Maps

Here, one can see how each sprint is being run according to the time assigned. Usually, teams can run a sprint in a week, 2 weeks or a month or you can even customise your timing for each sprint