Good software project leadership requires an understanding of three major areas: software technology, economic factors, and human relations. This course assumes that you have a good background in software technology, and concentrates on the economic and human factors and shows how they interplay with software factors.
The course will focus on a set of pervasive management and economic paradigms which are highly valuable software engineering tools: teambuilding, empowerment, continuous process improvement, win-win situations, production functions, economies of scale, present value, constrained optimization, risk and decision analysis, etc. It will do this in the context of new software challenges (rapid development, rapid change, COTS integration, talent shortages) and new approaches to the software process, including process maturity models, Theory W, the Spiral Model, Model-based (System) Architectecting and Software Engineering (MBASE), and software risk management. These will all be integrated into a framework of Value-Based Software Engineering.
MBASE integrates economics and human factors into software development through the fundamental concept of reconciling stakeholder value propositions into a win-win shared vision of the products to be developed and the process for developing them. A software project's success-critical stakeholders generally include users, acquirers, developers, and maintainers; and may also include marketers, venture capitalists, interpreters, and representatives of the general public.
Theory W project management is based on the fundamental principle that the project manager's principal objective is to Make Everyone a Winner (customers, subordinates, bosses, users, maintainers). The course will elaborate this principle into a 9-step approach which focuses on techniques for creating win-win conditions, negotiation, expectations management, and conflict resolution.
Software risk management is one of the nine Theory W steps: identifying and managing win-lose or lose-lose project risks. It is also the driver of the Spiral Model. The course will cover the discipline of software risk management under six primary sub-topics: risk identification, risk analysis, risk prioritization, risk management planning, risk resolution, and risk monitoring.
Basis of Grade
500 points: Homework exercises. Due dates are indicated in the Course Schedule. Assignments are due at 12 noon on the day indicated, in hardcopy in the box outside SAL330. Please do not submit softcopy.
200 points: Midterm Exams: 9/26(Friday) and 10/31(Friday). 100 points each; based on lecture, homework, and reading material covered through the previous class session. Open book; bring a hand calculator with an x^y key.
300 points: Final Exam: 12/15(Monday). Covering the full range of course material, but focused on topics covered in lectures and homeworks. Open book; bring at least textbooks and a hand calculator with an x^y key.