> For the complete documentation index, see [llms.txt](https://results.agilexr.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://results.agilexr.eu/1-guide-agile-teamwork-in-web-based-learning/chapter-1-agile-in-software/1.3-agile-project-management-and-practices.md).
# 1.3 Agile Project Management and practices
In the 1990s, the software industry faced significant challenges. First, it was relatively young, and there weren't enough skilled software developers available. Second, the industry relied on a strict project management approach known as "waterfall." This method prioritized creating extensive lists of requirements, often more for legal agreements than collaborating with clients. This lack of cooperation led to widespread distrust.
Additionally, software development differed from the incremental approach used today. Instead of gradual improvements, software was created in large packages. Consider software like the old Office 95, with numerous features that most people didn't use. Developing such extensive packages took years and often resulted in bugs. The Pareto Law illustrated that only around 20% of the software was utilized, leaving 80% of resources wasted.
In the traditional "waterfall" approach, a software project might take a whole year to complete without any input from the client. However, in the Agile approach, that same software gets delivered to the client every month or during a "sprint," allowing for early feedback and gradual improvements. This way, by the end of the year, you have a successful final solution.
The [Agile development process](https://www.ariadgroup.com/en/blog/all-about-scrum-Agile/details-about-scrum-Agile-components) involves several key practices. First, there's the "product backlog," which is a list of desired features and tasks for the entire year. Then, for each month, you have a "sprint backlog," which is a list of things to work on during that month. The Agile cycle happens regularly, usually every two weeks or a month, as decided by the team, and it involves steps like planning, designing, developing, testing, and releasing the software. This cycle keeps repeating, with each sprint drawing from the sprint backlog, and it leads to the delivery of the final product.
Various methods and approaches can be used to work in an Agile way. They all follow the principles and values we talked about earlier.
Some well-known [Agile frameworks in software developmen](https://www.altexsoft.com/whitepapers/Agile-project-management-best-practices-and-methodologies/)t include Scrum, Kanban, Hybrid, Lean, Bimodal, XP, and Crystal. Among these, Scrum is the most widely used.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://results.agilexr.eu/1-guide-agile-teamwork-in-web-based-learning/chapter-1-agile-in-software/1.3-agile-project-management-and-practices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.