How to make divisions in the software development process [closed]

Navigation
0

We have a whole project outlined on paper, drawings, sketches, what each part of the system will do, but how can we manage the team, define by which part of the code to begin? By the news feed or login? Our team of 3 developers is having difficulty with this since we are all lay, and I could find almost nothing on this on the internet. Thank you.

More information about the project: We are 2 android / java programmers, and one database, without much experience. We have to develop an application in which you will need a login and password, and a news feed where you will see the friends that the user follows, and I will also have to enter information from google maps, and all this saved inside the database of course. What we have difficulty, is where to start, programming? design What part of the programming? First the maps, or first the login? First the feed? We have no deadline, so it's quieter. If anyone can give some north, or material to help.

Items: • Login • News feed • Like button • Google Maps • Share with facebook

    
asked by anonymous 12.04.2014 / 23:50

2 answers

3

I think you can start by answering some questions:

  • What are all the tasks required for the project (including system components, design, software acquisition, hardware, or any feature)?
  • Which of these tasks are dependent on others?
  • How much time / effort will it take to complete each task?
  • What is the level of complexity of each task?
  • What tasks have risks of becoming more costly throughout the project? For example, promotional software will become more expensive if purchased too late, or an API you do not know well may be more complex than anticipated and increase the time needed for the task.

    • The first three questions can be arranged in a Gantt diagram for easy analysis.

    Once you have this information, I believe it will be easier to decide the priority of each activity. Tasks that are more dependent and more risky in general should be done first, so as not to block the progress of others, give more time to respond to risks before they become critical and avoid surprises at the end, when you are tight deadline .

        
    13.04.2014 / 02:19
    2

    Start by the project, clearly define each step and organize by order of value, the more you add value to the application the higher the priority, eg: (Database, login system, news etc), each module of this try to break more on small tasks of 1 day for example. of the one researched in scrum that will give you a better idea.

        
    13.04.2014 / 02:20
    You can run the same site in different domains Php equal functions return different values