Agile Methodology Features

C.

The correct answer is C: It uses an iterative approach, backlogs, and burndown charts.

Agile methodology is a project management approach that emphasizes flexibility, collaboration, and continuous improvement. It is used in software development, but also in other industries that require a fast and adaptable approach.

Here are some of the key features of Agile methodology:

1. Iterative approach: Agile methodology is based on the idea of breaking a project down into smaller, more manageable chunks called iterations or sprints. Each iteration is a mini-project with its own goals and deliverables. This approach allows for more frequent feedback and course correction, as well as faster delivery of working software or products.

2. Backlogs: Agile projects are driven by a product backlog, which is a prioritized list of features, requirements, and user stories that the team will work on during each iteration. The backlog is constantly reviewed and refined, with items being added or removed as needed.

3. Burndown charts: A burndown chart is a visual representation of the progress of an Agile project. It shows how much work has been completed and how much is left to do, and helps the team stay on track and identify potential issues early on.

4. Collaboration: Agile methodology values teamwork and collaboration. The team includes not only developers, but also stakeholders, product owners, and customers. Everyone is encouraged to communicate openly and work together to achieve the project goals.

5. Flexibility: Agile methodology is designed to be adaptable and responsive to change. The team is expected to embrace change and adjust their plans and priorities as needed to meet evolving requirements or new information.

In contrast, options A, B, and D describe features that are not typically associated with Agile methodology. Option A describes a more traditional, waterfall approach to project management that relies heavily on Gantt charts and a ticketing system. Option B suggests a less structured and less collaborative approach that relies on spreadsheets and change request documents. Option D describes a step-by-step approach that may not allow for the flexibility and iteration that is central to Agile methodology.