Managing Software Development (COMP3120)
Tutorials & Workshops
Students will work in small teams of 3 or 4 students during each workshop. Group membership will be constant for the first four workshops, after which the course academics will re-arrange students into new groups for the final four workshops.
Students will choose their own groups for the first four workshops. Students will complete their assignments in these groups.
One reading will be assigned to each group of students for each workshop.
This page will be updated as the course progresses
Workshop Times & Locations
Monday
- 11:00 - 13:00 -- CS&IT N101
- 13:00 - 15:00 -- CS&IT N101
Wednesday
- 11:00 - 13:00 -- CS&IT N101
Thursday
- 13:00 - 15:00 -- CS&IT N109
- 15:00 - 17:00 -- CS&IT N109
Workshop Topics & Timing
| Week |
Topic |
Materials |
|
3
|
Workshop #1 Project Management: An Accidental Profession?
|
READINGS
-
Pinto, J. and
Kharbanda, O. (1995). Lessons for an accidental profession. Business Horizons.
pp.41-50
-
Giammalvo, P. &
Suermondt, J. (2010). Behavioral Profiles of Successful Project Managers. Is Project Management a Profession? Retrieved
from www.build-project-management-competency.com. Can also be found in two parts at http://pmstudent.com/project-management-careers-behaviors-1/
Larson, E.W. & Gray, C.F. (2011). Leadership: Being an Effective Project Manager. Project Management: The Managerial Process, Chapter 10. 5th edition, McGraw Hill.
Schweriner, J.
(2007). Ethics Considerations for the Project Manager in Professional Services. PMI Global Congress Proceedings.
Retrieved from
http://www.schweriner.com/writing/EthicsConsiderationsfortheProjectManagerinProfessionalServices.pdf
INSTRUCTIONS
|
|
5
|
Workshop #2 Why Projects Fail
|
READINGS
Charette, R.
(2005), Why
software fails. IEEE Spectrum. Retrieved from
http://spectrum.ieee.org/computing/software/why-software-fails
Nix, L. and
Highsmith, J. (1996), To
Be, or Not to Be. Software Development Magazine.
Retrieved from http://www.ksinc.com/articles.html
Stepanek, G.
(2005).Chapter 2 – Why Software is Different.. Software Project Secrets: Why Software Projects Fail.
Springer-Verlag,
New York
Stepanek, G.
(2005).Chapter 3 – Project Management Assumptions.. Software Project Secrets: Why Software Projects Fail.
Springer-Verlag,
New York
INSTRUCTIONS
|
|
6
|
Workshop #3 Agile Project Management
|
READINGS
Sliger, M. (2006) Relating PMBOK Practices to Agile Practices - Parts 1- 4
- Part 1
- Part 2
- Part 3
- Part 4
Haas, K. The
Blending of Traditional and Agile Project Management. Retrieved from
http://www.ProjectSmart.co.uk
Which Life Cycle is Best for Your Project?. Retrieved from
http://www.ProjectSmart.co.uk
Scott Ambler & Associates. Choose the Right Software Method for the Job. Retrieved from Agile Data
INSTRUCTIONS
|
|
7
|
Workshop #4
Scope Management
|
READINGS
Mathis, M. Work Breakdown Structure: Purpose, Process and Pitfalls.
How to Develop Work Breakdown Structures
Goal-Driven Backlog Development - User Story Mapping
Noah's Ark Project
INSTRUCTIONS
|
|
9
|
Workshop Assistance from ASLC for assignments
|
Academic Skills & Learning Centre assistance during workshops
|
|
10
|
Workshop #5
Project Scheduling & Progress Reporting
|
READINGS
How to deal with software development schedule pressure.
Weigh the work ahead
Coding Horror: How long would it take if everything went wrong?
Create Achievable Schedules
Prioritising using MoSCoW
Suggested User Story Map
Suggested Product Breakdown Structure
Noahs Ark Scenario
INSTRUCTIONS
|
|
11
|
Workshop Student Presentations
|
Student groups present their research reports
|