ºÚÁÏÉçÇø

Agile was born out of disdain for prescriptive methods and approaches that do not put people first which often leads to issues such as high levels of risk, a lack of productive collaboration and/or producing outcomes not intended or foreseen initially.

The practices prescribed in Agile provide for shorter, more flexible and simpler workflows where those involved can regularly assess their progress, outcomes and work ethic. This leads to better work with more purpose and outcomes that are desired by all stakeholders.

Those who are moving towards and have already implemented practices of Agile see these advantages in comparison to the ways they currently operate and that working Agile can lead to increased satisfaction in work, increased productivity and provide for more positive outcomes and solutions.

As a disclaimer, it needs to be said that Agile is different. It is better, it is more effective, but it is different.

You have arrived at a collection of information on what Agile is, how to implement it, other professor’s experiences, ºÚÁÏÉçÇø experiences, definitions, advice, tips, and the science behind all of it. A good majority of what you encounter outside of this collection will apply mostly to business and software; it is a new concept and its full potential has not been explored in every environment.

This site is a compilation of everything relating to the foundation of Agile, geared towards education and created for professors by Agile ºÚÁÏÉçÇøs.

Start small, ask questions and reach out for support! When you open your mind and take the plunge of transitioning into an Agile classroom, the possibilities for ºÚÁÏÉçÇø outcomes and instruction become limitless.

Word cloud image courtesy of Lynne Cazaly, 2019.

"We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

• Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation.
• Responding to change over following a plan.

That is, while there is value in the items on the right, we value the items on the left more."

Agile Manifesto for Software Development. (2018, December 12). Retrieved March 29, 2019, from . 

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• ºÚÁÏÉçÇø changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Working software is the primary measure of progress.
• Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity--the art of maximizing the amount of work not done--is essential.
• The best architectures, requirements, and designs emerge from self-organizing teams.
• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

• 12 Principles Behind the Agile Manifesto. (2017, November 15). Retrieved March 29, 2019, from 
• Barroca, L. (n.d.). Approaches to software development. Retrieved from .