Let’s do a little Math.
Before agile existed, the widely used method in developing software was the Waterfall.
– relies on predictability and sequence
– need to spend a large amount of time and effort
– gather resources and plan with a lot of key decisions based purely on assumption
= constricting, regulated, and too slow moving X
This kind of method will have a hard time meeting and responding to sky-high user expectations.
Software developers need a more flexible project management method that made room for errors, bugs, setbacks, and feedback from real users.
Therefore, we need change.
In 2001, a group of 17 individuals came together to create an “alternative to documentation driven, heavyweight software development processes.”
A specific type of Rapid Application Development and newer than Waterfall. And that’s the birth of AGILE.
+ moving fast, releasing often, and reacting to the real needs of your users
+ prioritizes incremental and feedback-driven changes into software development
+ takes the emphasis off you and puts it on your customers
+ make a small change but can have huge results
= Faster development. More releases. More revenue √
The creators of Agile defined 4 key values that all Agile projects should adhere to:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
This doesn’t mean you should throw out your time-honed tools, documentation, and plans. But rather that while those things are valuable to any development effort, the items on the left should be your core focus: people, prototypes, collaboration, and iteration. To present their beliefs in a more actionable form.
How does Agile work?
Agile project methodology breaks down projects into small pieces that are completed in work sessions that run from the design phase to testing and quality assurance (QA). These sessions are often called sprints, the term for iteration used in one specific and popular Agile development method known as Scrum.
Sprints are generally short, running over days or weeks; they’re typically two to four weeks long.
The Agile methodology enables teams to release segments as they’re completed. This continuous release schedule allows for teams to demonstrate that these segments are successful and, if not, to fix flaws quickly. The belief is that this helps reduce the chance of large-scale failures because there is continuous improvement throughout the project lifecycle.
Many became a very needy consumer. They don’t care about your long-term plan, they want what they want now and Agile is a fantastic way to make sure the user’s needs are put front and center whenever you’re developing new software.
To learn more about a career in agile join our weekly seminars.