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 Contracting and Governance

    Understanding Agile Contract Models

    agreement having a lawful object entered into voluntarily by multiple parties (may be explicitly written or oral)

    Agreement having a lawful object entered into voluntarily by multiple parties (may be explicitly written or oral).

    Agile contract models are a crucial aspect of Agile project management. They provide a framework for defining the relationship between the client and the service provider, outlining the scope of work, payment terms, and other key aspects of the project. Unlike traditional contracts, Agile contracts are designed to accommodate changes and uncertainties that are inherent in Agile projects.

    The Need for Agile Contracts

    In traditional project management, contracts are often fixed and rigid, with a clearly defined scope of work and a set timeline for delivery. However, this approach doesn't work well in Agile projects, where the scope of work is often flexible and changes frequently based on customer feedback and changing business needs.

    Agile contracts are designed to accommodate these changes. They allow for flexibility in the scope of work, timeline, and other aspects of the project, making it easier for both parties to adapt to changes and uncertainties.

    Types of Agile Contracts

    There are several types of Agile contracts, each with its own benefits and risks. Here are a few common ones:

    • Fixed Price Agile Contracts: These contracts have a fixed price for the entire project, but the scope of work is flexible. The client pays a fixed price, and the service provider delivers the highest priority features within that budget.

    • Time and Materials Agile Contracts: In these contracts, the client pays for the time and materials used by the service provider. This type of contract provides a high level of flexibility, as the scope of work can be adjusted based on the client's needs and budget.

    • Money for Nothing Change for Free Contracts: This type of contract allows the client to change the scope of work without additional charges, as long as the total cost of the project doesn't exceed the agreed-upon price. The client can also choose to end the project early and pay only a fraction of the total price, hence the term "money for nothing."

    Negotiating Agile Contracts

    Negotiating Agile contracts requires a good understanding of Agile principles and practices, as well as strong negotiation skills. Here are a few tips:

    • Understand the Client's Needs: Before negotiating a contract, it's important to understand the client's needs, priorities, and budget. This will help you propose a contract that meets their needs and provides value for their money.

    • Be Flexible: Agile contracts should be flexible and adaptable. Be open to changes and adjustments in the scope of work, timeline, and other aspects of the project.

    • Communicate Clearly: Clear communication is crucial in contract negotiation. Make sure all terms and conditions are clearly defined and understood by both parties.

    • Manage Risks: Every contract comes with risks. It's important to identify these risks and manage them effectively. This could involve setting clear expectations, establishing contingency plans, and regularly reviewing and adjusting the contract as needed.

    In conclusion, Agile contracts are a key tool for managing Agile projects. They provide a flexible framework for defining the relationship between the client and the service provider, accommodating changes and uncertainties, and ensuring that the project delivers value for the client.

    Test me
    Practical exercise
    Further reading

    My dude, any questions for me?

    Sign in to chat
    Next up: Vendor Management in Agile