1 A detailed requirements analysis
2 When faced with problems at the beginning of a project, you need to face up to and deal with these difficult and controversial issues and should not run away
3 Choose the right technology The
right technology gives you the best chance at There's no benefit in picking a new technology that catches your eye, especially when you can't guarantee that it's going to be beneficial or you ca
n't to apply it correctly.
4 Design the structure of a product, which should have good modularity and be easy to understand. Take the time
to design functional modules and interfaces, and encapsulate and organize those modules and interfaces5
Once you know what you will need to do, you can start preparing the project plan.
6 Review tenders, contracts and other high-level documents related to the project.
If your plan shows that the contract is not enforced, then renegotiation is necessary to avoid serious problems later
7 Check the design and code
8 Prioritize
a.) Make sure to focus on the most urgent things first, and the most important second If there is still time left to do less important things. It's important to prioritize things from the customer's perspective.
b.) Ensure that the problem is adequately resolved.
9 Dealing with changes in demand
No matter how small the change is, you need to do the necessary processing and report the result of this change back to the customer or the marketing
department . Project delays More precisely people often think that projects will be delayed and don't expect to do more without more time and resources.
10 Getting people to work hard and tactfully is the crux of the matter.
It's better to name a delivered product by time and function than just by number.
You should trust the group to the members, that they understand what needs to be done, and will go all out to do it well.
11 Risk Reduction
a.) Do not use new technical languages or methods just to use them.
b.) Try to avoid mixing different languages or technologies.
C.) Reduce dependencies on other projects and organizations
d.) Include adequate workarounds in the project plan.
Project delays are often due to some major risk factors, such as the failure of a new technology or a delay in the delivery of the product by the supplier.
12 Do not do useless work. If you can COPY some useful functions, you don't have to rewrite them.
13 Adopt a solid programming style
a.) Apply the most advanced warning function in the development tool.
b.) Apply error checking tools to find memory leaks, generic code errors and other potential flaws.
c.) Make it a habit to test immediately after writing the program.
d.) Write down the program errors tested and write a report.
e.) Use reliable structures and algorithms.
14 Reduce the length of the Design-Program-Test cycle.
15 Spend time on testing.
16 Regular product releases.
The more feedback you get, the less likely your customers will end up rejecting your product.
17 To prevent delays in your projects, you must take responsibility for leadership and lead effectively.
a.) Take responsibility, don't blame others, don't make excuses, have the courage to admit mistakes and improve.
b.) Don't let others blame and don't make excuses that don't speak up.
c.) In order for the entire project team to work smoothly, you must do things that leaders should do, even if they are not pleasant.
d.) If you know what the problems are, work on them immediately instead of ignoring them.
e.) The person who wants to have a big picture of the whole project
18 Must be willing to spend time in order to save time.
If you have a way to save time for the entire project, go for it, although it may temporarily put work behind schedule.
2 When faced with problems at the beginning of a project, you need to face up to and deal with these difficult and controversial issues and should not run away
3 Choose the right technology The
right technology gives you the best chance at There's no benefit in picking a new technology that catches your eye, especially when you can't guarantee that it's going to be beneficial or you ca
n't to apply it correctly.
4 Design the structure of a product, which should have good modularity and be easy to understand. Take the time
to design functional modules and interfaces, and encapsulate and organize those modules and interfaces5
Once you know what you will need to do, you can start preparing the project plan.
6 Review tenders, contracts and other high-level documents related to the project.
If your plan shows that the contract is not enforced, then renegotiation is necessary to avoid serious problems later
7 Check the design and code
8 Prioritize
a.) Make sure to focus on the most urgent things first, and the most important second If there is still time left to do less important things. It's important to prioritize things from the customer's perspective.
b.) Ensure that the problem is adequately resolved.
9 Dealing with changes in demand
No matter how small the change is, you need to do the necessary processing and report the result of this change back to the customer or the marketing
department . Project delays More precisely people often think that projects will be delayed and don't expect to do more without more time and resources.
10 Getting people to work hard and tactfully is the crux of the matter.
It's better to name a delivered product by time and function than just by number.
You should trust the group to the members, that they understand what needs to be done, and will go all out to do it well.
11 Risk Reduction
a.) Do not use new technical languages or methods just to use them.
b.) Try to avoid mixing different languages or technologies.
C.) Reduce dependencies on other projects and organizations
d.) Include adequate workarounds in the project plan.
Project delays are often due to some major risk factors, such as the failure of a new technology or a delay in the delivery of the product by the supplier.
12 Do not do useless work. If you can COPY some useful functions, you don't have to rewrite them.
13 Adopt a solid programming style
a.) Apply the most advanced warning function in the development tool.
b.) Apply error checking tools to find memory leaks, generic code errors and other potential flaws.
c.) Make it a habit to test immediately after writing the program.
d.) Write down the program errors tested and write a report.
e.) Use reliable structures and algorithms.
14 Reduce the length of the Design-Program-Test cycle.
15 Spend time on testing.
16 Regular product releases.
The more feedback you get, the less likely your customers will end up rejecting your product.
17 To prevent delays in your projects, you must take responsibility for leadership and lead effectively.
a.) Take responsibility, don't blame others, don't make excuses, have the courage to admit mistakes and improve.
b.) Don't let others blame and don't make excuses that don't speak up.
c.) In order for the entire project team to work smoothly, you must do things that leaders should do, even if they are not pleasant.
d.) If you know what the problems are, work on them immediately instead of ignoring them.
e.) The person who wants to have a big picture of the whole project
18 Must be willing to spend time in order to save time.
If you have a way to save time for the entire project, go for it, although it may temporarily put work behind schedule.