The WBS is a key factor in the completion and success of a project. As we learned in class, the WBS defines the scope of the project and any changes made to the WBS will affect the scope of the project and vice versa. If we didn't have the detailed WBS for the project up front, I wouldn't know exactly how to allocate resources for each period. To think that a PM is responsible for developing a workable WBS project, using techniques such as Top-Down and Bottom-Up, is very impressive and impressive. I also learned the importance of budget allocation. As noted earlier, I had some budgeting issues throughout the simulation. Even though I was over budget, like everyone else in the class, I wasn't too far off. Finally, I learned the importance of anticipating the timeline to make decisions. The value of reviewing upcoming activities is a good practice for a PM to ensure they will be ready when the time comes. By analyzing two to three periods in advance, I was able to anticipate and track my resources and expenses, especially in periods where parallel tasks were being performed. It wasn't perfect 10/10 feedback but it's still useful.