Team Presentation

First Steps.

The road from the formation of an idea about an application till the final release is long, sometimes dangerous, but it is a route full of experiences and learning. We are the team “Codefathers” and we are about to start this journey. Welcome aboard!

Who are we?

The name “Codefathers”, as well as the team logo, is derived directly from the movie series “The Godfather”. Like the movie protagonist was able to control everything behind the scenes, we also hope to control efficiently every aspect of the software development proccess.

We consist of 4 people and the sole reason we ended up together, was that it just happened that we sat next each other in the first lecture.

• Ejas Nazeerutheen. He is coming from South india. He has done his Masters in Chemical and Energy Engineering.Before gthat, he worked as an business intelligence analyst in Infosys, an IT giant, in India, therefore he is not just experienced with Java but also with dealing with clients and gathering information about requirements. He hopes that he will be able to improve his skills in project management using the Scrum principle, and to dive into Android Development.

• Ilias Merentitis. A Greek Erasmus stundent. He is in the fourth year of his Barchelor studies in Informatics. His main interest is android application development. He is fascinated with how much somebody can do with such a small device. He has some experience with android studio, and android programing with java. He hopes that this project will help him develop his existing skills further, and to catch up with new modern technologies.

• Dimitris Tzilivakis Also an Erasmus student from Greece. He is in the fourth year of his studies in Informatics. He was also working during those years as a full stack web developer and graphic Designer in a small IT company in Greece. He is passionate about design and concept artist, therefore he has previous experience into UI designing and making presentations. With this project He hopes to improve his communication skills, work as a member of a team and also learn Android development and improve his Java skills.

• Alaba Ojo: Master student from Nigeria, with an electrical engineering background and experience in telecommunication industry. His major area of interest is Internet of things, so naturally this course is an excellent opportunity for him as it provides an interesting demonstration of internet connectivity that can be expanded to include devices. This course will enable him to connect the dots between electrical engineering and software engineering.

At first glance we are kinda different, we all share the same goal though, which is to make software that will help people and solve everyday problems. This is why choose to develop an app that will help people to reassure that their loved ones, have always arrived safely to their destination after a journey.

… and it will also be a long journey for us from those early steps of this team presentation, until the very final release.

Loosely defined roles.

From the member presentation somebody can easily see the range of each member abilities. Our skills extends to different areas therefore it is easy to assign some abstract roles.

• Ilias will focus more on the coding stage of the application, since he has previous experience.

• Ejas will also focus on development, but will be the brain power behind the requirement gathering and analysis.

• Dimitris will make sure “everything pretty”, design the ui of the application, the graphic images of the blog and the slides.

• Alaba will help throughout the project on many different levels, including github management and android developing

However, those roles are not absolute. Every member can and is encouraged to take up different roles and responsibilities during the development stage. Staying into confort zones can be boring. We are not an aeroplane crew, where the flight attetand has to stay to his role, and his role only, because touching the pilot cogpit could be fatal. We are software engineers, and this job demands creativity. By strictly restricting somebody to one role, you restrict his creativity.

What is more, this flexible way of assigning roles will help us respond to possible changes in a better way, since we would be able to immediately switch roles if nessecary.

Communication and organisation

We consist of people who met in the context of this course, therefore we don’t know each other well yet. As a result communication will be one of the first challenges we will face. We have taken some very first steps towards solving this problem (or at least we plan to take them).

• We will make use of technologies such online instant messaging, and teamviewer to help each other.

• Frequent scheduled face to face meets to prepare for presentations.

• Direct group calls, if emergency clarification is needed.

• Github for organising the whole project.

• Use some principles of Scrum in order to have an organised and flexible schedule, apply them through Zenhub.

… and of course hanging out for beers.