Agile (student)

The Agile Manifesto and Agile method originated in the 1990s and early 2000s, in response to limitations of traditional project management methods that were often too rigid and bureaucratic.

Origin of the Agile Manifesto

The Agile Manifesto was written in 2001 during a meeting in Snowbird, Utah (USA), where 17 software development experts gathered to discuss alternative approaches to traditional project management methods (like the waterfall model). Key figures included:

• Kent Beck

• Robert C. Martin

• Jeff Sutherland

• Martin Fowler

These experts, coming from different approaches (Scrum, Extreme Programming, DSDM, etc.), shared a common frustration: traditional methods were too heavy, too rigid, and didn't allow sufficient reactivity to changes. They therefore wrote the Agile Manifesto, which is based on 4 values and 12 principles.

Origin of the Agile Method

Even before the formalization of the Agile Manifesto, several methodologies had already emerged to promote more flexible and collaborative development:

1950s-1980s

• First iterative approaches with models like the Spiral Model (1986)

1990s

Pre-manifesto methodologies:

• Scrum (1993)

• Extreme Programming (XP) (1996)

• Lean Software Development (adapted from Toyota Production System)

• Dynamic Systems Development Method (DSDM) (1994)

These methods influenced the creation of the Agile Manifesto in 2001 and are today the foundations of Agile project management.

Why Did Agile Become Popular?

• Reduced timelines: Less bureaucracy, short cycles

• Flexibility: Adaptation to changing needs

• Increased collaboration: Continuous client involvement

• Better software quality: Frequent testing and continuous improvements

Today, Agile is no longer limited to software development: it is applied to project management, marketing, design, and even business organization!

The Agile Manifesto is based on four fundamental values that guide software development and project management by promoting adaptability and collaboration:

1. Individuals and interactions over processes and tools
   • Emphasizes communication and collaboration within teams rather than rigid processes
   • Focuses on human relationships and team dynamics

2. Working software over comprehensive documentation
   • The main goal is to deliver a functional product
   • Avoids focusing on detailed documentation that could slow down development
   • Documentation should support development, not hinder it

3. Customer collaboration over contract negotiation
   • Prioritizes close working relationships with clients
   • Actively involves customers throughout the project
   • Allows adaptation to changing needs
   • Builds trust and transparency

4. Responding to change over following a plan
   • Encourages a flexible approach
   • Enables adjustment to new requirements
   • Avoids rigid plan adherence
   • Embraces evolution and adaptation

These values are complemented by 12 principles that detail how to apply Agility in project management and software development.

The Agile Manifesto is built on 12 principles that enable the application of its values in project management and software development:

1. Customer Satisfaction is the Priority
   • Deliver high-value software quickly and regularly
   • Focus on providing tangible business value

2. Welcome Change
   • Adapt to evolving needs, even late in the project
   • Use change as a competitive advantage

3. Frequent Delivery of Working Product
   • Prefer short cycles (weeks to months)
   • Ensure regular updates and continuous delivery

4. Continuous Stakeholder Collaboration
   • Work hand in hand with clients and users
   • Maintain ongoing dialogue throughout the project

5. Support, Motivate, and Trust Teams
   • Provide necessary environment and resources
   • Foster engagement and autonomy

6. Face-to-Face Communication
   • Direct exchange is more effective
   • Prefer direct communication over lengthy email chains or documentation

7. Working Software as Progress Indicator
   • Focus on delivering usable product
   • Prioritize functional software over secondary metrics

8. Sustainable Work Pace
   • Avoid team burnout
   • Maintain stable and sustainable tempo

9. Technical Excellence and Quality
   • Encourage development best practices
   • Ensure robust and evolving product

10. Simplicity is Essential
    • Minimize unnecessary work
    • Focus on what's essential

11. Self-Organizing Teams
    • Promote collective responsibility and decision-making
    • Enhance creativity and productivity

12. Continuous Reflection and Adjustment
    • Continuously improve
    • Analyze successes and areas for improvement after each iteration

Each principle supports the core values and provides practical guidance for implementing Agile methodologies.

1. Productivity Indicators

• Velocity
  • Story points completed per sprint

• Cycle time
  • Time from "in progress" to "done"

• Lead time
  • Total time from initial request to delivery

2. Quality Indicators

• Defect rate
  • Number of bugs per sprint

• Automated test success rate
  • Percentage of passed tests

• Throughput
  • Total completed items in a sprint

3. Team Engagement Indicators

• Team satisfaction
  • Measured through retrospectives or surveys

• Team turnover rate
  • Frequency of team member changes

• Workload
  • Hours worked per team member

4. Customer Satisfaction Indicators

• NPS (Net Promoter Score)
  • End-user satisfaction measurement

• CSAT (Customer Satisfaction Score)
  • Immediate user satisfaction score

• Stakeholder feedback
  • Qualitative assessment of product utility

5. Timeline and Budget Indicators

• Predictability
  • Ability to deliver on sprint commitments

• Burndown Chart
  • Backlog consumption tracking

• Budget Burn Rate
  • Budget consumption vs. planning

These indicators provide a comprehensive view of Agile performance across multiple dimensions, helping teams continuously improve and deliver value.

collaboration; Individuals; plan; working

1. …………… and interactions over processes and tools

2. …………… software over comprehensive documentation

3. Customer …………… over contract negotiation

4. Responding to change over following a ……………

become, welcome, done, customer, face, measure, daily, deliver, trust, pace, excellence, self

1. Our highest priority is to satisfy the …………… through early and continuous delivery of valuable software.

2. …………… changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3. …………… working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4. Business people and developers must work together …………… throughout the project.

5. Build projects around motivated individuals. Give them the environment and support they need, and …………… them to get the job done.

6. The most efficient and effective method of conveying information to and within a development team is face-to-…………… conversation.

7. Working software is the primary …………… of progress.

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant …………… indefinitely.

9. Continuous attention to technical …………… and good design enhances agility.

10. Simplicity--the art of maximizing the amount of work not ……………--is essential.

11. The best architectures, requirements, and designs emerge from ……………-organizing teams.

12. At regular intervals, the team reflects on how to …………… more effective, then tunes and adjusts its behavior accordingly.