How to make divisions in the software development process

Asked

Viewed 283 times

0

We have a whole project architected 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 start? By news feed or by login? Our team of three developers are having a hard time with this since we’re all laymen, and I couldn’t find anything on the internet about it. Thank you.

More information about the project: We are 2 android/java programmers, and one database, without much clear experience. We have to develop an application where we will need login and password, and a news feed where will appear the friends that the user follows, and also I will have to enter information from google maps, and all this saved within the clear database. 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 don’t have a deadline, so it’s calmer. If someone can give some north, or material to help.

Items: • Login • News Feed • Like button • Google maps • Share with facebook

project-management

  • Maybe you should outline the architecture of the project here. It’s just feed and login, no right?

  • Please edit your question explaining about the project? without knowing what the reality of the project, items to be made, time gets a little complicated to opine ...

2 answers

3


I think you can start by answering a few questions:

  1. What are all the tasks required for the project (including system components, design, purchasing software, hardware, or any resource)?
  2. Which of these tasks depend on others?
  3. How much time/effort will be needed to complete each task?
  4. What is the level of complexity of each task?
  5. Which tasks run the risk of becoming more costly throughout the project? For example, a software on sale will be more expensive if purchased too late, or an API you don’t know well may prove more complex than expected and increase the time needed for the task.

The first three questions can be arranged in a gantt diagram to facilitate the analysis.

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

  • Thank you very much for the reply, thanks!

2

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

  • I’ll do a search on Crum. Thanks

Browser other questions tagged project-management

You are not signed in. Login or sign up in order to post.