As this is being published, I am in the midst of enjoying the vacation that, in these blog posts, I am planning. Behold, the power of modern technology! Time travel! With any luck, I have remembered to turn work emails off on my phone and am currently enjoying the heaven that is Minnesota in June without any disturbances. I might be camping by Lake Superior even as you read this.
OK. So I know I told you in the last entry that this one would be about how proficient I suddenly am at using Microsoft Project. Alas, epic tales of my success at jumping into Project 2010 will have to wait. Apparently, I was putting the cart a little bit ahead of the horse.
As I was watching Dux's video primer on using Microsoft Project, he said that he, as a programmer, first fired up Project intending to conquer it the first time he looked at it. You know, kind of like I promised to do in my last post. He also said that Project kind of assumes that you're familiar with some of the fundamentals of the PM process. Which, as an IT guy, he was not. He says, at about 10:30 in the screencast, that once he opened up Project, he just kind of stared at it for a couple of hours, not really knowing exactly what to do with it.
Suddenly, I don't feel quite as stupid as I did before. If even Dux, who is now a PM rock star, grappled with Microsoft Project the first time he looked at it, then maybe I'm not the complete moron I was beginning to think I might be.
But I'm not avoiding my project! OK, so I'm not rolling up my sleeves and becoming an instant Microsoft Project guru, but I'm finished with philosophies and avoidance for the moment. I'm doing the thing.
Watching Dux's screencast, I realized that before I do anything with Microsoft Project, I needed to create a WBS. A WBS is a Work Breakdown Strategy, and it is one of the very first things you do when you're planning out a project. Dux discusses how to develop a WBS in a screencast called Project Planning 101. When I was chatting with him about it after realizing I needed to do this before I do anything in Project, Dux described a WBS as a "brain dump." You just throw in all the things you need to do in order to make your project happen so you can see all the various components and contingencies of your project laid out before you. You're not organizing it, you're not ordering it, you're not arranging it – you're just brainstorming all the stuff you're gonna need for your project to come together.
So I sat down with old skool pen and legal pad and drew out a basic WBS for my vacation. Once I decide to take a vacation, what steps should I take to make it happen, from conception to stepping off the plane? Dux recommends using a mind map, but for very simple projects, you can probably just make a list. Like on a napkin or something, if you don't have a legal pad handy.
My particular WBS goes a little something like this (a-one and a-two and...)
- Select location
- Select accommodations (for me, steps 1 and 2 go hand-in-glove: a friend in Minnesota invited me to come see her and stay with her, and thus my vacation was born)
- Book flight
- Send friend flight itinerary
- Research and plan activities
- Create packing list
- Do laundry
- Research airport parking (because I don't travel often, I have never used the long-term parking at the airport, and I don't know how to do it)
- Research luggage limits and parameters (really, I should get out of the house more often. I know nothing about how to travel any way but by car)
- Pull cash for trip
- Put together documentation/paper for trip (driver's license, plastic money, paper money, itinerary)
- Go to airport
- Turn off work email on the phone so I am truly, blissfully disconnected from civilization
- Fly off into the wild blue Minnesota
- Begin an awesome week of vacation with my friend
For you, your vacation WBS might include getting a pet-sitter, stopping your newspaper, arranging to have someone drop you at the airport so you don't have to pay for long-term parking, and other items pertinent to your own vacation (project). It's vacation season, so why don't you play along, if you're new to Project 2010, too?
We are not, in fact, the only people who have used Project to plan a vacation. Arpan Shah, who used to be the Director of Microsoft Project and is now a Director on the SharePoint Project Management Team over at Microsoft, planned a three-month sabbatical using Project Professional. I am doing it for practice, because my trip is simple and I already know what few things I need to do, but Arpan's Project plan was both real and practical.
I have only just begun paying attention to my WBS, so as I watch the screencasts more, I may have more items to add to it. In fact, I almost certainly will, because I am forgetful. Some of my tasks will have sub-tasks. Some of my tasks may have dependencies (which is the relationship between the tasks and what needs to be done when, if I'm understanding correctly). I am going to finish watching Dux's screencasts and then sit back down with my WBS, add whatever squiggles it needs, and then, maybe, I'll be ready to plug some of this data into Microsoft Project.
Jun 05 2012, 09:30 AM
| Edit this post
Pamela Flora is currently the Marketing and Administrative Coordinator for the D.C.-area office of Innovative-e, Inc., where she has worked since March 2011. She has previously enjoyed work in both the public and private sectors as a technical writer, as well as taking the occasional freelance gig. While her current duties encompass a plethora of tasks both mundane and complex, they did not include project management until recently, when she was given the opportunity to explore project management from an in-the-trenches POV and document the experience in this blog. In her spare time, Pamela likes to hang out with her five kids, paint, write, spend quality time with her DSLR, and, now, read project management books. Though she is only infrequently on Twitter, you may follow her there just in case she feels compelled to tell you what she had for breakfast and you feel the strong desire to know: @puckish222.