PSM 2 EXAM 2023 ACTUAL EXAM TEST BANK COMPLETE
EXAM 400 QUESTIONS AND CORRECT DETAILED ANSWERS
WITH RATIONALES|ALREADY GRADED A+(PASSING SCORE
800)
I prefer to describe 'Agile' in terms of the following key characteristics that are
common to the portfolio of Agile methods: - ANSWER: ■ People driven;
Agile is driven by the continuous collaboration of people ranging over all required
departments; whether they are called business, IT, marketing, sales, customer
service, operations or management. People are respected for their creativity,
intelligence and self-organizing capabilities.
■ Facilitation;
Agile replaces the traditional command-and-control mechanisms of assigning
individuals on a daily basis with executable micro-tasks.Agile teams are facilitated
by servant-leadership. Boundaries and a context for self-management exist, upon
which teams are given objectives and direction.
■ Iterative-incremental process;
Products are created piece by piece ('incremental') The built pieces and the total
product are frequently revisited ('iterative') to assure overall integrity.
■ Measuring success
Agile makes it explicit that success and progress in software development can only
be determined by frequently inspecting working software and the actual value it
holds for the people who will have to use it.
■ Change.
Even when requirements and implementations are predicted in an upfront way,
they are prone to change.Agile encourages change as a source of innovation and
improvement.
Agile software development is driven by - ANSWER: business and business
opportunities.All work is reorganized to respond to and enable that business
opportunities can be capitalized on.
'Value' is the answer to business opportunities and the overall measure of progress
and success. - ANSWER: Value is an internal assumption within the organization
until the software is actually released to the marketplace. Releasing software on
the marketplace is the only way to validate this assumption.Releasing software on
the marketplace regularly is the only way to adapt to the feedback and
appreciation of the marketplace.
Value is continuously increased across iterations and risk is controlled by - ANSWER:
consecutively producing working increments based upon defined engineering
standards
, Technical perspective on risk (Will the system perform? Is it scalable?) often ignores
the fact that the ultimate goal of software development is - ANSWER: to provide
greater satisfaction to end-users and customers, to endure that software product is
useful.
The Agile software development process should address the risk - ANSWER: of not
being able to capitalize on unforeseen and previously unknown market
opportunities, of not releasing the software product fast enough,being subject to
customer dissatisfaction e.g. by releasing untested software, the risk of releasing
features that are not what users expect or appreciate etc.
High-value needs are answered first. - ANSWER: Software products, versions and
releases are released quickly and frequently.They get users to pay for the software
and optimize the stakeholders' return. They are of high quality in order to
minimize maintenance and support.
Agile understands the core purpose of the 'normal' IT activities: - ANSWER: Analysis,
Design, Coding and Testing/Integration), but breaks the sequential organization of
these. The goal of such an integrated, cross-functional approach is to build in
quality and to prevent defects, rather than attempt to establish quality by a bug
hunting approach in a post-development phase.
Agility is the state of - ANSWER: High responsiveness, speed and adaptiveness,
while controlling risks.It serves to better deal with the unpredictability so common
to the work of software development and to the markets that organizations
operate within.
■ Agility can't be planned; ■ Agility can't be dictated; ■ Agility has no end-state. -
ANSWER: Agility in itself is much more than following a new process. It is about
behavior, it is about cultural change.In a transformation towards an Agile way of
working, there is no way of predicting what change needs will be encountered at
what point in time, how these will be dealt with and what the exact outcome will
be in order to control next steps.
A time-planned way for an Agile transformation ignores the essence of Agile, -
ANSWER: that of dealing with complexity via well-considered steps of
experimentation and learning.
Agility has no end-state. - ANSWER: Time-plans create the illusion of deadlines and
a final end-state.
A practice to identify structural waste is Value Stream Mapping. - ANSWER: All steps
and phases in the process of going from 'idea' to 'cash' are set out on a timeline.
Activities may be labeled as 'valuable' or as 'non-value adding', but possibly also as
necessary although not directly value-adding.
EXAM 400 QUESTIONS AND CORRECT DETAILED ANSWERS
WITH RATIONALES|ALREADY GRADED A+(PASSING SCORE
800)
I prefer to describe 'Agile' in terms of the following key characteristics that are
common to the portfolio of Agile methods: - ANSWER: ■ People driven;
Agile is driven by the continuous collaboration of people ranging over all required
departments; whether they are called business, IT, marketing, sales, customer
service, operations or management. People are respected for their creativity,
intelligence and self-organizing capabilities.
■ Facilitation;
Agile replaces the traditional command-and-control mechanisms of assigning
individuals on a daily basis with executable micro-tasks.Agile teams are facilitated
by servant-leadership. Boundaries and a context for self-management exist, upon
which teams are given objectives and direction.
■ Iterative-incremental process;
Products are created piece by piece ('incremental') The built pieces and the total
product are frequently revisited ('iterative') to assure overall integrity.
■ Measuring success
Agile makes it explicit that success and progress in software development can only
be determined by frequently inspecting working software and the actual value it
holds for the people who will have to use it.
■ Change.
Even when requirements and implementations are predicted in an upfront way,
they are prone to change.Agile encourages change as a source of innovation and
improvement.
Agile software development is driven by - ANSWER: business and business
opportunities.All work is reorganized to respond to and enable that business
opportunities can be capitalized on.
'Value' is the answer to business opportunities and the overall measure of progress
and success. - ANSWER: Value is an internal assumption within the organization
until the software is actually released to the marketplace. Releasing software on
the marketplace is the only way to validate this assumption.Releasing software on
the marketplace regularly is the only way to adapt to the feedback and
appreciation of the marketplace.
Value is continuously increased across iterations and risk is controlled by - ANSWER:
consecutively producing working increments based upon defined engineering
standards
, Technical perspective on risk (Will the system perform? Is it scalable?) often ignores
the fact that the ultimate goal of software development is - ANSWER: to provide
greater satisfaction to end-users and customers, to endure that software product is
useful.
The Agile software development process should address the risk - ANSWER: of not
being able to capitalize on unforeseen and previously unknown market
opportunities, of not releasing the software product fast enough,being subject to
customer dissatisfaction e.g. by releasing untested software, the risk of releasing
features that are not what users expect or appreciate etc.
High-value needs are answered first. - ANSWER: Software products, versions and
releases are released quickly and frequently.They get users to pay for the software
and optimize the stakeholders' return. They are of high quality in order to
minimize maintenance and support.
Agile understands the core purpose of the 'normal' IT activities: - ANSWER: Analysis,
Design, Coding and Testing/Integration), but breaks the sequential organization of
these. The goal of such an integrated, cross-functional approach is to build in
quality and to prevent defects, rather than attempt to establish quality by a bug
hunting approach in a post-development phase.
Agility is the state of - ANSWER: High responsiveness, speed and adaptiveness,
while controlling risks.It serves to better deal with the unpredictability so common
to the work of software development and to the markets that organizations
operate within.
■ Agility can't be planned; ■ Agility can't be dictated; ■ Agility has no end-state. -
ANSWER: Agility in itself is much more than following a new process. It is about
behavior, it is about cultural change.In a transformation towards an Agile way of
working, there is no way of predicting what change needs will be encountered at
what point in time, how these will be dealt with and what the exact outcome will
be in order to control next steps.
A time-planned way for an Agile transformation ignores the essence of Agile, -
ANSWER: that of dealing with complexity via well-considered steps of
experimentation and learning.
Agility has no end-state. - ANSWER: Time-plans create the illusion of deadlines and
a final end-state.
A practice to identify structural waste is Value Stream Mapping. - ANSWER: All steps
and phases in the process of going from 'idea' to 'cash' are set out on a timeline.
Activities may be labeled as 'valuable' or as 'non-value adding', but possibly also as
necessary although not directly value-adding.
