In this section of Software Engineering – Software Project Management.It contain Software Project Management Concepts MCQs (Multiple Choice Questions Answers).All the MCQs (Multiple Choice Question Answers) requires in depth reading of Software Engineering Subject as the hardness level of MCQs have been kept to advance level.These Sets of Questions are very helpful in Preparing for various Competitive Exams and University level Exams.

Practice it now to sharpen your Concepts


. Effective software project management focuses on
  • people, performance, payoff, product
  • people, product, performance, process
  • people, product, process, project
  • people, process, payoff, product
. Organizations that achieve high levels of maturity in people management have a higher likelihood of implementing effective software engineering processes
  • True
  • False
. The first step in project planning is to
  • determine the budget.
  • select a team organizational model.
  • determine the project constraints
  • establish the objectives and scope
. Process framework activities are populated with
  • milestones
  • work products
  • QA points
  • all of the above
. Project management is less important for modern software development since most projects are successful and completed on time
  • True
  • False
. Which of the following is not considered a stakeholder in the software process?
  • customers
  • end-users
  • project managers
  • sales people
. The best person to hire as a project team leader is the most competent software engineering practitioner available
  • True
  • False
. The best project team organizational model to use when tackling extremely complex problems is the
  • closed paradigm
  • open paradigm
  • random paradigm
  • synchronous paradigm
. Which factors should be considered in choosing the organizational structure for a software team?
  • degree of communication desired
  • predicted size of the resulting program
  • rigidity of the delivery date
  • size of the project budget
  • a, b, c
. One of the best ways to avoid frustration during the software development process is to
  • give team members more control over process and technical decisions
  • give team members less control over process and technical decisions.
  • hide bad news from the project team members until things improve.
  • reward programmers based on their productivity.
. Small agile teams have no place in modern software development.
  • True
  • False
. Which of these software characteristics is not a factor contributing to project coordination difficulties?
  • interoperability
  • performance
  • scale
  • uncertainty
. Which of these software characteristics are used to determine the scope of a software project?
  • context, lines of code, function
  • context, function, communication requirements
  • information objectives, function, performance
  • communications requirements, performance, information objectives
. The major areas of problem decomposition during the project scoping activity are the
  • customer workflow
  • functionality to be delivered
  • process used to deliver functionality
  • software process model
  • b and c
. Product and process decomposition occurs simultaneously as the project plan evolves.
  • True
  • False
. When can selected common process framework activities be omitted during process decomposition?
  • when the project is extremely small in size
  • any time the software is mission critical
  • rapid prototyping does not require their use
  • never the activities are invariant
. How does a software project manager need to act to minimize the risk of software failure?
  • double the project team size
  • request a large budget
  • start on the right foot
  • track progress
  • c and d
. The W5HH principle contains which of the following questions?
  • Why is the system being developed?
  • What will be done by whom?
  • Where are they organizationally located?
  • How much of each resource is required?
  • a, c d
. Which of these are critical practices for performance-based project management?
  • assessing product usability
  • defect tracking against quality targets
  • empirical cost estimation
  • formal risk management
  • b, c, d

You may be interested in:
Software Engineering Online Tests