| Topic : Perspectives on Agile Development |
|
|
|
|
Activity:
Question posted: 02 20 2009 20:08:38 +0000,
3 answers, 395 views, last activity
07 06 2010 20:18:08 +0000
|
|
This person is easily identified in small software development house.
But in larger organisation, the competence is shared by PM, SSA,BA, SA, Developer, SQA, etc.
The difficulty : when there is a problem (any problem related to Project), the answer-finding is a group process rather than single person's judgement, which make it difficult since I believe responsibility must fall down to one person.
In term of title, PM is the one, but is it true? What is the characteristics of good PM? Should he/she an all-round person? Should he/she technically sound enough to take decision?
What is your opinion ?
thanks,
Pankaj Dwivedi
Hi pankaj,
I do readily admit that it is a very difficult job & quite frankly its a royal pain......
Few of the important characteristics are: -
- To complete projects on schedule, within budget, and with all requirements met.
- AS quality is not achieved by accident. Quality must be planned for and tracked to ensure project goals are achieved.
the focus on political leadership makes it seem somewhat remote from the world of business and software.
- Familiar with the application of standards but able to adapt them to the project and environment as appropriate
- Disciplined and organized but flexible
- Familiar with the project details without getting mired in them
- Willing to accept the expertise of others
- Has a good understanding of the organizational politics but does not play political games
- Always holding themselves as accountable as they hold others
- Credible and honest
A "project" manager must have a technical background, but more germane is the ability to lead people who are IT professionals. This is the primary criterion above any other set of measurements.
Project Management is stressful, time consuming, challenging, and down right frustrating, but an awful lot of fun mate....
Hi Pankaj,
I think management and techinical ability does not gel together well. A guy managing a project will always think about delivery of a project in time, costs, time sheet etc..etc. But a technical guy will think in an entirely different path. He knows what he is doing on the technical part of a software. The problem arises when we have to stike a balance between technical and managerial aspects of a project. For me there should a Techinal Guy heading a development team and a management guy should closely monitor the team sitting in sidelines taking inputs from the leads and facilitating time management and project management for the leads. This will help the technical leads to concentrate more on what is required in core product. I know this will not work in full in service companies where time and cost comes above innovative thinking and product qualilty but will (and is) definitely work for product companies.
Vinay
Hi Pankaj, I feel a Good PM should have the capabilities of managing the Team, Customer,and shouldn't show any partiality towards a particular person. He should be able to listen to all the voices and should have the capability of judging the right solution, instead of listening to a single or few.He should definetly follow the hierarchy level while administering and even should be technically or functionally good or else, atleast should be in a position to analyse the technicality,so that a proper Time Management could be done.

- Create a confidential Career Profile and Resume/C.V. online
- Get advice for planning their career and for marketing of experience and skills
- Maximize awareness of and access to the best career opportunities
|
|
|
|
|
|
|
|
|
|
|
|
What is the Best Profile to Lead Software Development Team? |
I am working in AGILE for last 18 month using VersionOne tool. For me AGILE means develop and deliver the code in a smart way to the customer. But agile needs atleast 12-14 hours of work at offshore . |