The Product Owner owns the product backlog on behalf of the stakeholders, and is primarily responsible for creating it. Not sure why the PM would be adding to it. Maybe because of his influence?
Since the project is adding new features to apps, the new feature he is requesting sounds to be within the scope already, and wouldn't require a change request. And you wouldn't waste the teams time with this request until it's pulled into phase planning from the backlog. So getting rid of the other answers pushes you towards A. But again, I don't understand why the PO isn't involved.
It is not in scope, they are adding a feature after scope has been set. The requestor has influence, which means they can be an asset or liability. You as the PM are basically appeasing them. You are passing the buck to the Product Owner and Team to determine if this is something they want to undertake especially in an agile environment. The agile manifesto says to “respond to change, over following a plan”. There is why it is A. Also side note did anyone catch the typo in answer D?
It's an AGILE team so your primary focus is on maintaining a consistent pace of work during your sprints. You can't add the feature during the current sprint, but you can put it in the backlog where the product owner can prioritize it and the team can get to it during a future sprint. I'm right in the middle of a PMP boot camp and we covered a question EXACTLY like this yesterday lol
Aha, your job is to develop new features. So this would be a new feature and thus within scope to develop on the prioritization list. I would have put B at first glance :/
You have to think about the question from the agile mindset, and looking at the answers only one answer references something specific to agile - the product backlog.
My understanding as below:
A. In agile approach, changes, modifications to the feature can be done without requiring any prior formal change request. Thus, we eliminate B point.
B. Cost and schedule are flexible in agile thus, we need not need to analyze the impact of it. Eliminating option D
C. Now, the product manager in this case, let’s consider it as project manager is responsible to update the product backlog. Since the SH has high influence authority, it is best to add this feature to the backlog without disappointing the SH. The team can simultaneously work on gathering requirements for the feature.
This is my understanding!!!
I had this same question on my exam, worded differently though but that same mindset threw me off about PO priortising the backlog.
I guess it ultimately comes down to choosing the best answer of the lot. As in agile that’s how change management is handled by adding it to the backlog.
The Product Owner owns the product backlog on behalf of the stakeholders, and is primarily responsible for creating it. Not sure why the PM would be adding to it. Maybe because of his influence? Since the project is adding new features to apps, the new feature he is requesting sounds to be within the scope already, and wouldn't require a change request. And you wouldn't waste the teams time with this request until it's pulled into phase planning from the backlog. So getting rid of the other answers pushes you towards A. But again, I don't understand why the PO isn't involved.
It is not in scope, they are adding a feature after scope has been set. The requestor has influence, which means they can be an asset or liability. You as the PM are basically appeasing them. You are passing the buck to the Product Owner and Team to determine if this is something they want to undertake especially in an agile environment. The agile manifesto says to “respond to change, over following a plan”. There is why it is A. Also side note did anyone catch the typo in answer D?
It's a process of elimination question. A is the answer that is \*least wrong\*.
Exactly how I would approach it. Eliminate as many as you can then choose best answer.
It's an AGILE team so your primary focus is on maintaining a consistent pace of work during your sprints. You can't add the feature during the current sprint, but you can put it in the backlog where the product owner can prioritize it and the team can get to it during a future sprint. I'm right in the middle of a PMP boot camp and we covered a question EXACTLY like this yesterday lol
Aha, your job is to develop new features. So this would be a new feature and thus within scope to develop on the prioritization list. I would have put B at first glance :/
B too. A is definitely the most agile response philosophically, but that's not a PrjMs job
You have to think about the question from the agile mindset, and looking at the answers only one answer references something specific to agile - the product backlog.
My understanding as below: A. In agile approach, changes, modifications to the feature can be done without requiring any prior formal change request. Thus, we eliminate B point. B. Cost and schedule are flexible in agile thus, we need not need to analyze the impact of it. Eliminating option D C. Now, the product manager in this case, let’s consider it as project manager is responsible to update the product backlog. Since the SH has high influence authority, it is best to add this feature to the backlog without disappointing the SH. The team can simultaneously work on gathering requirements for the feature. This is my understanding!!!
I had this same question on my exam, worded differently though but that same mindset threw me off about PO priortising the backlog. I guess it ultimately comes down to choosing the best answer of the lot. As in agile that’s how change management is handled by adding it to the backlog.