This document provides an introduction to Agile and why it is used. It discusses that Agile allows teams to (1) learn with each new iteration, (2) deliver prototypes and improve them in each cycle, and (3) manage shifting priorities more effectively. It also differentiates between industrial work, which uses defined processes, and knowledge work, which relies on empirical processes better suited to uncertain projects. Agile provides a flexible approach for managing knowledge work.
3. Why using Agile?
1. Gives the teams an opportunity to
learn with each new iteration.
2. Lets teams deliver a prototype and
improve it with every cycle.
3. Manage shifting priorities more
effectively.
4. Fast and flexible process increases
productivity.
5. Supports regular and collaborative
troubleshooting.
4. Why using Agile?
6. Anticipating incoming project
changes.
7. Make quick-course corrections
based on stakeholder feedback.
8. Stakeholders can provide feedback
as the project evolves.
9. Empowering project teams to work
creatively and effectively.
10.Higher Quality Product.
8. Industrial
Work
Work is visible.
Work is stable.
Emphasis is on running things.
More structure with fewer decisions.
Define the task.
Strict standards.
Focus on quantity.
Measure performance based on standards.
Minimize cost of workers for a task.
Knowledge
Work
Work is invisible.
Work is changing.
Emphasis is on changing things.
Less structure with more decisions.
Understand the task.
Continuous innovation.
Focus on quality.
Continuously learn and teach.
Treat workers as assets, not as costs.
13. Industrial Work
uses a defined process
• Define the steps in advance.
• A well-understood project in an
unchanging environment.
• Planned and managed by using a
defined approach.
14. Knowledge Work
relies on an empirical process
• Processes are not well-defined When
faced with a new process.
• An experiment is required to
determine what works.
• Required for uncertain and risky
projects.