605.608.81 - Software Project Management

Course Structure

The course materials are divided into modules. The Modules can be accessed by clicking Modules on the menu. A module will have several sections including the overview, content, readings, discussions, Wikis, and activities. Students are encouraged to preview all sections of the module before starting. Modules officially run for a period of seven (7) days, Tuesday - Monday (although after Module 1, each module will be release four days early to allow you two weekends with the material.)

Students should regularly check the Calendar and Announcements for activity due dates.

Course Topics

Module 1: Overview of Software Project Management
Module 2: Development Life Cycle Approaches
Module 3: Planning
Module 4: Schedule and Cost Estimation
Module 5: Schedule and Cost Management
Module 6: Hiring and Retaining Staff
Module 7: Risk
Module 8: Metrics Collection
Module 9: Process Improvement
Module 10: Performance Reviews
Module 11: Merit Planning
Module 12: Skills Building
Module 13: Team Building
Module 14: Operations and Maintenance

Course Goals

To master strategies to become a valued technical leader and critical thinker, and apply this knowledge to managing software programs/projects, communicating effectively with internal and external teams, and impacting the program/project by making a difference.

Course Learning Outcomes (CLOs)

• Differentiate between the skills and roles of functional and technical managers for software efforts and their relationship with other organizations.
• Produce specific sections of the plan used to manage the software development and maintenance efforts.
• Evaluate software project management practices within an organization and recommend practical improvements based upon your evaluation.
• Apply schedule and cost techniques to determine a Basis of Estimate.

Textbooks

None Required.

Required Software

You will need access to scheduling software such as Microsoft Project, Artemis, MPM, Primavera, or even Excel (which is not ideal) for a team project in the course. If you do not have access, generally you can download a copy of Microsoft Project and get a free 30-day trial. DO NOT download it until later in the semester when it is needed, as your trial period will run out too early. You will work in teams so everyone does not need this software. If you will not have access to scheduling software, please let me know by the end of Module 1. If you plan to download a trial copy of MS Project; you do not need to contact me.

Student Coursework Requirements

It is anticipated that this course will take approximately 5–8 hours per week to complete. Here is an approximate breakdown: reading the course material, listening to the audio annotated slide presentations and responding to learning activities (approximately 1–2 hours per week); posting to discussions (three parts) and  Wikis (1–2 hours), completing assessments and role playing activities, and working on project milestones and team activities (approximately 3–4 hours per week.) These times may vary from week to week.

Please do not provide company proprietary or classified information. If you have concerns on this matter, please contact the instructor.

 This course will consist of four basic student requirements:

Preparation and Participation (Class Discussions, Wikis, and Role Playing) (20% of Final Grade Calculation)

Each student is responsible for carefully reading all assigned material and being prepared for discussion. The readings are from the course materials. Some discussions require students to volunteer for role-playing exercises. If an insufficient number of students volunteer, the instructor will assign the roles. Those students who are not actors in the role-playing exercise will be required to comment on the scenarios viewed. More details will be given as the activity approaches; however, volunteering to role-play is on a first come basis.

Class Discussion

Each week will include a three part discussion forum. Post your initial response (Part 1) to discussion questions by 11:59 PM on Day 4 (Friday) for that module week, unless otherwise noted in the discussion board assignment. Start your initial discussion thread with Initial Post your first name your last name or for group discussions start with Initial Post Scenario X first name last name. first name last name, etc where X is the number of the Scenario and first name last name is the name of each team member who participated. You will receive a grade from 0 – 3 points for Part 1 of the class discussion. Your grade is based on both Timeliness and Critical Thinking. Late postings result in 0 points (unless the instructor decides otherwise) as it is not fair to your classmates who are depending on you. The late penalty is intentionally severe.

Part 2 of your discussion grade is your interaction with other classmates, responding with thoughtful responses to at least one and often two other students’ posting. You should begin each response with a single line that says either: Response to first name last name where first name last name is the person you are responding to or when we have group discussions Response to Scenario X first name last name. first name last name, etc where X is the number of the Scenario and first name last name is the name of each person on the team who participated. Part 2 is also awarded 0 – 3 points based on Critical Thinking and Timeliness and is due by 11:59 PM Sunday or Day 6. Late postings result in 0 points (unless the instructor decides otherwise.)  

