Table of contents
Open Table of contents
Lessons Learned
This section will help you to learn about the history, approach, and philosophy of Agile project management and Scrum theory. You will also learn why Agile is best suited to industries that are susceptible to change and how to differentiate and blend Agile approaches.
Learning Objectives
- Describe the history and motivation behind the emergence of Agile and Scrum.
- Explain the Agile project management approach and philosophy, including values and principles.
- Explain why Agile is best suited for industries or projects that are susceptible to or that encourage change and uncertainty.
- Discuss the origins of Scrum and the basics of Scrum theory.
- Differentiate Agile frameworks and explain when and why to blend approaches.
Agile History
Agile methodologies emerged organically during the 1990s as the software industry was booming. Software startups like Google were blazing a trail to get more software products built in less time. Meanwhile, the tech giants of the time were experimenting with faster ways to build better software and stay competitive.
Agile aims to solve that problem by getting customer feedback more quickly to make sure that the team is building what the customer really wants. Part of working with an Agile mindset is always seeking out ways to work more efficiently. We do this by finding ways to streamline processes without reducing product quality or value. The key to streamlining is to reduce waste.
For example, unnecessary documentation is a form of waste. Another form of waste is spending weeks or months working on a feature, only to find out that the customers, who could also be users or stakeholders, don’t like the feature after all.
Important aspects
Three important aspects of a project are
- documentation
- deliverables
- requirements Requirements are conditions that must be met or tasks that must be finished to ensure the successful completion of the project.