stud
bud
Sign up
Log in
Home
Library
Explore
SAT
More
CSM Intro Flashcards | StudBud
Explore
/
CSM Intro
CSM Intro
20 terms
·
StudBud Administration
·
14 plays
Imported from external platform
Flashcards
20 cards
F
Practice quiz
P
Host live
L
Questions
20
Answers
1
What is the purpose of conducting a risk assessment in a software project?
To ignore any potential risks.
To assign blame for future problems.
To identify potential risks and develop strategies to mitigate them.
To create unnecessary paperwork.
2
How can regular communication with customers help reduce project risk and ensure their expectations are met?
By keeping customers in the dark about project progress.
By building trust, managing expectations, and addressing issues promptly.
By avoiding customer contact until the project is complete.
It can't; customer communication only adds complexity.
3
In risk management, what does the term "mitigation" refer to?
Blaming the customer for risks.
Increasing the severity of risks
Ignoring risks.
Taking actions to reduce the impact or likelihood of risks.
4
What is the purpose of a project kickoff meeting?
To celebrate the start of the project.
To confuse the project stakeholders.
To discuss unrelated topics.
To align the project team, set expectations, and define goals and roles.
5
What does the acronym "KPI" stand for in project management?
Key Performance Indicator
Key Product Information
Kindly Provide Instructions
Keep Problems Ignored
6
Explain the importance of setting clear project milestones and deadlines in managing customer expectations.
They provide clear roadmap for progress and help set realistic expectations
Milestones and deadlines are irrelevant to managing expectations
They are unnecessary for software projects
Milestones and deadlines should be kept secret from customers
7
How can account managers help customers understand the value of your software products?
By avoiding discussions about value.
By refusing to explain the product's features.
By promising unrealistic results.
By providing clear documentation and training.
8
What strategies can account managers use to align customer expectations with the capabilities of your software products?
Ignore customer expectations.
Promise everything the customer wants to hear.
Delegate the task to the development team.
Educate customers about the limitations of the software.
9
What are some common risks associated with software project delivery, and how can they be mitigated?
Scope creep
Inadequate testing
All of the above
Poor communication
10
Which of the following is NOT a best practice for managing customer expectations?
Underpromise and overdeliver.
Be transparent about any project challenges.
Avoid all communication with customers.
Provide regular project updates.
11
What is the primary goal of managing customer expectations in software projects?
To avoid all communication with customers.
Ensure customers are satisfied with the final product and project success
To confuse customers.
To make unrealistic promises.
12
Why is it important to involve customers in user acceptance testing (UAT)?
It's not necessary; customers are not qualified to test software.
To shift all testing responsibilities to the development team.
To avoid any contact with customers during testing.
To ensure that the software meets their requirements and expectations.
13
When should account managers involve the software development team in discussions with customers?
Only in emergencies.
Regularly, to ensure alignment of expectations and technical capabilities
Only at the end of the project.
Never, as developers should not interact with customers.
14
Name three key steps in the software development process that account managers should closely monitor.
Planning, coding, and debugging
Design, development, and marketing
Requirements gathering, design, and testing
None of the above
15
What role does quality assurance and testing play in reducing risk in software projects?
It doesn't affect project risk.
Ensures software meets quality standards, preventing issues in production
It slows down the project unnecessarily.
It's the sole responsibility of developers.
16
What is the purpose of a post-project review or retrospective?
To make unrealistic promises to customers.
To avoid any discussion about the project.
To reflect on what went well and what could be improved for future projects
To assign blame for any project issues.
17
What does the term "stakeholder engagement" mean in project management?
Involving stakeholders in decision-making and keeping them informed
Ignoring stakeholders' input and requests.
Keeping stakeholders in the dark about the project.
Treating stakeholders as irrelevant.
18
How can account managers address customer dissatisfaction during a project?
Blame the development team for all issues.
Listen to customer's concerns, resolve problems, and keep them informed
Ignore customer complaints.
Tell the customer that their concerns are not important.
19
How can account managers proactively identify potential risks in a software project?
By conducting regular risk assessments and monitoring project metrics.
By ignoring any signs of trouble.
By blaming the client or product team for any issues that arise.
By avoiding discussions with the development team.
20
What is the primary purpose of a Service Level Agreement (SLA) in a software contract?
To make the project more complicated.
To define agreed-upon service levels, response times and responsibilities
To protect the software company from all liabilities.
To specify the penalties for customers if they change their requirements.
