What is the Agile methodology?

• 2001: Publication of the “Agile Manifesto” by a group of 17 programmers
• Earlier methods, such as Scrum (1995) and Extreme Programming (1996), which contributed to the emergence of Agile
• Inspiration from Japanese management practices such as Lean and Kaizen

1. People and interactions over processes and tools
2. Working software over extensive documentation
3. Working with the customer beyond contract negotiation
4. Responding to change over following a plan

1. Iterative development: The product is developed in short cycles (iterations)
2. Incremental delivery: Frequent delivery of small, functional parts of a product
3. Adaptive planning: Flexibility to adapt plans to changing requirements
4. Continuous communication: regular team meetings and customer interactions
5. Self-organized teams: Teams have autonomy in decision-making
6. Quick response to changes: Readiness to modify the product during development

1. Planning the project and defining the product vision
2. Creating a product backlog (list of requirements)
3. Iteration (sprint) planning
4. Implementation of tasks within an iteration
5. Daily synchronization of the team (daily stand-up)
6. Iteration review and product demonstration
7. Retrospective and improvement planning
8. Repeat the cycle from point 3

1. Scrum: A sprint-based framework with Scrum Master and Product Owner roles
2. Kanban: A method to visualize work and optimize task flow
3. Extreme Programming (XP): Focuses on engineering practices such as pair programming and continuous integration

• It is self-organized and multidisciplinary
• Works closely with customers and stakeholders
• Takes responsibility for delivering the product
• Participates in task planning and estimation
• Regularly delivers working increments of product

1. Increased flexibility and adaptability
2. Deliver business value faster
3. Better product quality through continuous testing and improvement
4. Increased customer satisfaction
5. Better communication and cooperation in the team
6. Increased design transparency
7. Reducing project risks

1. Changing organizational culture
2. Difficulties in estimation and long-term planning
3. Need for ongoing customer engagement
4. Managing stakeholder expectations
5. Integration with existing processes and systems
6. Ensure proper documentation

• Flexibility vs rigid planning
• Iterative delivery vs. delivery at the end of the project
• Continuous customer interaction vs limited interaction
• Adaptation to change vs resistance to change
• Self-organized teams vs hierarchical structures

1. Project management systems: JIRA, Trello, Asana
2. Version control tools: Git, SVN
3. Continuous integration and delivery tools: Jenkins, GitLab CI
4. Test automation tools: Selenium, JUnit
5. Team communication tools: Slack, Microsoft Teams

• Marketing and advertising
• Education
• Production
• Financial services
• Health care
• Construction and architecture

1. Velocity – the amount of work done in a sprint
2. Burn-down and burn-up charts
3. Cumulative Flow Diagram
4. Lead Time and Cycle Time
5. Customer satisfaction index
6. Code quality and number of defects

In summary, the Agile methodology offers a flexible and effective approach to project management that can bring significant benefits to organizations ready to make changes to their culture and work processes. The key to success is understanding the basic principles of Agile and skillfully adapting them to the specifics of your organization and project.