Summary PMI-ACP EXAM : VERY IMPORTANT PIONTS UPDATE
0 view 0 purchase
Course
PMI
Institution
PMI
Understand Then Understand For Understating Then Practicing The Exam
1. You should understand the Roles and Responsibilities of Agile Practitioner -Product Owner
-Scrum Master/Agile Coach/Team Lead, Development team and Sponsor.
2. Many questions as an agile practitioner what you will do in thes...
Very important points on PMI-ACP Exam: -
Understand Then Understand For Understating Then Practicing The Exam
1. You should understand the Roles and Responsibilities of Agile Practitioner -Product Owner
-Scrum Master/Agile Coach/Team Lead, Development team and Sponsor.
2. Many questions as an agile practitioner what you will do in these situations.
Such as: As a Scrum Master what should be your action? -- As a Product Owner what should
be your action? -- As a Development Team what should be your action?
3. Any question asking “what should have been done” for a case with faulty result, therefore considering
preventive actions was necessary.
4. Agile practitioner embraces the idea of Refactoring which means Cleans up the code to make it: – Simpler–
Easier to understand – Adhere to standards – Future work
5. As the company starting to introduce agile to its employees. It is always better to balance teaching principles
with Agile practices and make them be agile not just doing it.
6. In exam there are no much mathematical questions one or two questions.
7. Broken Comb is a person who has various depths of specialization in multiple skills required by the team.
8. Behavior-Driven Development (BDD) involves a system design and validation practice that uses test-first
principles and English-like scripts
9. A Business Requirement Document (BRD) lists all requirements for a specific project.
10. Changes may change the prioritize list in the product backlog and may bump out some priorities from the list.
11. Some questions on Prioritization (T&T) Moscow, Kano model, Dot Voting and Risk value quadrant, Also
Estimation(T&T) -Planning Poker and Affinity
12. Important terms and topics Osmatic communication &Co-Located team, Value stream map, Kanban board,
burndown chart, information radiator, interpersonal skill, servant leadership, product backlog refinement,
issues, risks, project charter, WIP and Spike
13. There has to be a minimum of three teams to apply the Scrum of Scrums method; two base teams plus an
overarching team
14. KanBan Boards are pull systems 1-They visualize the project 2- They are sign boards 3-KanBan in Japanese
means “cards you can see.
15. If the customer wants you to add new high important requirements to the next iteration. Then, it is
recommended to review the current planned stories and check if the high risky with low value story can be
removed.
16. If the story is complex and cannot be completed within the time-box of one iteration, the story should be
sliced. Whether the story should be replaced with another one, or should the developer consult with the team
only or with the team and product owner
17. If there are bugs found later in the accepted work, these should be treated as new stories but it is a priority
call taken by product owner whether to add these in current iteration or later
18. You can calculate your efficiency using (Value Stream)
19. Minimal Marketable Feature (MMF) can increase the ROI.
20. Cadence means rhythm of execution. Time-boxing is one specialized form of cadence. The time box of a
sprint helps to create a regular cadence for the development team, management team, customer, etc. This
rhythm helps to keep everyone in sync and keep the process moving.
21. Technical debt is a major problem in may products that is generally because of poor agile practices followed.
Agile practices focus on the reduction of technical debt and there are three main proactive practices that can
be followed for the same purposes. These practices increase technical excellence with good code design by
implementing refactoring and using automated testing tools. Including technical debt reduction user stories in
the backlog is a reactive methodology. In this, technical debt is already incurred in user stories and user stories
have been completed for eliminating the debt. Therefore, it is the least likely approach that you should
recommend to improve the quality of the upcoming projects as an agile practitioner.
22. You are selecting interpersonal skill from the following ones to use. Within your team (Communication or
Leadership). Best answer is communication as sometimes they define Interpersonal skills as communication
between two or more people
23. Refactoring: A change that is made to the internal structure of software to make it easier to understand and
cheaper to modify without changing its observable behavior ,Also is changing code, without changing its
functionality, to make it more maintainable, easier to read, easier to test, or easier to extend. Also is a
technique for restructuring an existing body of code by improving/simplifying its internal structure (design)
without changing its external behavior. Also, is one of the principal techniques for managing technical debt.
(A technique to improve external functionality.)
24. Technical debt can arise during initial development, ongoing maintenance (keeping a product at its original
state), or enhancement (adding functionality).( All Times)
25. During sprint If there is potential problem or risk usually contact Product Owner.
26. During Sprint If there is Significant /essential or major risk, contact Stakeholder
27. Question about: disagreement on the requirement, someone say it is there and another say it is not there and
it is not meeting the requirement (Definition of Done)
28. While you are presenting the demo, it was not accepted as it is not meeting the requirements (acceptance
Criteria)
29. When new stakeholders engage the project, the agile practitioner need to learn how the current project may
be affected by these stakeholders.
30. A Fishbowl window is a long-lived video conferencing link between various locations. People start the link
at the beginning of a workday and close it at the end. In this way, people can see and engage spontaneously
with each other, reducing the collaboration lag otherwise inherent in the geographical separation. An effective
communication tool may reduce the risk of scope creep but doesn't reduce the project scope. This might
increase the direct project costs (due to the use of technology) but, at the same time, might reduce the indirect
project costs (due to efficient WIP management).
31. The document in Agile are barely sufficient. (In Agile writing heavily, documentations are not the right way
to deal with challenges).
32. The team augmentation arrangement is regarded as the most collaborative contracting approach as this
embeds the supplier's services directly into the customer organization. Funding teams instead of a specific
scope preserves the customer's strategic discretion on what work should actually be done.
33. Your team made an innovative way to implement the solution in a new way. Should the team directly
implement it or check it with the product owner
- One case team should directly implement it as team is self-organized and self-directed
- Another case you will need to return back to the case will clear it Fully
34. In case when there are issues/risks/dependencies/ changes. After describing the case ask you for the solution
and you see in the answer (Describe or explain to the customer working software is better than compressive
documentation or other agile values) Usually those are Trap questions make sure you understand it very
good as the answer in many case is not that direct choice. Sometimes implement the solution or discuss the
solution with the customer or the product owner before you implement it.
35. If senior manager is asking for many reports –Educate him that the agile working software is over
comprehensive documentation OR Refer him to the information radiator.
36. When you read the following words / phrases, pay special attention as the answer choices may not be correct:
change management-create a plan / amend a plan-assign tasks/scope creep-escalation-report and
documentation-baseline-Monte Carlo, regression analysis, etc.
37. The following words will guide you to eliminate this option such as:
assigned (tasks / user stories) – escalate (the situation) – the very nature of the Agile team formation (with Product
Owner / Customer co-located) makes escalation of issues much less than traditional project management
plan – Agile projects seldom create lots of project management plan upfront- documentation – though Agile
highly favors working software, it is perfectly okay to create documentations that are barely sufficient, don’t rule
out creating documentation as a possible task- direct, instruct, request, Force, push (by the project leader) the
leader is often a servant leader and would seldom assume a “command and control” position
38. The following words will guide you to select this option such as (Motivate, Assist, Self-organized, high
value, in last responsible moment, guide, support, help, Innovate etc.)
39. If team member came with innovative idea and ask for permission to make it. Then ask you what you will do:
Support him & let him try it in the next iteration.
40. If team member is overloaded and is thinking that the work has no end. (To give him a break or to give him
vacation)
41. Product Owner is not needed to attend sprint regular meetings. Only some of them. The retrospective meeting
is used to check what went well in the last sprint and enable improving for next iteration also it is an
opportunity for the team to inspect itself and create a plan for improvements to be enacted during the next
sprint.
42. As agile coach you reward and recognize innovative failure. Its ok to fail as long as team learn and improve.
43. Agile, Encouraging the generalizing specialist, not overtime to avoid lack of resources.
44. If there are too many interruptions to the team, you need as an agile practitioner to work toward shield team
from distractions.
Issued by Eng. Wagdy Azzam _2020 Ver.0 Mob. 00966 556239052
PMP®, (PMI-RMP) ®, (PMI-ACP), PMO-CP,6Sigma, SFC™
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller THEEXCELLENCELIBRARY. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $11.99. You're not tied to anything after your purchase.
