Forum Replies Created

Viewing 15 posts - 1,171 through 1,185 (of 1,483 total)
  • Author
    Posts
  • in reply to: Agile Question 21 #5822
    admin
    Keymaster

    Correct answer is D.

    Transparent communication allows the project stakeholder to see the whole picture of the project, its status, progress, roadblocks, and helps them make informed decisions.

    All Agile Questions & Answers: Questions & Answers

    Learn Agile Concepts : Agile Concepts

    Agile Tips & Tricks : Agile Tips & Tricks

    Quiz: 20 Questions Challenge

    in reply to: PMP Question 57 #5821
    admin
    Keymaster

    Correct answer is D.

    Transparent communication allows the project stakeholder to see the whole picture of the project, its status, progress, roadblocks, and helps them make informed decisions.

    Pass PMP in the First Attempt : PMP Strategy

    All PMP Question & AnswersQuestion & Answers

    Revise PMP ConceptsPMP Concepts

    PMP Tips & TricksPMP Tips & Tricks

    Quiz:
    20 Questions Challenge
    50 Questions Challenge

    in reply to: Agile Question 20 #5668
    admin
    Keymaster

    Correct answer is A.

    In Agile, team members are responsible to put plans and components together.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: PMP Question 56 #5667
    admin
    Keymaster

    Correct answer is A.

    In Agile, team members are responsible to put plans and components together.

    Pass PMP in the First Attempt : PMP Strategy

    All PMP Question & Answers: Question & Answers

    Revise PMP Concepts: PMP Concepts

    PMP Tips & Tricks: PMP Tips & Tricks

    Quiz:
    20 Questions Challenge
    50 Questions Challenge

    in reply to: PMP Question 55 #5662
    admin
    Keymaster

    Correct answer is B

    As per Risk-Value Quadrant (Agile Requirements Prioritization Scheme)
    Do First – High Value and High Risk
    Do Second – High Value and Low Risk
    Do Third – Low Value and Low Risk
    Avoid – Low Value and High Risk

    Main point is high risk items need to be get off as early as possible because they can derail the whole project. If it is of low value we can ignore it. But if it is of high value then it should be done first so that if we fail then atleast we fail early to save time and effort.

    Pass PMP in the First Attempt : PMP Strategy

    All PMP Question & AnswersQuestion & Answers

    Revise PMP ConceptsPMP Concepts

    PMP Tips & TricksPMP Tips & Tricks

    Quiz:
    20 Questions Challenge
    50 Questions Challenge

    in reply to: Agile Question 19 #5660
    admin
    Keymaster

    Correct answer is B

    As per Risk-Value Quadrant (Prioritization Scheme)
    Do First – High Value and High Risk
    Do Second – High Value and Low Risk
    Do Third – Low Value and Low Risk
    Avoid – Low Value and High Risk

    Main point is high risk items need to be get off as early as possible because they can derail the whole project. If it is of low value we can ignore it. But if it is of high value then it should be done first so that if we fail then atleast we fail early to save time and effort.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Procurement Management Question 1 #5654
    admin
    Keymaster

    The correct answer is B.

    Private conversations are inappropriate regarding bids status. All communications with bidders should be open to all parties to have fairness in the process.

    Pass PMP in the First Attempt : PMP Strategy

    All PMP Question & AnswersQuestion & Answers

    Revise PMP ConceptsPMP Concepts

    PMP Tips & TricksPMP Tips & Tricks

    Quiz:
    20 Questions Challenge
    50 Questions Challenge

    in reply to: Agile Question 18 #5635
    admin
    Keymaster

    Correct answer is A.

    When we add a new feature to the project, it isn’t added to the top of the backlog or completed as soon as possible; instead, it is prioritized and inserted at the appropriate place in the backlog. .Since agile projects typically fix cost and time and allow scope to vary, it’s unlikely that more time and money would be added to the project. So of these options, the MOST likely one is that the lowest-priority feature would be dropped from the backlog. However, often that feature wouldn’t actually be removed; it would just drop down further in the backlog, making it increasingly less likely to be completed.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Agile Question 17 #5633
    admin
    Keymaster

    Correct answer is C.

    Value Add Time = 2 hours = 120 mins
    Non-Value Add Time = 2 + 8 = 10 mins
    Total Cycle Time = 120 + 10 = 130 mins

    Process Efficiency = 120 / 130 = 92%

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Agile Question 16 #5631
    admin
    Keymaster

    Correct answer is D.

    It is true that burn up charts can be converted to cumulative flow diagrams by the addition of WIP, and they trend in the opposite vertical direction from burn down charts. It is also true that burn up charts that also track total scope (rather than burn down charts) separate out the rate of progress from the scope fluctuations. So the option that is not true is “Burn down charts indicate whether rate of effort changes are due to changes in progress rates or scope.”

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Agile Question 15 #5629
    admin
    Keymaster

    Correct Answer is D.

    Personas do represent real, stereotyped, composite, and fictional people. They are archetypal (exemplary) descriptions, grounded in reality, goal-oriented, specific, and relevant to generate focus. Personas are not a replacement for requirements on a project.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Agile Question 14 #5627
    admin
    Keymaster

    Correct answer is B.

    This is a case where product owner is right, and the team member is doing something that is potentially dangerous. The reason that scrum have a product owner role is so that someone can stay on top of all stakeholder communications. There is nothing wrong with the team member working directly with stakeholders, but they should Never cut the product owner out of the discussion.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: Agile Question 13 #5625
    admin
    Keymaster

    Correct answer is A.

    Limiting WIP means work has to be completed in that stage before new work can be pulled from the previous stage.

    Learn Agile Concepts : Agile Concepts

    Agile Blog : Agile Blog

    in reply to: PMP Question 54 #5623
    admin
    Keymaster

    Correct answer is A. When we add a new feature to the project, it isn’t added to the top of the backlog or completed as soon as possible; instead, it is prioritized and inserted at the appropriate place in the backlog. Since agile projects typically fix cost and time and allow scope to vary, it’s unlikely that more time and money would be added to the project. So of these options, the MOST likely one is that the lowest-priority feature would be dropped from the backlog. However, often that feature wouldn’t actually be removed; it would just drop down further in the backlog, making it increasingly less likely to be completed.

    Pass PMP in the First Attempt : PMP Strategy

    All PMP Question & AnswersQuestion & Answers

    Revise PMP ConceptsPMP Concepts

    PMP Tips & TricksPMP Tips & Tricks

    Quiz:
    20 Questions Challenge
    50 Questions Challenge

    in reply to: Integration Management Question 1 #5621
    admin
    Keymaster

    Questions are updated but not frequently. I publish whenever it gets updated.

Viewing 15 posts - 1,171 through 1,185 (of 1,483 total)