Week 4 (Febraury 6 – 11) is here and its time to work under pressure since exams are ahead. A lot of projects deadlines are coming through bottleneck these days, but for this one the new sprint is starting.
What is up for this sprint?
Hopefully the front page with a final design and fitted in the angular setup. It is time to start finishing our trello assignments. In our team meeting we agreed to split the work by doing a functionality each. Specifically:
Week 3 (really week 4 if you take in account the first two setup classes) has come to and end, and is clearly now that the rocky cobblestone road is ahead. What I mean is that things are gonna get rough in the next week and the preparations made us lower the pace of work. We must be aware of this, and be very honest in the responsibilities of each one. And even if we do not make big changes to the product it is necessary to focus on at least checking that something works.
Talk with Ken
On the first session of the week we got to talk to Ken, something that I thought was very important because it could make my teammates and I have a greater commitment in what we are doing. Unfortunately I got out of my part-time job a little late, enough to get stuck in traffic and not be on time for this meeting. However, I feel satisfied with what I have contributed and I trust that together with my team we can resolve the communicative obstacles.
Lesson learned: This is one more experience to remember the importance of time management and commitments.
Next stop week 3 (January 30 – Febraury 4), the team work will be more split as we need to get stuff done. Hopefully we write it down in our trello board so it can be used as a backlog,
My work this week
I will be working on the front-end design of the home page and try to make it flexible so it can fit with the Angular project that has been already done, so that means a little more research of how to that. Also I need to find a testing method (if it exists) that can save me a lot of time while doing the user interface.
The first sprint has passed by and we got some first feedback. We had made the very first mockups drafts in html and css, and start deploying the Angular framework setup. Last friday we exposed our idea of project to the group, and we are gladly we did because it lead to an amazing feedback.
Team resolutions
Try to focus first on deliver a functional product, that could be able to scale after we do not work longer on it.
The ultimate purpose is learn, so we dont need to kill ourselves trying to compliment the client. As it is important to know how to deal with clients, this project is time limited and is part of a learning experience so its better not to get stuck on a partial deliver.
On the first week (January 15 – 26) of working on this project, we naturally need to setup a few things. We have to clearly specify what are we going to do and create an enviroment to type down the tasks to do.
Communication
We wil be working in 3 main application for the developing of the project.
Whatsapp: A group for quick messaging just in case of…
Trello: We will use this as a scrum tool for describing project related tasks.
Github: We will make a public repository to access the project, control the versions and push the worked code.
My work for this week
The responsibility that I have for this week is to talk as soon as possible with the people to whom we are going to do the project, to detail the requirements and to be clear about their idea of the business model. Also I need to start looking some documentation of how Angular works.
And, like in the photo above, our project will not have not a single drop of rain.
What it will have is a fun browser-based game that will not use any kind of plug-in because if Adobe and Oracle don’t even care for the support for their products, why should we? (Well, in fact, even if they did, we wouldn’t use them. Nobody uses them now. Nobody wants to).
The game will, basically, be a platformer with timer and a number of obstacles and maybe enemies. The score will be stored in an online leaderboard. We talked about maybe doing some drag-n-drop technology so we could let the players design their levels, and then compete with their friends and stuff. They could even download a level to text translation and share it with their friends.
My partners for the development for this new project are:
Our project for the semester will be a note keeper app, this app will keep track of the notes you’ve writen as well as its classification and share these notes with other users.
First Mockup
Our note app will have the advantage that you will be able to take a photo from some text and it will extract the text from the image and put it in a note (The image will need to be clear and also be text in its most part). Imagine that a professor wrote something important in the board and then, instead of writing it down by yourself you can take a picture of the board and then have it automatially converted in a note, now you are able to share it with others.
This app will be developed by Francisco, Marco, Estefy and me.
We will be developing in native Android, and will (provably) use the Android OpenCV library and tesseract to perform the text extraction, we will create a nodejs server to share the notes. We’ll test our app following the recomendation of the android developers website.
The project that my team and I will address this semester will be an electronic commerce for the sale of hardware (ironmongery), in which the user can choose between different brands.
The main features are the following:
A search engine
A shopping cart
A catalog administrator
A sign-up/ log-in module
Payment services
Database management
Tools to use:
Github: collaborative work control.
Angular: framework for the implementation of the web application.
JavaScript, HTML and CSS: languages with which the development of the web application will be carried out.
Firebase: management of the database that includes the user accounts and the catalog.
