Just recently, I have been tasked with setting up a preliminary schedule for my first real project (by the way, all of my high school English teachers are cringing because I used passive voice. That's the coolest part about working with engineers now – passive voice, schmassive voice). I have worked on other projects, but they have all been in conjunction with another, more seasoned project controller. The nature of this project is demolition and deconstruction with a lot of complicated facets. I, along with Cherie's help, worked on getting the WBS set up for this project. We got everything just right, all of the activities in place, to find out that the project manager wanted to go in a different direction. So, we created a new project, with a new WBS, new activities and resource loaded it. I proudly presented this at our team meeting later that week. By the end of the meeting, I realized that the WBS would be changing yet again. Let me point out here that the project manager on this effort is actually awesome to work with and has been very flexible. Speaking of flexibility, that brings me to my point in this week's post. I realized very quickly, that flexibility is a huge asset in project controls because things (i.e. activities, WBS's, budgets, and even baselines) change. I think this is one of things I actually like most about project controls because it keeps you on your toes.