Buzzme Direct Messaging App

Buzzme Direct Messaging App

Human communication has evolved from just speech 500, 000 years ago to various communication methods today, an average human use 3-4 apps per day for various types of communication which are powered by technology. The global mobile messaging apps market is over $100B in 2023 and the global messaging app users is over 3 billion people in 2023 with Whatsapp serving as the most used mobile messaging app. Among the users of mobile messaging apps, 53% of them use the apps for calls and a wide majority for texting. The industry is characterized by messaging apps evolving into social media apps and trends like rich texts, communication services, business messaging, ads retargeting, use of AI, expansion of social messaging, mobile payments, and remote work are defining the roadmap for various direct messaging apps in the market.

Buzzme was created to serve as a direct messaging app with no ads, and with a focus on enhancing communication, we aim to help users facilitate all of their daily communication in business, work, social and family aspects of their daily communication routine with a single app and in a productive way, we implemented the use of chat categorization that includes message filter settings, instant translation and transcription of text, video and audio messages, file sharing and Groups and channels features that enable collaboration.

We aim to attract people who want to become more productive, values privacy, and collaboration, and use various messaging apps for daily communication in different aspects of their lives; Buzzme will be the app that helps them complete all their various communications daily productively.

The Task

Create a “direct messaging app” project on Jira, prioritize and organize your backlog into sprints, run scrum ceremonies, and more, all within Jira Software.

As soon as we got our task, the team lead shared resources for the team to update their knowledge on how to use the Jira project management tool.

This helps to ensure that all members who contribute and team members who were inactive last week were assigned tasks for the week. Other team members were given new types of tasks different from the ones they worked on last week.

SPRINT PLANNING MEETING

We had our sprint planning meeting on the 17th of April, 2023: we deliberated on the type of app we are creating and we identified features that the app will possess. The sprints for tasks were divided into five sprints; Prd creation, user flow design, user persona creation, etc.

OUR FIRST STANDUP MEETING

Our first daily stand-up meeting was conducted on the 18th of April, 2023. The team lead anchored the virtual meeting on Jira. He onboarded the team members and defined our tasks and processes to execute them.

OUR SECOND STANDUP MEETING was on 19th April 2023. We discussed the progress of the project, all team members assigned to a task gave an update and most of them submitted their deliverables.

OUR THIRD STANDUP AND RETROSPECTIVE MEETING

The meeting was held on 20th April via Google Meet, most of the team members were present and we talked about What did we do well during the week, what could we have done better, and what are we going to do better next time. We also discussed how our tasks can be better, how we got into PM, and how can be more effective as a team.

Challenges

We had a challenge pairing with the product design team, we had to wait for them to deliberate and agree to pairing with us, but this was resolved after we had a meeting with them. Also, the Jira project management tool affected our team's collaboration on the PRD, most of the team members were unable to be added directly from the Confluence board by the team lead and they had to request access, and when they did. Access requests didn't show on the document dashboard, it was sent to the team lead's email which he saw a day after. We evaded this challenge by moving product requirements writing to the Clickup project management tool.

Lastly, communication with the PD Team was not prompt as we have to wait hours before our messages were replied to and to receive updates.

Steps in Solving this Week's Task

Creating a Jira Project and Tasks board for the team; To manage all the team members' communication and to manage our tasks, we used the Jira project management tools stated by the task brief.

Product Name Creation: At this stage, we chose a product name out of the various suggestions from team members and we picked Buzzme.

Product Details and Direction: it is at this stage we debated on the type of app we are building whether it's a social media app or a Direct messaging app.

PRD Creation: We created the Product Requirements Document page on ClickUp space for our team because not the challenges we encountered using Jira's Confluence app.

Product Roadmap, User Flow, and, User Persona Design: The team lead and other team members were assigned to design the User flow and User personas for our key persona.

PRD and other Essentials Proofread and Editing: We collaborated on editing the PRD and all other essentials.

Submission: Buzzme Product Requirements Document was submitted using the required methods of submission.

Buzzme's List of Features includes:

Signup/Login and user onboarding, search functionality, contacts syncing and signup notification, push notifications, profile, chat and chat categorization, text chat, message translator and transcription, audio message and audio room, video call and group video calls, disappearing messages, filesharing, message broadcast, group, and channels.

Our task was completed before Friday this week, we are 80% done by Wednesday, the team was effective this weekend we hope will continue with that.

Product Managers:

Amos Adedoyin

Chidinma Ohaeri

Mitchelle Leonard

Alara Charis

Victoria Ihonre

Afonja Omotomiwa

Nnadi Chioma Faith

Daniel Omotara

Akinlotan Busayo

Timileyin Blessed

Eunice Adamper