This POGIL activity will help you learn about project scheduling, including challenges & useful techniques. To do this, you will explore ways to estimate how long it will take to make a batch of cookies.
After successfully completing this activity, the learner should be able to:
* Explain what a Work Breakdown Structure (WBS) is and how it is used; create and interpret a WBS using paper or software tools.
* Explain what a Gantt Chart is and how it is used; create and interpret a Gantt Chart using paper or software tools.
* Explain Critical Path Analysis (CPA) is and how it is used;(aka Program Evaluation and Review Technique) perform and interpret a CPA using paper or software tools.

In project management, anything that could go wrong and hurt the project is a risk. Any work to identify, prevent, or handle risks is risk management. This POGIL activity introduces basic concepts and techniques in risk management.
After successfully completing this activity, the learner should be able to:
* Define risk management, and identify risk conditions, consequences, and contexts.
* Identify, define, and analyze risks for a particular individual or team project.
* Describe and develop a risk management plan for a particular project.

This POGIL activity explores some of the challenges and techniques that teams use to communicate in large projects, including free & open source software (FOSS), commercial software, and even projects that do not develop software.
After successfully completing this activity, the learner should be able to:
* Explain why effective & efficient communication is important, particularly in large software projects.
* Describe communication methods often used in FOSS communities and by software developers.
* Describe the pros & cons of different communication methods, and identify appropriate methods for various scenarios.

We refer to FOSS culture or community (singular), but every project is its own community, and has its own rules, processes, and norms. This POGIL activity explores some elements, structures, and principles that are common across many (not all) FOSS and HFOSS communities.
After successfully completing this activity, the learner should be able to:
* Describe and give multiple examples of organizations with a pyramidal structure.
* Describe roles in a typical FOSS project, and how people transition between roles.
* Describe the common motivations for FOSS participants.

Slides that accompany Marko Schütz’s book Intro to FOSS (http://teachingopensource.org/learning-material/book-intro-foss./) Text is a comprehensive overview of the business of FOSS. Chapters include FOSS application areas, Philosophy and History of FOSS, FOSS Development and Community, FOSS Business, Case Studies, FOSS Government and more.

Comprehensive overview of the business of FOSS. Chapters include FOSS application areas, Philosophy and History of FOSS, FOSS Development and Community, FOSS Business, Case Studies, FOSS Government and more. Slides for the text: http://teachingopensource.org/learning-material/slides-intro-foss/

The Open Source Way is a book shows how to (and how not to) engage with the community members on projects of any type by practicing the open source way. This handbook distills years of knowledge our community members have gained while running open source projects.

11 ways to get involved in HFOSS

Introduction to the OpenMRS project.

Students are offered some key and optional readings, whereupon they will be asked questions to answer. This can be given as homework, or as an in-class quiz. The questions are a mix of definitive and open-ended questions. Answers and grading-suggestions are given.