PT M4 - Lists (Agile Methodologies)

Question 1

3 Distinctive characteristics of iterative and incremental management approaches

Answer 1

• Short Feedback Cycles
• Frequent Deliveries
• Redefinition of Priorities

Question 2

How many Values and Principles make up the Agile Manifesto?

Answer 2

4 Values

12 Principles

Question 3

The 4 Values of the Agile Manifesto

Answer 3

1. Individuals and interaction over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

Question 4

12 Principles of the Agile Manifesto

Answer 4

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple weeks to a couple of months, with a preference to the shorter timescale.
4. Businesspeople and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity, the art of maximizing the amount of work not done, is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.

Question 5

3 Questions an agile project charter should answer

Answer 5

• Why are we doing this project?
• What does finished mean for project purposes
• How are we going to work together?

Question 6

3 Typical characteristics of an agile project manager

Answer 6

• Great listener & communicator
• Attends to the needs of team members
• Promotes safety, respect, and trust among team members

Question 7

3 Roles that are applied in a project with an agile approach

Answer 7

• Team Member
• Team Facilitator
• Product Owner

Question 8

4 Typical characteristics of an agile team

Answer 8

• Mixed specialists and generalists
• Dedicated team members
• Multidisciplinary team
• Stable work environment

Question 9

In what order do servant leaders approach agile project work? (3 steps)

Answer 9

1. Purpose
2. People
3. Processes

Purpose refers to working with the team so that it clearly understands the main objective to be achieved. Once the purpose has been defined, it is necessary to work with People to create a team so that everyone can be successful, empowering people to make a good team. Finally, the Process is addressed. Since in agile environments processes are continually changing and must be defined or adjusted based on purpose and people, this is the final stage.

Question 10

In what order do servant leaders approach predictive project work?

Answer 10

1. Purpose
2. Process
3. People

This would be the approach of a predictive project leader, where the process is more important than the person and the team. However, in agile approaches, people and the team are ones that facilitate adaption to change.

Question 11

2 things that need to be clear among members of an agile team before starting work

Answer 11

• Team Values

- Ground Rules

Question 12

2 Charts used in agile projects to track progress

Answer 12

• Burn Down &

- Burn Up Charts

Question 13

The 3 Statuses that can appear on a Scrum Board

Answer 13

• Open
• In Progress
• Done

All the tasks that have not begun by the team will appear as Open. This means that no work has been carried out related to these tasks. All the tasks that the team is currently working on (and which have not yet been finished) will appear as In Progress. The tasks that have been completed will appear as Done.

It is important to note that even if tasks are nearly finished, they will stay in the in-progress status until they are entirely completed. It is an error to consider a task as nearly done, even if there appears very little left to do. This is because setbacks can occur at the end of a task that can cause delays.

Question 14

3 techniques used to bring the principles of agile methodology to an entire company or organization

Answer 14

• Scrum of Scrums
• Scaled Agile Framework (SAFe)
• Large Scale Scrum (LeSS)

Question 15

3 Elements that must be indicated in the tasks to be carried out by the team during an iteration in an agile project

Answer 15

• Effort
• Person in Charge
• Description of the task

Question 16

In an agile project using work cycles or iterations, what order should meetings be held?

Answer 16

1. Planning Meeting
2. Daily Stand Up Meeting
3. Review Meeting
4. Retrospective Meeting

Question 17

3 advantages of placing team members in the same physical workspace

Answer 17

• It improves communication between team members.
• The time required to make changes is minimized.
• It avoids organizational silos.

Question 18

What is attained when a team is empowered to improve their value flow?

Answer 18

• Tasks are finished earlier
• Less time is spent on unnecessary tasks
• Collaboration between team members improves

Question 19

Who manages the Product Backlog and the Iteration Backlog?

Answer 19

• Product Backlog: The Product Owner in collaboration with the Client
• Iteration Backlog: The Team

Question 20

Which elements appear on a Kanban Board?

Answer 20

• Work in Progress (WIP)
  (indicates the number of tasks that can be in the same state simultaneously). Tasks can only be advanced into another state when there is a gap for them in the state they are moving into.
• Statuses that tasks go through
  (It is possible that not all the tasks go through all the status states).
• Team member responsible for each task