Friday, August 15, 2008
New Blog Coming!
Thursday, August 14, 2008
Project Management Advice for Start-Ups or Small Businesses (aka the basics for getting started)
1. Define your projects- Start with a simple list that includes what you are delivering, when you want to deliver it by and who is responsible for it.
2. Understand tasks- Once you have a solid list of projects start thinking about what high level tasks are required to complete the projects. Identify who is responsible for each task. Also note which tasks have to happen before another or tasks that can occur simultaneously.
3. Analyze your staff- Look for names that show up a lot on your lists or areas where you don't have a name assigned.
4. Analyze your dates- Look for periods of time where there is a lot going on for everyone or just one person.
5. Check your budget- Make sure the above analysis matches your budget or what you are charging for the project.
The steps above should really give you a good idea of where you stand with your projects and how you balance them. It should also help you discover where and what your risks are. Being aware of your risks is very important and the first step in preventing them from becoming problems.
To improve your application of project management, there are two additional things I recommend doing.
6. Analyze how your team works- Observe how your team gets stuff done. You have a current process, no matter how informal it is. Watch for how things go wrong and right. Listen to what people directly and indirectly say about the process.
7. Learn about project management software and practice- At least read a bit about it and think about how it could help you. And start using it when you find that you need it and are ready to adopt it in your process.
There is a ton of information out there about project management as a discipline. However, I find that bringing it down to these simple steps not only helps someone unfamiliar to it, but also helps to prevent practitioners like me from turning it into a mindless bureaucracy.
Wednesday, August 13, 2008
Personal Branding and My Brand
This makes me reflect on my own personal brand. Not because I need one, but because I am someone with an online personality. But I don't like to think of it as a brand. I just want to think of it as an accurate representation of me. Nothing strategic, just me.
Maybe I am off base. I would love to talk more about this with people.
So, in my reflection on personal brand I did a bit of soul digging. Here are a few core things about me:
* I love technology. I am particularly interested in how new advancements change our culture, use and approaches to developing technology. Getting an opportunity to explain this stuff to people is great.
* I like adventures. Through travel or outdoor activities, adventures provide the perfect balance and perspective in my life.
* I like to be organized. I like to see how I can be more effective and efficient.
* I like art. Anything aesthetically pleasing with meaning.
* I like to help and inspire people, especially in regard to technology.
* I love to learn anything about and related to any of the above.
Does that make a brand? I guess it is more of a list of interests that drive my actions that represent me. Hopefully, this comes through all of my other posts. But would anyone argue that a representation of one's interests is still lacking the extra strategy that is fundamental to a personal brand?
Wednesday, August 06, 2008
Requirements Writing
However, for smaller projects it is still a good idea to apply the fundamentals of requirements.
Things to think about:
* requirements are What not How
* stepping through use scenarios helps
* assumed functionality requirements are the most dangerous
* coming back to ultimate goals is key to having a full set
* use previously made scope decisions as hard limits
* again, what not how
Thursday, July 31, 2008
A Rant On Requirements
Well, this is where I feel the pressure as the program/project manager. The responsibility to make sure we have a comprehensive set falls on me. I am comfortable with this - yet this is where it is crucial that I know my scope and stakeholders before beginning the requirements gathering process. So, if you ever participate on a program or project team, please be patient through the initial steps. You may know your stuff, but the PM needs to get that information from you as well as possible.
Let me know if you want a 3,000+ requirements document to chill with and I will send you a link ;)
Tuesday, July 29, 2008
You Need Project Manangement
I have been around the DC tech community for almost 2 years and I want to get some discussions going about how to get stuff done more efficiently and effectively. I don't mean anything too formal or process heavy. I mean some simple application of the project management theories that work.
Email me, liz[at]the315[dot]com, if you want to talk about project management with me. This is what I do for a day job and I actually enjoy it.
Friday, July 18, 2008
Direct from the Philippines
Its been an amazing trip so far. But that's not all that I wanted to write about.
I love technology. I have had access to all of my regular addictions and conveniences. If it wasn't for the change in content and strange times, no one would know I was really halfway across the world. The only thing I couldn't do was attend the Twin Tech event. I hope it was as much fun as it sounded!
Photos to come.