Well, every job is a project with requirements so I'm managing micro projects with very clear and defined requirements. Smaller scope means that you either do what you're asked or you don't get paid - simple.
The great thing about small projects vs bigger stuff is that in a small project you see the end and the benefits very quickly, so it gives you confidence that some of the bigger ones are also going to pay off and be worthwhile - especially if you have a similar methodology and approach for both.
Even though I'm doing some small stuff in my spare time, I still apply some science to the work - e.g. I fixed a leak and took moisture readings before the repair so that I can check that the repair has been successful at a later date. So basically pre and post metrics on benefits.
With the confidence to operate robustly at a small level - accounts, invoicing, contracts, scope, client management, communications, estimating, installation, etc. it all adds to the delivery on bigger projects, where I feel more confident on calling BS on people who don't complete tasks, paperwork, RAMS, etc. It's not difficult, you're just being lazy!
Anyhow, it all adds up to a better PM/BA experience for people I work with/for, so what's not to like?
Please feel free to comment. What do you do that improves your PM/BA role?
No comments:
Post a Comment