Team project practical points
How to carry out a project is a very confusing topic for people like us who start a project for the first time, and this involves some rules of the software industry, so generally no one will teach you how to carry out the whole project. Today, I had the honor to have a more detailed conversation with a project manager who has been in the industry for many years. I wrote down my experience, hoping to help everyone.
start a project
When a project manager gets a project (when the previous market research is completed), he does not immediately direct the following programmers to code the work, but does the following things before starting to write the code.
- Make a needs analysis , where the needs of a project are. For example, one of their projects is a video surveillance management system, and the customers they face need a reflection of a sense of technology, so the interface of the entire project must be built around the sense of technology. After doing so, even if the back-end function is not particularly perfect, it will quickly attract the attention of users.
- Refine the project , make a project management table , even the lowest Excel table has to be made. What's in the form? The vertical is the content of each item, and the content should be more detailed . For example, you can't directly write a "user interface", but it is divided into "login interface", "registration interface", "Profile" and so on. The horizontal is the person in charge and the time needed. The time needs to be refined to man*day . If you can't evaluate how long this module will take, then list it as a black hole project, put it at the end, and reserve time.
- Drawing a Gantt chart can intuitively show the dependencies of modules, and then know what to do at each time. If you're a newbie like me and don't even know exactly which modules are needed, you can work backwards in time. For example, the deadline for the project is September 1st. I want to set aside one month for the final debug, merge and other work, and then move forward to see what needs to be developed and what needs to be done finally... keep going Go down, know that it's not moving.
- If you don't know the requirements at the beginning, there is a very effective method, that is, brainstorming . A team, each person lists 100 requirements, and then merges, removes duplicates, that is the final requirement of the project.
- Write requirements documents . According to his words, many newcomers do not like the requirements document and feel it is useless. In the end, the project becomes more and more difficult to do. I still don't fully understand what he said, but it is definitely better to write, although it will consume a lot of time.
After doing this, the project is half done, because the work of Coding is behind it.
to the designer
The project manager gives the interface style of the project to the designer, not directly through dictation or the like, and must find examples of others on the Internet, otherwise the dictation designer cannot fully understand, which will cause unnecessary rework, time-consuming and labor-intensive. For example, if you need to reflect the sense of technology, then find an example on the Internet that uses a black background as the background and blue light reflects the sense of technology, so that the designer can see that this is the effect I want. By the way, in the early stage of the project design, it is mainly the work of the project manager, so the project manager is the brain of the entire project, and the entire project needs to be completed in the project manager's head, which needs dictatorship!
feature design
What functionality does this interface need? For example, to make a mobile APP, how do I design the functions of each page? At this stage, the front-end and the back-end are sitting together to burn the brain. Here we recommend the artifact Sketch (for macOS) & Adobe XD CC (for Windows 10 & macOS). As for how to use it, I don’t know how to use it now, and it may be in the future. Write about it in the blog.
Must make a cool project introduction
In actual projects, money is used! So the project manager is going to look for investment, but you haven't started anything, how to attract investors. We can use various techniques to show the final effect through PPT or video. The effect must be cool and eye-catching.
Don't reinvent the wheel
The project manager is just telling you to get it done, not the prescribed way! Most of the things you do have been done by thousands of programmers better than you! You may scoff at this, so here are a few sites for you to look at and come back.
If I remember something, I will update it... (To be continued...)