Active Outline

General Information

Course ID (CB01A and CB01B)
CISD095G
Course Title (CB02)
Agile Project Management - A Practicum
Course Credit Status
Credit - Degree Applicable
Effective Term
Fall 2023
Course Description
This course teaches students how to apply Agile principles and the Scrum framework to create software-intensive products and acquire the practical knowledge and skills to initiate, plan, manage and execute Agile software development projects.
Faculty Requirements
Course Family
Not Applicable

Course Justification

This course is required for earning a Project Management Practitioner Certificate of Achievement and is in a CTE program that was developed based on labor market data. This course provides guidance to apply Agile principles and Scrum framework for effective team collaboration on complex products. This course is CSU transferable.

Foothill Equivalency

Does the course have a Foothill equivalent?
No
Foothill Course ID

Course Philosophy

Formerly Statement

Course Development Options

Basic Skill Status (CB08)
Course is not a basic skills course.
Grade Options
  • Letter Grade
  • Pass/No Pass
Repeat Limit
0

Transferability & Gen. Ed. Options

Transferability
Transferable to CSU only

Units and Hours

Summary

Minimum Credit Units
4.0
Maximum Credit Units
4.0

Weekly Student Hours

TypeIn ClassOut of Class
Lecture Hours4.08.0
Laboratory Hours0.00.0

Course Student Hours

Course Duration (Weeks)
12.0
Hours per unit divisor
36.0
Course In-Class (Contact) Hours
Lecture
48.0
Laboratory
0.0
Total
48.0
Course Out-of-Class Hours
Lecture
96.0
Laboratory
0.0
NA
0.0
Total
96.0

Prerequisite(s)

Corequisite(s)

Advisory(ies)

ESL D272. and ESL D273., or ESL D472. and ESL D473., or eligibility for EWRT D001A or EWRT D01AH or ESL D005.

Limitation(s) on Enrollment

Entrance Skill(s)

General Course Statement(s)

Methods of Instruction

Lecture and visual aids

Discussion of assigned reading

Discussion and problem solving performed in class

Collaborative learning and small group exercises

Collaborative projects

Guest speakers

Assignments

  1. Practice exam covering the topics covered in class.
  2. Readings from text.
  3. Participation in exercises that demonstrate ability to critically evaluate the proper use of appropriate agile software to complete a given set of project related tasks.

Methods of Evaluation

  1. One or two midterm examinations requiring students to write code applying topics covered in the lectures and reading. To be evaluated on correctness.
  2. Final examination requiring students to applying topics covered in the lectures, reading, and assignments.
  3. In-class exercises, group exercises, and/or online exercises demonstrating ability to implement agile software to complete a given set of project related tasks.

Essential Student Materials/Essential College Facilities

Essential Student Materials: 
  • None.
Essential College Facilities:
  • None.

Examples of Primary Texts and References

AuthorTitlePublisherDate/EditionISBN
The Great ScrumMaster: #ScrumMasterWay, Cohn, 1st edition, (Addison-Wesley Signature Series (Cohn)) 2017

Examples of Supporting Texts and References

AuthorTitlePublisher
None.

Learning Outcomes and Objectives

Course Objectives

  • Apply the foundations of Agile Software Development in team to get work done.
  • Describe and apply fundamentals of the Scrum Framework including roles, product delivery, tracking and monitoring projects.
  • Identify Product Planning with Agile Development, develop business value and features to be added for iteration
  • Illustrate how to create a work environment that fosters self-management with development teams
  • Illustrate how change management can be done through rapid reviews and feedback of iterations
  • Demonstrate how to create Agile culture through your organization

CSLOs

  • Illustrate usage of Agile Software practices in product delivery, tracking and monitoring projects.

  • Demonstrate creation of project plans with Agile Development methodology while understanding business value and planning feature iterations.

Outline

  1. Apply the foundations of Agile Software Development in team to get work done.
    1. Articulating Agile values and principles
    2. Comparing Agile with traditional, master plan methods
    3. Appreciating Agile development as value-driven delivery
  2. Describe and apply fundamentals of the Scrum Framework including roles, product delivery, tracking and monitoring projects.
    1. Recognizing Scrum as a framework for self-managing teams
    2. Locating Scrum in empirical process control theory
    3. Revealing systematically the issues in product development
    4. Ordering requirements and insuring Return on Investment through the Product Owner
    5. Establishing the ScrumMaster as a fundamentally new management role
    6. Shaping the self-managed Development Team
    7. Creating a Product Backlog as a list of requirements and technical issues
    8. Iterating development through cycles of one month or less
    9. Time boxing to establish a regular rhythm of energized work
    10. Capturing user needs as stories
    11. Using capacity-based planning to plan progress
    12. Measuring estimated effort with story points
  3. Identify Product Planning with Agile Development, develop business value and features to be added for iteration
    1. Delivering business-valued functionality with Sprint Planning
    2. Collaborating with customers to manage risk and uncertainty
    3. Demonstrating implemented features as "potentially shippable increments"
    4. Envisioning value through Product Chartering
    5. Creating a Sprint Goal through feature selection
    6. Identifying development tasks in the Sprint Backlog
  4. Illustrate how to create a work environment that fosters self-management with development teams
    1. Staffing the Development Team
    2. Protecting the team from outside interference
    3. Making progress visible and open
    4. Facilitating cross-functionality and team learning
    5. Empowering the team to control their own development process
    6. Adapting management roles external to the development effort
    7. Inspecting and adapting through the Daily Scrum
    8. Producing a quality-assured, business-valued product
    9. Ensuring standards through an agreed Definition of Done
  5. Illustrate how change management can be done through rapid reviews and feedback of iterations
    1. Demonstrating completed functionality to the customer
    2. Fostering collaboration with stakeholders through discussion of "done" increments
    3. Recalibrating estimates based on experience
    4. Revising team behavior on the basis of lessons learned
    5. Continuously improving by embedding new knowledge
  6. Demonstrate how to create Agile culture through your organization
    1. Working with large Product Backlogs
    2. Scaling the Product Owner role
    3. Coordinating component teams with Scrum Development Teams
    4. Planning Releases and Sprints for distributed teams
    5. Planning Releases and Sprints for distributed teams
    6. Holding distributed Sprint Reviews
    7. Assessing the organization's readiness for Agile adoption
    8. Creating an Improvement Backlog for ongoing improvement
Back to Top