Discuss an article from a trade journal or a professional publication (See below).
Discuss a software risk or "horror story". (Project failure, defect,
unreliability, or
security hole).
A short intro or demo of a software tool (Obtain permission in advance.)
Discuss how your team dealt with some management, coordination, or communication problem.
Introduce a current event or issue in the software industry and
discuss its significance or implications from a software engineering
perspective..
Give a "motivational" talk that explains the benefits of any software engineering method or technique, from "design by contract" to "risk management" to "regression testing" to "formal technical reviews."
Explain a method or technique that you think your team would benefit from adopting. Present a detailed "adoption plan" explaining how your team could incorporate and apply the technique.
Present an evaluation of some "adoption plan" that your team undertook. Describe what happened and what your team learned.
In addition, the instructor will on occassion ask for a volunteer to
lookup the answer to some short question for the class, such as "Which
language has the most programmers currently developing software
applications?"
You can report how you researched the answer and what you found.
Trade journals and professional publications