Over the last week, we’ve been discussing the strengths and weaknesses of managers vs more technically capable resources such as architects in their role of managing software projects. We’ve had quite a vibrant debate on this topic and i feel it is a very positive step for us in looking beyond our own limited world views.
If we were to breakdown what it is exactly that a person in charge of a software project does, then maybe we can figure out where the strengths and weaknesses specifically lie in each case. This will not only help you appreciate what it takes to manage a project, but also, if you are in a management role, to identify which skillsets you might need to brush up on.
Project Management Body of Knowledge (PMBOK) issued by the Project Management Institute, the backers of the PMP certification, says that project management can be thought of as nine (9) distinct areas which need to be managed. These are Integration, Scope, Time, Cost, Quality, HR, Communications, Risk and Procurement. These nine knowledge areas are managed over five stages of the project which are initiating, planning, executing, controlling and monitoring and closing.
Over the next couple of weeks, we’ll be looking into each of the areas and the skill sets required as pertaining to the Pakistani software industry.For now, I’d like to put forward a question to everyone of you reading this post. Which of the nine knowledge areas do you think are most applicable to us and why? Please remember that applicability is different in the case of startups and established firms, so please mention the context when presenting your views.