Have Geek Brain

What do you do before starting a project?

I am still a fairly new project and I haven’t worked on large projects yet. However, several projects for the school showed me things that I had never thought of before.

Pre-project planning. In one of the projects, we faced a huge problem at the last minute, and the other project was not divided very evenly among the partners, so all the work was done at the end.

So my question for everyone here is: how do you plan the project in advance?

Please try the following: Design (render the UI by hand, UML, etc.) Division of Labor Timing (especially how you estimate how long it takes for certain things) and whatever you can think of.

Thanks for the help!

+2


a source to share


2 answers


I do very little before starting a project. I consider everything I do for the project as part of the project.

I realize this is not a very useful answer, so this is what I usually do at the beginning of a project:



  • I check that the project entry is clear. Do I know what to do? Are there any guesses that haven't been tested yet? If the project is not clear or my understanding might be wrong, I go back to the client / project to make sure I understand what they want me to do right.
  • I am doing a ball estimate for a project, breaking it down into sub-tasks, which I estimate take no more than a few days (including prototyping). I'll sum it all up and use it as a rough rule of thumb for how long I think it will take. The scores have two meanings: the "average case" score, approximately 66% probability of completion during this time, and the "bad case" score, approximately 90% probability of completion during this time. If the difference between the two values ​​is large, it means that this is a high-risk item.
  • I start prototyping a project starting with the highest risk. If I learn something from prototyping that goes back straight to my case and sub-task.
  • When the risk has diminished, in my opinion, I get rid of prototypes and get things done "the right way."

The important thing to realize is that you cannot plan ahead. The software is unpredictable, customer requirements change, you realize that you have not been able to eliminate some assumptions. Don't be discouraged if you are wrong. You will ALWAYS get some parts wrong the first few times.

+6


a source


There are several steps to consider before starting a project. However, the real start of a project is when an idea is given, then you have to analyze how viable it is. PMBOOK is an excellent guide for this. http://www.unipi.gr/akad_tmhm/biom_dioik_tech/files/pmbok.pdf



+2


a source






More articles:


All Articles