Object Oriented Software Engineering   View all facts   Glossary   Help

subject > person or group > person > stakeholder > project manager

project manager (development manager)
subject			fact

project manager	is a synonym of development manager
	acts as a mentor
	bases cost estimate on The number of use cases The number of distinct requirements The number of classes in the domain model The number of widgets in the prototype user interface An estimate of the number of lines of code
	has definition The person responsible for performing project management tasks
	determines how the plans need to change, and takes action to keep the project on track
	directs people to appropriate sources of information
	directs subordinates and contractors
	does not perform activities such as hiring, building morale, and issuing the final directions if there is a departmental manager to do them instead
	ensures that hardware and software is available
	ensures that people always have somebody to talk to about problems
	ensures that people feel rewarded, respected and motivated
	ensures that people have the requisite security clearance
	estimates the amount of time that will be required to complete the project
	estimates the cost of the system which involves studying the requirements and determining how much effort they will take to design and implement
	finds customers
	finds office space
	fires people who are not performing adequately
	gives advice about engineering problems
	gives people feedback to help them improve their work
	has activities Deciding what needs to be done Estimating costs Ensuring there are suitable people to undertake the project Defining responsibilities Scheduling Making arrangements for the work Directing Being a technical leader Reviewing and approving decisions made by others Building morale and supporting staff Monitoring and controlling Co-ordinating the work with managers of other projects Reporting Continually striving to improve the process
	has goal to please the customer or sell the most software, while spending the least money
	helps people solve problems by leading discussions
	helps employees resolve inter-personal conflicts
	hires employees
	initiates the paperwork involved in hiring or subcontracting
	is a subtopic of 11.1 - What is Project Management?
	is part of software development team
	is a kind of stakeholder
	makes high-level decisions about requirements and design
	may be judged on when they deliver product, not on its quality level
	may not be familiar with small details of the project
	must have knowledge about how to manage software projects
	must realize that the vicious circle of software reuse exists and costs money - in order to save money in the longer term, an investment in reusable code is justified
	negotiates contracts
	often has education in business administration
	often uses lines of code to give an intermediate cost estimate that people can easily understand although you usually cannot accurately base cost estimates on lines of code until you have almost completed design
	performs project management
	plans work schedule
	runs the organization that is developing the software
	selects the overall processes that will be followed
	sets up training courses
	should allow time to re-engineer part or all of the system periodically
	should be realistic in initial requirements gathering
	should develop a close relationship with other members of the team so that he or she is more keenly aware at all times about the progress achieved, and the potential risks
	should encourage all necessary communication between team members
	should ensure that everybody understands the position of everybody else, the costs and benefits of each alternative, and the rationale behind any compromises
	should ensure that everybody's proposed responsibility is clearly expressed
	should follow an iterative approach
	should improve cost estimation skills so as to account for the kinds of problems that may occur
	should learn how to run effective meetings
	should listen to everybody's opinion
	should make sure that everybody has the information they need
	should make sure that project information is readily available for browsing, e.g. using an Intranet web site
	should monitor communication between team members
	should realize that attention to quality of reusable components is essential so that potential re-users have confidence in them
	should realize that developing and reusing reusable components improves reliability, and can foster a sense of confidence
	should realize that developing reusable components will normally simplify the resulting design, independently of whether reuse actually occurs
	should reward software developer for developing reusable components
	should take assertive action, when needed, to ensure progress occurs
	should take courses in negotiating skills, leadership, written and oral communication
	should take into account a realistic assessment of the resources available when determining the requirements and the project plan
	should use 'groupware' technology to help specific groups of people exchange the information they need to know
	takes the ultimate legal responsibility for declaring that proper engineering practice has been followed, and that the manager believes the resulting system will be safe
	tells customers and higher-level managers what they need or want to know
uses cost-benefit analysis to choose among alternatives
wants software that sells more and pleases customers while costing less to develop and maintain
works with customers to determine their problem and the scope of the project
stakeholder	must agree on requirements
person	can understand requirements better if they are expressed in terms of use cases

Next stakeholder: software developer    Up: stakeholder    Previous stakeholder: customer