A large part of this site is dedicated towards software project management. I get a lot of question how this differs from general IT project management. Actually, it doesn't. In 90% of IT projects, software makes up a large part of the effort. Next to, hardware, networks, and other infrastructure related components. So, in a sense IT project management has a broader scope.
However, the general techniques, outlines, and processes are the same. By focusing my course on software projects I can put emphasis on typical application software related issues, like user requirements, but that's all. If you are looking for a IT project management guide, I highly recommend my course.
Related Posts
3 Steps Towards Becoming An Agile Project Manager
Why is this basically the same… I need to go a step back to explain this properly.
Recent years a lot of complains about current project management practices have emerged. Methods are too rigid, too centralized in respect to planning, etc. (good examples of these methods are PMP and Prince 2) This even has resulted in a new breed of methods, agile a.k.a. light weight a.k.a. lean methods. Examples for project management are Last Planner (construction) and SCRUM (software development).
However, the replacement of one normative method for project management by another may not me the answer to the problems projects are faced with. Different circumstances may require a different approach. If you need creativity to solve a problem or to create a design, you need an easy going, stimulating approach; if you are running towards a deadline to get in to production, a rigid, centralized controlled environment is more the way to go. Depending on the environment and general circumstances a project manager should construct a process and organization that serves him or her best.
Key question is "what make up the circumstances?" Without hesitation I would say "people". In my personal experience all major problems concerning projects are caused by human stuff. Intuitively I would state that the source of the trouble lies within the interest of the individuals and (the lack of) information/knowledge. As humans are controlled by their own fears and wishes, it's more then logical that if they are working under a project, they use the same mechanism.
And it is just this assumption that form the basis of The Microwave Way to Software Project Management. See, the subject is software, the application area very general.
Leave a Reply