So why do we need another project management blog?
It’s a good question.
Part of the answer is that I’ve reached the stage where I want to help people get better at delivering projects, particularly ones with software as a major component.
Another part of the answer is that I’ve spent much of my professional life trying to define what project management means to me: writing for myself, writing processes, procedures etc for my customers and employers, and implementing project management concepts in my own tools. I have boxes of notes and notebooks from over the years that document my bright ideas, brain explosions and WACI’s (Wild and Crazy Ideas).
Through this blog and my other writings, I want to share my experience and my thinking about project management. I want to find ways to interact with people who face the same problems that I have (do) in delivering projects of this type.
What’s my background?
I’ve been fortunate to have a very wide range of experience in the technology industry, which gives me a perspective on project delivery that is perhaps not common amongst my peers.
I’ve spent nearly 40 years building software-based solutions, and although much of it has been in Project Management roles, it’s by no means been a continuous activity.
Although the bulk of my experience chain has been in Project Management, I’ve also included roles in Software development, Professional Services Sales, Startups, Business Development, Product Management, Solutions Lead and Resources Manager.
The common interest has been in finding and delivering the solution outcomes based primarily on software technology and more specifically, it has been about building products destined for use by an end-user, mostly a consumer end-user.
The operating domain has almost always been in some high-growth area: PC’s in the 80’s, Telco’s in the 90’s, Internet in the 00’s and Digital Content in the 10’s. This context has always been “Software product development in a ‘Big Damn Hurry’”.
No schedule or launch date that I’ve ever proposed has been soon enough, the level of chaos has always been high, and new or revised requirements have cascaded down like hailstones on a tin roof.
I’ve always been fascinated by the process of software development and the way in which people interact with each other in such a domain of “hurry up”: where standing still is going backwards.
What can you expect?
First and foremost, you’ll get Adam Russell. Whilst there may be content driven by other blogs, books and people, the bulk of it will be my thinking on the subject.
I like to write long: to give thorough and considered treatment to a subject or concept. So there will be a mix of shorter blog posts and so-called “long read” articles that cover a point of professional interest for me.
Although written in a lightweight and sometimes irreverent style, the content is serious: I’ve considered it seriously and developed it slowing over time; and this content addresses serious aspects of the project management practice as it exists today. that’s my style: I work in an irreverent way, but I am deadly serious about getting things done right.
Please read and comment, even if (or perhaps especially if) you don’t agree.
My goal is to engage you and have a dialog.
Please let me know what you think.