Agile XR
  • Welcome
  • Key Project Learnings and Reflections
  • Project Result 1
  • 1 - Guide: Agile Teamwork in Web-Based Learning
    • Chapter 1 - Agile in Software
      • 1.1 Values in Agile Software Development
      • 1.2 Principles in Agile Software Development
      • 1.3 Agile Project Management and practices
      • 1.4 Agile Mindset
    • Chapter 2 - Agile in Education
      • 2.1 Agile Compass for Education
      • 2.2 eduScrum
      • 2.3 Agora schools
      • 2.4 Agile Learning Centers
    • Chapter 3 - Agile practices for project-based learning
      • 3.1 Sprint Planning and Execution
      • 3.2 Daily Stand-Up Meetings
      • 3.3 Collaborative Learning and Projects
        • 3.3.1 Project initiation
        • 3.3.2 Project planning
        • 3.3.3 Project execution
        • 3.3.4 Project performance/monitoring
        • 3.3.5 Project closing
        • 3.3.6 Agile rituals using Mural
    • Conclusions
    • Bonus: Interviews with Agile Experts
      • Interview with Yeremi Marín, ALC Facilitator at EduCambiando, Mexico
      • Interview with Ryan Shollenberger, Co-director ALC NYC
      • Interview with Willy Wijnands, Cofounder eduScrum
  • 2 - Video Tutorials: Agile Teaching Techniques
  • Project Result 2
    • 3 - Guide: Implementing VR/XR in Team-Based Education
      • Our Approach: Design-Research
      • State of VR for Education
      • How To Choose VR Hardware and Software
      • Testing and Benchmarking VR Platforms
      • Designing Virtual Environments for VR Learning
    • 4 - Manual: Spatial.io for VR-Enhanced Teamwork
      • Terminology in XR
  • Project Result 3
    • 5 - Workshop: Designing Blended Learning Courses
      • Session 1 - Redesign Project Framing
      • Session 2 - Understanding the Student Experience
      • Session 3 - Understanding the Teacher Experience
      • Session 4 - Blended Course Plan
    • 6 - Workshop: Enhancing Existing Lessons for Blended Learning
      • Session 1 - Quick Scan
      • Session 2 - Deep Scan
    • 7 - Lesson Plan Templates for Online and Hybrid Learning
      • LP1 - Intro to AI - Elementary School
      • LP2 - Planning Skills - Lower Secondary Level
      • LP3 - Intro Radioactivity - Higher Secondary Level
      • LP4 - Berlin Wall - Upper Secondary Level
      • LP 5-10 - Lifelab Project - Upper Secondary Level
  • Project Result 4
    • 8 - Guide: Mastering Effective Distance Learning
      • Module 1: Introduction
        • What is distance learning and is it expanding so fast?
        • Online learning
      • Module 2: Methods of implementing distance learning
        • Synchronous online learning
        • Asynchronous online learning
        • Blended learning and flipped learning/classroom
      • Module 3: Classroom management in online learning
        • Class management in distance learning and how to engage students in distance learning
      • Module 4: Promoting collaborative learning in distance learning
        • Collaborative learning in distance learning
        • Problem-based learning and project-based learning in distance learning
        • Cooperative learning in distance learning
      • Module 5: How to promote social interactions in distance learning
      • Module 6: Educational technology tools for distance learning
      • References
    • 9 - Reference Guide: EdTech Tools for Interactive Teaching
      • Module 1: Introduction
        • How to get more student engagement?
        • How can we make it more collaborative?
        • What can be done with less or no teacher support? (e.g. for flipped classrooms)
      • Module 2: EdPuzzle
      • Module 3: Socrative
      • Module 4: Trello
      • Module 5: Nearpod
      • Module 6: Google Drive, Microsoft OneDrive, etc. (Shared document tools)
    • 10 - Digital Tool: EdTech Decision-Maker
    • 11 - Report: Evaluating Agile and VR/XR Teaching Pilots
      • Introduction
        • The project "Augmented Agile teamwork for hybrid learning at Schools” (AgileXR)
        • Project Result 4: Pilot and Impact Evaluation and Lessons Learned
        • Brief Theoretical Framework
        • Pilot Teaching Experiences in the AgileXR Project
      • Aim of the report
      • Method
        • Participants
        • Materials
        • Data Analysis
        • Procedure
      • Results and discussion
        • Students' perspectives
        • Teachers’ perspectives
      • Educational implications
      • Conclusions
      • Bibliographical references
      • Appendix
        • Appendix 1. Pilot evaluation student questionnaire
        • Appendix 2. Pilot evaluation teacher questionnaire
        • Appendix 3. GDPR - Family authorisation for secondary school students
  • Translations
    • 12 - Multilingual Publication Translations
Powered by GitBook
On this page
  1. 1 - Guide: Agile Teamwork in Web-Based Learning
  2. Chapter 1 - Agile in Software

1.3 Agile Project Management and practices

Previous1.2 Principles in Agile Software DevelopmentNext1.4 Agile Mindset

Last updated 1 year ago

In the 1990s, the software industry faced significant challenges. First, it was relatively young, and there weren't enough skilled software developers available. Second, the industry relied on a strict project management approach known as "waterfall." This method prioritized creating extensive lists of requirements, often more for legal agreements than collaborating with clients. This lack of cooperation led to widespread distrust.

Additionally, software development differed from the incremental approach used today. Instead of gradual improvements, software was created in large packages. Consider software like the old Office 95, with numerous features that most people didn't use. Developing such extensive packages took years and often resulted in bugs. The Pareto Law illustrated that only around 20% of the software was utilized, leaving 80% of resources wasted.

In the traditional "waterfall" approach, a software project might take a whole year to complete without any input from the client. However, in the Agile approach, that same software gets delivered to the client every month or during a "sprint," allowing for early feedback and gradual improvements. This way, by the end of the year, you have a successful final solution.

Various methods and approaches can be used to work in an Agile way. They all follow the principles and values we talked about earlier.

The involves several key practices. First, there's the "product backlog," which is a list of desired features and tasks for the entire year. Then, for each month, you have a "sprint backlog," which is a list of things to work on during that month. The Agile cycle happens regularly, usually every two weeks or a month, as decided by the team, and it involves steps like planning, designing, developing, testing, and releasing the software. This cycle keeps repeating, with each sprint drawing from the sprint backlog, and it leads to the delivery of the final product.

Some well-known t include Scrum, Kanban, Hybrid, Lean, Bimodal, XP, and Crystal. Among these, Scrum is the most widely used.

Agile development process
Agile frameworks in software developmen
Waterfall vs Agile
Agile Development Cycle
How Scrum framework works