Few Important Notes on Domain Questions by Eng. Mahmoud
Nassar
تم تسجيلها على عدة مراحل سواء قبل أو بعد اجتيازي.. Domains هذه بعض المالحظات على السبع
..لالختبار و بمناقشات عدة مع الزمالء الذين اجتازوا االمتحان
Domain أو قبل حل أسئلة كل6يفضل المرور عليها قبل حل االمتحانات
Domain I. Agile Principle and mindset Notes:
1. The goal of agile leadership is to create an empowered and motivating work environment in
which people want to do what needs to be done.
2. Kanban teams use their WIP limits to control the number of items that can be in a given stage of
work at a time.
3. “Code standard” is an XP concept, not a Scrum concept; while a scrum team might use such
standards, and possibly even list the code standards themselves wouldn’t be included in backlog
list.
4. A phased and gated approach is associated with Waterfall. Phases are strictly linear sequences of
activities to build a product or deliver a project.
5. Planning and estimating during a feasibility stage is focused on determining value to the
customers by asking questions like, “What should we build?” As the project progresses past the
feasibility stage, the cost, the budget, and the overall project schedule become clearer and easier
to control.
6. Continuous integration Small batches of the source code are checked in, the control system
initiates a full build, a suite of automated is run, and developer is notified electronically of any
code compilation failures
7. ‘Barely sufficient’ is the agile term used to describe the approach of doing only as much as is
necessary to accomplish the work without including non-value added activities.
8. Cycle time = work in progress / throughput.
9. The scrum value of commitment states ‘Because we have great control over our own destiny, we
are more committed to success’
10. Wireframes assist the project’s development by laying out content and functionality so the
project has a visual structure and basis for development.
11. The rule of engagement, also known as ground rules or working agreements, provide structure
and boundaries for how team members.
, 12. The Scrum master is responsible for teaching others how to use the Scrum process to deal with
every new complexity encountered during a project.
13. Agile approach is an umbrella term that includes a diverse number of Agile methods, practices,
and techniques.
14. Every project is unique, but projects all have different requirements, uncertainty, and risk.
15. As uncertainty and risk for a project increase, teams select project delivery life cycles ranging
from Predictive (non-Agile) approaches to Agile approaches.
16. The Agile Practice Guide identifies four types of project life cycle. Projects should assess these to
determine the best approach for project characteristics.
17. Predictive life cycles take advantage of high certainty around requirements, a stable team, and
low overall project risk. These projects are executed in a serial manner.
18. Incremental life cycles optimize work to deliver value to customers more often than a single, final
product.
19. The practice guide represents a bridge to understanding the pathway from a predictive approach
to an agile approach
20. The practice guide goes beyond addressing the use of agile in the computer software
development industry
21. Agile techniques and approaches effectively manage disruptive technologies.
22. The first principle of agile places customer satisfaction as the highest priority and is key in
delivering products and services that delight customers
23. In order to stay competitive, organizations can no longer be internally focused but rather need to
focus outwardly to the customer experience.
24. Definable work projects are characterized by clear procedures that have proved successful on
similar projects in the past.
25. High-uncertainty projects have high rates of change, complexity, and risk.
26. Iterative life cycles are optimized for speed of delivery. They focus on frequent delivery of smaller
deliverables.
27. Agile and Kanban are subsets of Lean. This is because they are named instances of lean thinking
that share lean concepts as: ”focus on value, small batch sizes, & elimination of waste”.
28. Agile manifesto values
a. Individuals and interactions over processes and tools
Nassar
تم تسجيلها على عدة مراحل سواء قبل أو بعد اجتيازي.. Domains هذه بعض المالحظات على السبع
..لالختبار و بمناقشات عدة مع الزمالء الذين اجتازوا االمتحان
Domain أو قبل حل أسئلة كل6يفضل المرور عليها قبل حل االمتحانات
Domain I. Agile Principle and mindset Notes:
1. The goal of agile leadership is to create an empowered and motivating work environment in
which people want to do what needs to be done.
2. Kanban teams use their WIP limits to control the number of items that can be in a given stage of
work at a time.
3. “Code standard” is an XP concept, not a Scrum concept; while a scrum team might use such
standards, and possibly even list the code standards themselves wouldn’t be included in backlog
list.
4. A phased and gated approach is associated with Waterfall. Phases are strictly linear sequences of
activities to build a product or deliver a project.
5. Planning and estimating during a feasibility stage is focused on determining value to the
customers by asking questions like, “What should we build?” As the project progresses past the
feasibility stage, the cost, the budget, and the overall project schedule become clearer and easier
to control.
6. Continuous integration Small batches of the source code are checked in, the control system
initiates a full build, a suite of automated is run, and developer is notified electronically of any
code compilation failures
7. ‘Barely sufficient’ is the agile term used to describe the approach of doing only as much as is
necessary to accomplish the work without including non-value added activities.
8. Cycle time = work in progress / throughput.
9. The scrum value of commitment states ‘Because we have great control over our own destiny, we
are more committed to success’
10. Wireframes assist the project’s development by laying out content and functionality so the
project has a visual structure and basis for development.
11. The rule of engagement, also known as ground rules or working agreements, provide structure
and boundaries for how team members.
, 12. The Scrum master is responsible for teaching others how to use the Scrum process to deal with
every new complexity encountered during a project.
13. Agile approach is an umbrella term that includes a diverse number of Agile methods, practices,
and techniques.
14. Every project is unique, but projects all have different requirements, uncertainty, and risk.
15. As uncertainty and risk for a project increase, teams select project delivery life cycles ranging
from Predictive (non-Agile) approaches to Agile approaches.
16. The Agile Practice Guide identifies four types of project life cycle. Projects should assess these to
determine the best approach for project characteristics.
17. Predictive life cycles take advantage of high certainty around requirements, a stable team, and
low overall project risk. These projects are executed in a serial manner.
18. Incremental life cycles optimize work to deliver value to customers more often than a single, final
product.
19. The practice guide represents a bridge to understanding the pathway from a predictive approach
to an agile approach
20. The practice guide goes beyond addressing the use of agile in the computer software
development industry
21. Agile techniques and approaches effectively manage disruptive technologies.
22. The first principle of agile places customer satisfaction as the highest priority and is key in
delivering products and services that delight customers
23. In order to stay competitive, organizations can no longer be internally focused but rather need to
focus outwardly to the customer experience.
24. Definable work projects are characterized by clear procedures that have proved successful on
similar projects in the past.
25. High-uncertainty projects have high rates of change, complexity, and risk.
26. Iterative life cycles are optimized for speed of delivery. They focus on frequent delivery of smaller
deliverables.
27. Agile and Kanban are subsets of Lean. This is because they are named instances of lean thinking
that share lean concepts as: ”focus on value, small batch sizes, & elimination of waste”.
28. Agile manifesto values
a. Individuals and interactions over processes and tools
