{"id":4883,"date":"2026-01-30T21:36:55","date_gmt":"2026-01-31T03:36:55","guid":{"rendered":"https:\/\/ykim.synology.me\/wordpress\/?p=4883"},"modified":"2026-01-31T10:46:46","modified_gmt":"2026-01-31T16:46:46","slug":"agile-manifesto","status":"publish","type":"post","link":"https:\/\/ykim.synology.me\/wordpress\/agile-manifesto-4883\/","title":{"rendered":"Agile Manifesto"},"content":{"rendered":"\n

The Agile Manifesto<\/strong> (officially the Manifesto for Agile Software Development<\/em>) is a brief, foundational document created in 2001 that changed how software is built.<\/sup> It was written by 17 software developers who met at a ski resort in Snowbird, Utah, to find an alternative to the “heavyweight,” documentation-heavy processes that were then standard.<\/sup><\/p>\n\n\n\n

The manifesto is built on 4 Core Values<\/strong> and 12 Guiding Principles<\/strong>.<\/sup><\/p>\n\n\n\n

1. The 4 Core Values<\/h3>\n\n\n\n

The manifesto famously uses the phrase “over”<\/em> to show where the focus should shift.<\/sup> It does not say the items on the right are useless; it simply states that the items on the left are more valuable.<\/p>\n\n\n\n

    \n
  • Individuals and interactions<\/strong> over<\/em> processes and tools.<\/li>\n\n\n\n
  • Working software<\/strong> over<\/em> comprehensive documentation.<\/li>\n\n\n\n
  • Customer collaboration<\/strong> over<\/em> contract negotiation.<\/li>\n\n\n\n
  • Responding to change<\/strong> over<\/em> following a plan.<\/li>\n<\/ul>\n\n\n\n

    2. The 12 Guiding Principles<\/h3>\n\n\n\n

    These principles provide the practical framework for the Agile mindset:<\/p>\n\n\n\n

      \n
    1. Customer Satisfaction:<\/strong> Priority #1 is satisfying the customer through early and continuous delivery.<\/li>\n\n\n\n
    2. Welcome Change:<\/strong> Changing requirements are viewed as a competitive advantage, even late in development.<\/li>\n\n\n\n
    3. Frequent Delivery:<\/strong> Deliver working software often (weeks rather than months).<\/li>\n\n\n\n
    4. Collaboration:<\/strong> Business people and developers must work together daily.<\/li>\n\n\n\n
    5. Support & Trust:<\/strong> Build projects around motivated people; give them the environment they need and trust them.<\/li>\n\n\n\n
    6. Face-to-Face Conversation:<\/strong> The most efficient way to convey information is through direct talk.<\/li>\n\n\n\n
    7. Working Software:<\/strong> This is the primary measure of progress.<\/li>\n\n\n\n
    8. Sustainable Development:<\/strong> Teams should be able to maintain a constant, steady pace indefinitely.<\/li>\n\n\n\n
    9. Technical Excellence:<\/strong> Continuous attention to good design and technical quality enhances agility.<\/li>\n\n\n\n
    10. Simplicity:<\/strong> Focus on the “art of maximizing the amount of work not done.”<\/li>\n\n\n\n
    11. Self-Organizing Teams:<\/strong> The best work comes from teams that manage themselves.<\/li>\n\n\n\n
    12. Regular Reflection:<\/strong> Teams should regularly pause to look at how to become more effective and adjust accordingly.<\/li>\n<\/ol>\n\n\n\n

      Why it matters<\/h3>\n\n\n\n

      Before Agile, many projects followed the Waterfall<\/strong> model, where every detail was planned years in advance. This often led to software being “outdated” by the time it was actually finished. The Agile Manifesto shifted the industry toward a “learn as you go” culture that prioritizes people and adaptability.<\/sup><\/p>\n\n\n\n

      In the video below, one of the original signatories explains the story and the thought process behind the creation of these values.<\/p>\n\n\n\n

      \n