Part 3 of the discussion is where you will respond to other students’ questions or comments on your post. You should begin each response with a single line that says: Response my initial Post or Response to our Scenario X. For scenario (team) discussions, at least one person on the team should respond to each question or comment; I suggest assigning team members to respond. You do not need to respond is there are no questions or comments to your original post. Part 3 postings which are late or insufficient will result in a deduction up to 0.6 points off based on Critical Thinking and Timeliness and are due by 11:59 PM Monday or Day 7 (unless the instructor decides otherwise.)

I welcome further discussions by posting questions or responses after the end date although no additional credit is rewarded.

Posting only your initial response to a discussion question is not sufficient; you should interact with your classmates. Be detailed in your postings and in your responses to your classmates' postings. You should feel free to agree or disagree with your classmates but please ensure that your postings are constructive and civil. The instructor will monitor class discussions and may respond to some postings.

Wikis

Each week one or more students will be assigned to post the module’s summary to the Wiki. This task should be completed by 11:59 PM on Day 7 (Monday.) Students assigned to write the Wiki will be awarded 0-4 points. Late postings result in 0 points (unless the instructor decides otherwise).

When there are multiple students summarizing a single module, please coordinate with teammate(s) to ensure that your week's Wiki is complete, the material complements one another, and each students’ contributions are roughly the same length. When two or more students are assigned to the week’s Wiki, you may work as a team to determine what the post should include; however each assigned student should post to the thread, or label who contributed what sections, or email me with whom contributed to each section so I am aware of the group effort, thus avoiding a teammate getting no credit.

It is recommended that other students (not assigned to that week’s Wiki) add to the Wiki after the initial posting is submitted; they will not receive a grade, but class participation may be used in the event of a borderline grade.

Role Playing

Module 6 requires students to volunteer to role-play; the first to volunteer will be chosen. All students will comment on the role-play in the discussion forum.

Module 10 requires different students (if possible) to volunteer; the first to volunteer will be chosen. All will comment on the role-play in the discussion forum.

Student can receive 0-6 points either as a volunteer or as a reviewer. Late postings result in 0 points (unless the instructor decides otherwise). Actors/actresses may receive an extra point (if the instructor decides) if they are one of the first four to volunteer.

Discussions (parts 1, 2, and 3), Wikis, and role-playing (both the actors and reviewers) are assessed as following:

Assessments (50% of Final Grade Calculation)

Reading class materials are important sources for your written assessments. Unless otherwise noted, assessments are due by 11:59 PM, Eastern Time on Day 7 or Monday. Students may use the course notes to complete the assessments. Point values for these assessments vary and are noted in the instructions. Late postings result in 10% off for each day the assessment is late.

Assessments will include a mix of qualitative activities (e.g. written questions), quantitative problem sets, and case study evaluations. Each assessment should include a cover sheet with your name and assessment identifier. Also, include your name and a page number indicator (i.e., page x of y) on each page of your submissions. Each problem should have the problem statement, assumptions, computations, and conclusions / discussion delineated. All Figures and Tables should be captioned and labeled as appropriate.

Team Project (30% of Final Grade Calculation)

The team project has several milestones and with three or four students assigned to the team. The team members will not change during the semester unless it is deemed necessary.

The Team Project will include a Software Development Plan (SDP), Basis of Estimate (BOE), re-assessing the BOE, risk and metric assignments, and schedule. It will also require you to comment on your team's cohesiveness. This project will ensure you and your team understand the course material and how it can be used. Each milestone should include a cover sheet with your name(s) and milestone identifier. Also, include your name(s) and a page number indicator (i.e., page x of y) on each page of your team project submissions. Each problem should have the problem statement, assumptions, computations, and conclusions / discussion delineated. All Figures and Tables should be captioned and labeled as appropriate. Team project milestones are due by 11:59 PM, Eastern Time (Monday) as noted in the instructions and point values vary from 5 – 40 points as noted in the instructions. Late postings result in 10% off for each day the team project is late.

