| This work belongs courses | <Links courses> |
|---|---|
| Where the job requires | <Link job requirements> |
| My aim in this course is | Concluding Thoughts |
| Team Name | Rise ape family |
Course Review
The first job link :( https://www.cnblogs.com/JoneAndMe/p/11503976.html )
to sum up
Blink of an eye a few months have passed, and now look back to this time, this course gives me the experience of growing and rewarding.
Before taking the course, although the project has done, but there is no systematic, efficient, formal set of management methods. Knock Code is a very serious thing, there can be no logical errors, software development process should be the same scientific rigor.
My biggest achievement is the cooperation between local team members, in general, the development team is far less personal development of high efficiency (that person with appropriate qualification), I have done before the project is so that each person only needs to manage their own that aspect, as far as possible no intersection between people, or are likely to delay the progress of the disagreement. Although the team some people wait for others the phenomenon is inevitable, but that does not mean that the former is no other thing you can do while waiting, assigned the task of how to deal with the labor-time team members to balance the door knowledge.
For the answer to the question before:
The first question that contradiction or core crew coordination and ability to form a team, if we level or less, will be impossible to adopt superstar mode and so on, but if there are more powerful man team, then we can not avoid this issue. My view is that, according to the team members need to choose form. If we are to enhance the capacity of the first line, the second purpose of learning to do the project, twinning, etc. can be adopted to develop, if not, to take the actual situation most efficient way.
The second paradox is that what is asked of a good standard software, or the software should be developed and to what extent. There is no perfect software in the world, if the pursuit of the perfect software continue to improve and take the time it was like falling into a bottomless pit. We need not make a perfect software, but to do a good enough software. In fact, the United States is also developing a short time.
The third question to ask is peacemaker is appropriate as a team leader. My answer is necessarily impossible. There must be strict leadership of executive power and authority, but not to understand human peacemaker.
Forty-five asked almost contradictory, if I developed something too far ahead, so we will not use it at this stage, it is a failure or a success? I think it is successful, or that the success from the very close, because this experience allows developers to accurately grasp the degree to where the market, ahead of its time while this is commendable ability.