3 March 2010
On project management blogging
And many of us are talking around the same themes and ideas. For example, many of us rail against bureaucracy or bloated control processes at the expense of the team’s motivation, enthusiasm and desire to get things done.
Frankly, I have to question myself about the value of this blog today. Am I still contributing, or is this space just another part of the internets noise?
Way back when this blog was in it’s infancy I decided to focus on the role of the business analyst rather than on project management, to provide it some sort of differentiation from the project blogs that were already out there. But today there are plenty of outstanding BA blogs.
And my focus has broadened beyond my initial focus into scrum and technical pm practices, mainly because these are the things I am working on and thinking about as I go.
So, what’s in it for me these days?
I don’t seek to monetise this blog (although I have added some affiliate links) and I haven’t tried to leverage my online reputation in my day job.
On the other hand I do get to engage in some interesting discussions with my peers around the world, which I don’t get to do with my peers in the building. And by engaging in a professional community I get to learn.
I also force myself to articulate ideas in relatively clear language, which for me is important. I haven’t yet tackled the really important discussion – which is about dialogue with sponsors and stakeholders. Sometimes I think the project blogging community is all about project teams talking to themselves in a closed environment. That’s not really what we are about.
Sometimes I also think that the PM and BA blogs are operating in two different worlds. One a couple of occasions I have asked questions in PM and BA forums what the readers think about the other role, but usually just get a generic answer that, at least to me, says the answers aren’t really thinking about the potential conflict and collaboration embedded in the partnership.