To Do, or Not To Do…
Like most millennials trying to navigate through life as an adult, I had trouble being able to manage my time wisely, and as a result, I ended up missing deadlines, plans I made with other people, and even forgetting things on my grocery list.
As a result, I turned to downloading applications on my phone and on my computer to help me solve my problem. Unfortunately, for what it was I needed, either applications were too complicated, or it was so outdated it frequently crashed, thus adding on a new set of problems to my unorganized ones. I knew I wasn’t alone, so as a result my project partner Colleen Ni came up with the idea to completely revolutionize our productivity habits along with others.
Our goal is to help young adults achieve a piece of mind and assist them with living less stressful life through our productivity app, Projects(Working Name), which manages and organizes your tasks.
As described in the ScrumGuide, Sprint Planning is planning the work that needs to be done. Time frames for sprints can range from 8 hours to a month, depending on what the Scrum Master or client needs.
Sprint Retrospectives are what take place after a sprint, and prior to the next Sprint Planning. What is usually discussed in sprint retrospectives are what went well, what needs to be improved on, and commitments on what needs to be improved. Sprint planning and retrospectives provide engineering teams with an opportunity to focus on introspection and adaptation.
Throughout our 6 week sprint, Colleen and I regularly had retrospective meetings in order to stay on track to completing our project. Initially it was a bit hard for us to find the right time and place to meet to discuss our project, but what worked for us was mini retrospectives that lasted around 5–10 minutes in which we discussed and updated the other on our project’s progress. As a result, our communication improved and we were able to get more accomplished.
When it came to planning out our app, Colleen and I are both very imaginative and creative people, so coming up with ideas was the easiest part of our process. Our issue when it came to project planning was that we had so many great ideas! After awhile we were able to come to an agreement on what our project should be based on.
Our biggest challenge was by far our technical issues. Originally, we were creating a location-based chatting application using a Meteor/Angular/Ionic stack. Since neither of us were familiar with this framework, we ran into a lot of different errors which gave us nothing in return. After reaching out to staff here at Make School, we were advised to scale our project down. Realizing we were shooting for the stars here, we decided to take our project in another direction by creating a to do application.
User tests are an integral part of an iterative design/developing process. The goal of user testing is to get as much feedback as possible, preferably as early as you can. The best practices we used when it came to our user testing was listening to the users that were testing our application and making changes to improve our project. Below is a sample video of a user test that we conducted.
In a world where we have abandoned our notebooks, journals and post-it notes, we have turned to our digital devices to guide us in our day to day lives. Our application takes away the indecision surrounding what productivity app is for you. We combine the minimalistic UI/UX of free apps, along with the exclusivities that premium apps offer. There is truly no app out there that is like our app, and I am very grateful that Colleen and I were able to achieve this.