Final Exam: Software Project Lead - compare internal and external stakeholders of a project
- define business analysis
- define key terms associated with risk assessment
- define project risk
- describe how a project business case can align the project to the organization's goals
- describe how flow diagrams can be used to improve project processes
- describe how negotiation skills can improve conflict resolution within teams
- describe how the feasibility study tool helps determine whether a solution is practically achievable or not
- describe how the roles and responsibilities matrix can be used to specify ownership of project activities among team member
- describe how to classify identified risks in a project
- describe key techniques used for collecting stakeholder requirements
- describe methods of negotiating effectively
- describe the Agile metrics that are commonly used to evaluate Agile projects
- describe the best ways to present information gathered using metrics
- describe the Cause and Effect Analysis method, which is used to resolve issues early in the project to ensure efficient processes
- describe the commonly used tools to document requirements
- describe the commonly used tools to effectively communicate with stakeholders
- 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 different types of stakeholder needs
- describe the Failure Mode Effect Analysis method, which is used to detect errors early in the project to ensure quality
- describe the five types of negotiating
- describe the importance of negotiation skills in project management
- describe the importance of the tasks performed by a project analyst in ensuring the success of a project
- 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 risk register tool used to manage risks
- describe the types of negotiation techniques commonly used
- describe typical business analyst activities
- describe ways to overcome hurdles during negotiations
- differentiate between quality assurance and quality control, with a specific focus on business analysis
- identify how a project analyst benefits from using negotiation skills within the project team
- identify the common types of risk in a project
- identify the key components of a business case document
- identify the key strategies used for managing risks
- identify the need to reassess the effectiveness of a metric
- identify the role of a project analyst in risk assessment
- identify the various types of Agile metrics
- recognize commonly used methods for generating ideas
- recognize commonly used techniques for risk identification
- recognize how different stakeholders can exert different influences on the project
- recognize qualitative and quantitative methods to assess risks
- recognize the benefits of using collaborative negotiation to bring about a win-win situation
- recognize the correct way to evaluate using metrics
- recognize the details required to define a metric
- recognize the effectiveness of the empathy map for communicating user preferences to the project team
- recognize the five stages of the negotiating process
- recognize the importance of analyzing data to provide insightful information
- recognize the importance of assessing competition
- 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 need to track defects through reviews
- recognize the qualities that make a metric powerful
- recognize the specific risks associated with a software project
- recognize the steps involved in a negotiation
- recognize the steps involved in creating a business analysis plan
- recognize the technique of asking probing questions to get clarity on stakeholder requirements
- recognize the ways to effectively handle difficult stakeholders
- specify the need to set benchmarks for effective metrics
|
