101.school
CoursesAbout
Search...⌘K
Generate a course with AI...

    Agile project management

    Receive aemail containing the next unit.
    • Introduction to Agile Project Management
      • 1.1History and Evolution of Agile Methodologies
      • 1.2Key Concepts and Principles of Agile
      • 1.3Introduction to Agile Project Management
      • 1.4Roles and Responsibilities in Agile
    • Agile Mindset and Agile Manifesto
      • 2.1Understanding Agile Mindset
      • 2.2Agile Manifesto and its Principles
      • 2.3Building an Agile Culture
      • 2.4Agilism and the Role of a Leader
    • Agile Leadership
      • 3.1Agile Leadership Styles
      • 3.2Role and Responsibilities of Agile Leaders
      • 3.3Facilitating Team Performance
      • 3.4Managing Conflicts and Backlogs
    • Agile Methodologies and Frameworks
      • 4.1Introduction to Scrum
      • 4.2Introduction to Kanban
      • 4.3Lean and XP Explained
      • 4.4Choosing the Right Agile Framework or Methodology
    • Building an Agile Team
      • 5.1Organizing Agile Teams
      • 5.2Building Psychological Safety Within Teams
      • 5.3Distributed Agile Teams
      • 5.4Team Performance Metrics in Agile
    • Agile Planning and Estimation
      • 6.1Introduction to Agile Planning
      • 6.2Story Points and Velocity
      • 6.3Agile Estimation Techniques
      • 6.4Capacity Planning in Agile
    • Executing Agile Projects
      • 7.1Running Agile Meetings and Setting Sprint Goals
      • 7.2Managing and Prioritizing Backlogs
      • 7.3Tracking Project Progress: Burn-Down and Burn-Up Charts
      • 7.4Handling Blockers and Impediments
    • Agile Quality Assurance
      • 8.1Quality Metrics in Agile
      • 8.2Agile Testing Strategies
      • 8.3Test-Driven Development
      • 8.4Continuous Integration and Continuous Deployment
    • Value-Driven Development
      • 9.1Principles of Value Driven Development
      • 9.2Prioritizing Value in the Backlog
      • 9.3Minimum Viable Product and Incremental Delivery
      • 9.4Value Stream Mapping
    • Agile Contracting and Governance
      • 10.1Agile Contract Models
      • 10.2Vendor Management in Agile
      • 10.3Governance in Agile
      • 10.4Compliance and Documentation in Agile
    • Agile Transformation and Scaling
      • 11.1Agile Transformation Pathways
      • 11.2Implementing Agile at Scale
      • 11.3Challenges in Agile Scaling
      • 11.4Tools for Managing Agile at Scale
    • Case Studies and Best Practices
      • 12.1Agile in IT and Software Development
      • 12.2Agile in Non-IT Industries
      • 12.3Agile Project Pitfalls and Mitigation
      • 12.4Sharing Best Practices
    • Reflection and Synthesis
      • 13.1Agile Leadership Reflections
      • 13.2Applying Agile Methodologies in Real-life Scenarios
      • 13.3Adapting Agile Frameworks to Unique Situations
      • 13.4Continuing Education and Certification in Agile

    Agile Mindset and Agile Manifesto

    Understanding the Agile Manifesto and its Principles

    The Agile Manifesto is a foundational document for Agile project management and software development. It was created in 2001 by a group of seventeen software developers who were looking for a more flexible, efficient way to manage projects and develop software. The Agile Manifesto consists of four core values and twelve principles that guide the Agile approach.

    The Four Values of the Agile Manifesto

    1. Individuals and interactions over processes and tools: This value emphasizes the importance of people and the way they work together in Agile projects. While processes and tools are important, they should serve the team, not the other way around. Effective communication, collaboration, and a focus on individuals' skills and talents are key to Agile success.

    2. Working software over comprehensive documentation: In traditional project management, extensive documentation is often required before any actual work begins. In contrast, Agile values working software that delivers value to the customer over detailed documentation. This doesn't mean that documentation is not important, but Agile teams aim to produce minimal, necessary documentation that supports the development process without hindering progress.

    3. Customer collaboration over contract negotiation: Agile teams prioritize close collaboration with customers throughout the project. This ongoing interaction allows for regular feedback and adjustments, ensuring that the final product meets the customer's needs and expectations. This value emphasizes the importance of flexibility and adaptability over rigid contract terms.

    4. Responding to change over following a plan: Agile recognizes that change is inevitable in any project. Instead of resisting change, Agile teams embrace it, viewing it as an opportunity to improve the product and deliver greater value to the customer. While planning is important, the ability to respond to change is valued more in Agile.

    The Twelve Principles of the Agile Manifesto

    The twelve principles of the Agile Manifesto provide further guidance on how to implement the Agile approach. They are:

    1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
    2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
    3. Deliver 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 daily throughout the project.
    5. Build projects around motivated individuals. Give them the environment and support they need, and trust 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-face conversation.
    7. Working software is the primary measure of progress.
    8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
    9. Continuous attention to technical excellence and good design enhances agility.
    10. Simplicity--the art of maximizing the amount of work not done--is essential.
    11. The best architectures, requirements, and designs emerge from self-organizing teams.
    12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

    In conclusion, the Agile Manifesto and its principles provide a framework for Agile project management, emphasizing flexibility, collaboration, customer satisfaction, and responsiveness to change. By understanding and applying these values and principles, Agile teams can deliver high-quality products that meet customer needs and expectations.

    Test me
    Practical exercise
    Further reading

    Howdy, any questions I can help with?

    Sign in to chat
    Next up: Building an Agile Culture