Android Group Project Management

ITstudent1213

As part of our course we are doing an android app over the next 3 - 4 weeks, there are five of us.

We have all done a very few basic apps so far.

Any tips or suggestions on how to split the workload between us?

I was thinking:

• One person be in charge of layouts,
• Two persons in charge of coding
• One person testing/gathering resources
• One person in charge of graphics etc

Any tips on storing project on Github etc.. (any other recommendations?)

Would it be easier if each person was allocated a time to work on the project?

Could get very messy otherwise - any tips at all welcome!

Thanks.

jimmycrackcorm

Breakdown the lists of tasks to be done in order of priority and then decide who can or wants to take them on one at a time from the top. It may suit to have one person work specifically in particular areas to maximise reuse but the important thing is to integrate and co-ordinate often.

I'd follow a scrum type approach if possible and decide what you want to achieve on a week by week basis. Aim to have something viable and working at the end of each week. co-ordinate each day to make sure everyone is on track and whether they need help.

Github would be very useful. use Youtrack for your tasks, it also integrates with Github

Talisman

You could use BitBucket for the project - Private Git/Mercurial hosting which is free for 5 users, comes with built-in issue tracker and wiki.

Colonel Panic

Git branching comes into it's own here

http://nvie.com/posts/a-successful-git-branching-model/

If you are comfortable with this, you're already better than most graduates!

jester77

Colonel Panic wrote: »

Git branching comes into it's own here

http://nvie.com/posts/a-successful-git-branching-model/

If you are comfortable with this, you're already better than most graduates!

The git flow model is a bit over complicated for such a small project imo. I would just have a master branch and feature branches and stick to rebasing from master and merging back to master upon feature completion.

ITstudent1213

Hmm well my project management strategy to date has just been to make a backup of the project every time I make progress, and rename the folder something meaningful.

colm_c

ITstudent1213 wrote: »

Hmm well my project management strategy to date has just been to make a backup of the project every time I make progress, and rename the folder something meaningful.

You should try to learn one of the source control technologies, not only are the benefits huge when multiple people are working on the same code base, it is also great for potential employers. The amount of graduates who I've interviewed and/or worked with who have never used source control is staggering.

ITstudent1213

colm_c wrote: »

You should try to learn one of the source control technologies, not only are the benefits huge when multiple people are working on the same code base, it is also great for potential employers. The amount of graduates who I've interviewed and/or worked with who have never used source control is staggering.

Do you think I good get a basic handle on it in a day or two?

I definitely want to learn how to use it, but am conscious of time, we only have 3 weeks to submit this (no - we could not have started earlier ), all at the same time as lots of exams, other projects (bla bla bla - excuses excuses!)

Talisman

Try Git - Code School - it's a free course which will get you up and running with Git in a few hours.

ITstudent1213

Talisman wrote: »

Try Git - Code School - it's a free course which will get you up and running with Git in a few hours.

Great, looks good, thanks.

professore

If it's a coding course, the people in charge of the non coding tasks are getting a raw deal. I would split it up differently, giving everyone a section of the app to develop and test.