Free IBM 000-188 Exam Dumps Questions & Answers

The following is an example of a user story: s a hiring manager, I need a web form to enter results of my interview with the candidate. If I decided not to hire the candidate, I need to email the?s a hiring manager, I need a web form to enter results of my interview with the candidate. If I decided not to hire the candidate, I need to email the recruiter so that he/she can call the candidate. If I decided to hire the candidate, I need to open an MS Word template and draft an offer for employment? What feedback should the program manager give on the user story?

• A.  It is a good user story because it leaves out all implementation details as to how the work will actually get done.
• B.  It is a good user story because it maintains a clear definition of what the hiring manager needs to accomplish and why.
• C.  It is poorly written user story because it documents what the user needs to do.
• D.  It is a poorly written user story because it specifies implementation details.

A development team is preparing Playback 2. The Playback includes system integrations. When preparing for a playback, what should the program manager do? Advise the development team to:

• A.  warn stakeholders with possible technical problems in advance.
• B.  use power point slides with screenshots.
• C.  postpone the playback if a technical problem is found.
• D.  create a script and practice the playback.

Within a business process application, access to business data in other systems is accomplished via:

• A.  connection lines between Business Process Definition (BPD) activities.
• B.  exposed process variables.
• C.  integration service.
• D.  tracking points

The BPM Program Manager, Process Owner, and Lead Developer are collaborating to define the theme and assign user stories for the next iteration. The team is planning the 7th of 15 iterations in the Release Plan for Release One. The Program Manager displays a Team Velocity chart showing that the Development team has shown significant growth in story points accepted from iterations 1 to 4 and has been leveling off to roughly 200 story points in iterations 5 and 6.
Given there are 9 iterations remaining in the release plan, the Process Owner immediately recognizes there is room for roughly 1800 story points in the remaining time for Release One. However, the backlog contains 2400 story points marked as "high" priority and another 1200 story points marked as "medium" priority. The Process Owner asks to reduce the points assessed to the high priority user stories to bring the total points down to roughly 1800 so as to make them fit in the remaining time. The Program Manager agrees.
What is wrong with this scenario?

• A.  Process Owner forgot to include a risk factor of 1.4 that should be applied to 1800 resulting in roughly 2500 story points (1.4 x 1800 = 2520) remaining in the Release. No action should be taken.
• B.  Team Velocity is fixed and changing the method of estimating story points mid-way through a release will not increase the scope of work that can be completed.
• C.  This is a conversation for a Release Planning meeting and not during Iteration Planning.
• D.  Both "high" and "medium" priority stories should be included in the Release Plan meaning all user story points should be reduced by 50% to get all high/medium priority stories to fit in 1800 points remaining (2400+1200 = 3600 : 3600/2 = 1800).

A program manager asks a developer to create a document describing the solution features that end user and system administrators needs to be aware or in order to deploy and use the process application. The developer tells the program manager that documentation is not a deliverable for any playback. The program manager responds by telling the developer that documentation required to enable later developers is a deliverable for which of the following playbacks?

• A.  Playback 2
• B.  Playback 3
• C.  Playback 0
• D.  Playback 1