I have read a few days of books and taught us to avoid many schedule game practices. Now I will summarize them and work with you to study these practices one by one.
These practices include:
1. Use inch-Pebbles for workload evaluation
2. Make the status of the project team members visible, and urge the project members to report their status in time to help them solve the problem, rather than asking about the progress. Evaluate anything they submit and give timely feedback and comments.
3. If you must work on multiple projects at the same time, use one week of iteration to focus on a project within one week and make deliverables.
4. Implement by feature, instead of architecture-based development.
5. Develop the delivery list and ranked product backlog (requirements)
6. Use short timeboxed Iteration
7. Use the time range and percentage to describe your estimate
8. Use the speed icon to observe the project progress.
9. For unfamiliar projects and technologies, try to use Hudson Bay start to maintain the small feature made by the evaluation.
10. Evaluate and plan any project-related matters, especially the evaluation and planning work itself (more planning required)
11. ensure that project team members have field knowledge
12. Review milestone criteria with the management to ensure that the project is not off track
13. Make everyone's progress visible
based on the above practices, we can avoid many problems encountered during the project process, I will continue to learn the specific content and skills of the above practices and share them with you.
