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 Methodologies and Frameworks

    Introduction to Scrum

    Agile software development framework

    Agile software development framework.

    Scrum is one of the most popular Agile methodologies used in project management today. It is a framework that helps teams work together, encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved.

    Definition and Overview of Scrum

    Scrum is an iterative and incremental Agile software development framework for managing product development. It defines a flexible, holistic product development strategy where a development team works as a unit to reach a common goal. It challenges the traditional, sequential approach to project management and development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved.

    The Scrum Framework: Roles, Events, Artifacts, and Rules

    The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.

    • Roles: There are three roles in Scrum: The Product Owner, the Scrum Master, and the Development Team. The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Scrum Master ensures that everyone follows the Scrum theory, practices, and rules. The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

    • Events: Scrum defines four events (time-boxed events, meaning they have a maximum duration) to create regularity: The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

    • Artifacts: Scrum Artifacts represent work or value. They are designed to maximize transparency of key information. These include the Product Backlog, Sprint Backlog, and the Increment.

    • Rules: The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them.

    The Scrum Values: Commitment, Courage, Focus, Openness, and Respect

    When the values of commitment, courage, focus, openness, and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone. The Scrum Team members learn and explore those values as they work with the Scrum events, roles, and artifacts.

    Benefits and Challenges of Implementing Scrum

    Implementing Scrum can offer numerous benefits, including improved product quality, higher customer satisfaction, increased team morale, and reduced time to market. However, it also presents challenges, such as resistance to change, maintaining stakeholder engagement, and managing evolving requirements.

    In conclusion, Scrum is a powerful Agile framework that, when implemented correctly, can drive significant improvements in productivity and product quality. It requires a shift in mindset from traditional project management methodologies and a commitment to its principles and values to be truly effective.

    Test me
    Practical exercise
    Further reading

    My dude, any questions for me?

    Sign in to chat
    Next up: Introduction to Kanban