Project management is a job that I find challenging and fulfilling, especially when one considers the various methodologies and philosophies that exist around managing software development projects. There’s no “one way” to approach project management. We have many tools in our toolbox and evaluate each project to determine how best to approach it.
It’s part art, part science, and all communication.
We are light on process, but value the processes we do have in place and follow them in all projects consistently across the company.
When people ask us how we manage our projects we are very upfront in saying that our methods cater to our environment/experience and may not be suitable for other companies. But with that said, we’re more than happy to share what we do and the things we’ve learned.
And that’s why I’m writing this blog series.
There are several unique topics I’d like to write about. Throwing them all into a single post would just be too long. Instead, I’m writing a series with each post dealing with a different aspect. In upcoming posts I will talk about how we handle release planning, design our software, plan iterations and hold daily standups, the value of post-release retrospectives, and our values/practices in general.