Software Project Management Competency (Intermediate Level)

  • 24m
  • 24 questions
The Software Project Management Competency benchmark will measure your ability to recognize key terms and concepts related to key software project management concepts. You will be evaluated on project management metrics, negotiation, stakeholder analysis, scope management, and risk management. A learner who scores high on this benchmark demonstrates that they have the skills related understanding key software project management terminology and concepts.

Topics covered

  • compare internal and external stakeholders of a project
  • describe how a project business case can align the project to the organization's goals
  • describe how to classify identified risks in a project
  • describe the Agile metrics that are commonly used to evaluate Agile projects
  • describe the components of a scope statement and how to create it
  • describe the cost-benefit analysis method, which is used to determine solution that offers the most benefits for the least cost
  • describe the Failure Mode Effect Analysis method, which is used to detect errors early in the project to ensure quality
  • describe the key processes involved in managing stakeholders for project success
  • describe the process of performing user acceptance testing to validate the project outcome
  • describe the types of negotiation techniques commonly used
  • identify metrics as a tool to evaluate performance
  • identify the common types of risk in a project
  • identify the role of a project analyst in risk assessment
  • identify the various types of Agile metrics
  • recognize commonly used techniques for risk identification
  • recognize how different stakeholders can exert different influences on the project
  • recognize the effectiveness of using product vision board to define the product features
  • recognize the five stages of the negotiating process
  • recognize the importance of stakeholders in a project
  • recognize the key parameters of a project to measure
  • recognize the need to identify and gather requirements from key stakeholders
  • recognize the qualities that make a metric powerful
  • recognize the specific risks associated with a software project
  • recognize the steps involved in creating a business analysis plan