It is expected that each team member participate equally for each milestone and I encourage teams to let me know if a team member is not performing his/her fair share.

Grading Policy

Student activities are due according to the dates in the Calendar and Activity item in corresponding module. The instructor will post grades generally within two weeks after activity due dates.

A grade of A indicates achievement of consistent excellence and distinction throughout the course—that is, excellence in all aspects of activities and discussion every week.

A grade of B indicates work that meets all course requirements on a level appropriate for graduate academic work.

EP uses a +/- grading system (see “Grading System”, Graduate Programs catalog, p. 10).

Final grades will be determined by the following weighting:

Course Evaluation

There will be a mid term and end of course evaluations for students to complete.

Academic Policies

Deadlines for Adding, Dropping and Withdrawing from Courses

Students may add a course up to one week after the start of the term for that particular course. Students may drop courses according to the drop deadlines outlined in the EP academic calendar (https://ep.jhu.edu/student-services/academic-calendar/). Between the 6th week of the class and prior to the final withdrawal deadline, a student may withdraw from a course with a W on their academic record. A record of the course will remain on the academic record with a W appearing in the grade column to indicate that the student registered and withdrew from the course.

Academic Misconduct Policy

All students are required to read, know, and comply with the Johns Hopkins University Krieger School of Arts and Sciences (KSAS) / Whiting School of Engineering (WSE) Procedures for Handling Allegations of Misconduct by Full-Time and Part-Time Graduate Students.

This policy prohibits academic misconduct, including but not limited to the following: cheating or facilitating cheating; plagiarism; reuse of assignments; unauthorized collaboration; alteration of graded assignments; and unfair competition. Course materials (old assignments, texts, or examinations, etc.) should not be shared unless authorized by the course instructor. Any questions related to this policy should be directed to EP’s academic integrity officer at ep-academic-integrity@jhu.edu.

Students with Disabilities - Accommodations and Accessibility

Johns Hopkins University values diversity and inclusion. We are committed to providing welcoming, equitable, and accessible educational experiences for all students. Students with disabilities (including those with psychological conditions, medical conditions and temporary disabilities) can request accommodations for this course by providing an Accommodation Letter issued by Student Disability Services (SDS). Please request accommodations for this course as early as possible to provide time for effective communication and arrangements.

For further information or to start the process of requesting accommodations, please contact Student Disability Services at Engineering for Professionals, ep-disability-svcs@jhu.edu.

Student Conduct Code

The fundamental purpose of the JHU regulation of student conduct is to promote and to protect the health, safety, welfare, property, and rights of all members of the University community as well as to promote the orderly operation of the University and to safeguard its property and facilities. As members of the University community, students accept certain responsibilities which support the educational mission and create an environment in which all students are afforded the same opportunity to succeed academically. 

For a full description of the code please visit the following website: https://studentaffairs.jhu.edu/policies-guidelines/student-code/

Classroom Climate

JHU is committed to creating a classroom environment that values the diversity of experiences and perspectives that all students bring. Everyone has the right to be treated with dignity and respect. Fostering an inclusive climate is important. Research and experience show that students who interact with peers who are different from themselves learn new things and experience tangible educational outcomes. At no time in this learning process should someone be singled out or treated unequally on the basis of any seen or unseen part of their identity. 
 
If you have concerns in this course about harassment, discrimination, or any unequal treatment, or if you seek accommodations or resources, please reach out to the course instructor directly. Reporting will never impact your course grade. You may also share concerns with your program chair, the Assistant Dean for Diversity and Inclusion, or the Office of Institutional Equity. In handling reports, people will protect your privacy as much as possible, but faculty and staff are required to officially report information for some cases (e.g. sexual harassment).

Course Auditing

When a student enrolls in an EP course with “audit” status, the student must reach an understanding with the instructor as to what is required to earn the “audit.” If the student does not meet those expectations, the instructor must notify the EP Registration Team [EP-Registration@exchange.johnshopkins.edu] in order for the student to be retroactively dropped or withdrawn from the course (depending on when the "audit" was requested and in accordance with EP registration deadlines). All lecture content will remain accessible to auditing students, but access to all other course material is left to the discretion of the instructor.