Advantage & Disadvantage + Continuous testing and communication can find issues rapidly - Might not find bugs until later stage Risk Management - Knowledge is stored mentally - Code is the documentation + Highly emphasize + Requires in every stage Documentation + Good internal communication + Higher quality - Lack of communication with the customer and team members Communication + Micro Planning + Avoid Requirement cramming - Might be headed toward wrong direction + Able to see the overall project Planning + No delays on important features + Less important features might scaled back or dropped + Support for long-term plans Prioritization Agile Method Traditional Management
Work Breakdown Schedule
Review Case Study (March)
Paper Analysis (March-April)
Writing the Paper
Pressman, Roger S. “Software Engineering.” Software Engineering Project Management. Pp. 30-47. IEEE. 2000.
Highsmith, Jim & Cockburn, Alistair. “Agile Software Development: The Business of Innovation.” IEEE Computer. September 2001.
"Agile software development." Wikipedia, The Free Encyclopedia . 19 Apr 2007, 10:26 UTC. Wikimedia Foundation, Inc. 19 Apr 2007 < http:// en.wikipedia.org/w/index.php?title = Agile_software_development&oldid =124050398 >.
Rising, Linda & Janoff, Norman. “The Scrum Software Development Process for Small Teams.” IEEE Software. July/August 2000.
Brooks, Frederick. The Mythical Man-Month: Essays on Software Engineering. MA: Addison-Wesley Professional 1975.
Sutherland, Jeff. “Agile Development: Lessons Learned From the First Scrum.” Cutter Agile Project Management Advisory Service. Executive Update, Vol. 5, No. 20. October 2004.
Anderson, David. Agile Management for Software Engineering . New Jersey: Prentice Hall, 2004.
KarlstrÖm, Daniel & Runeson, Per. “Combining Agile Methods with Stage-Gate Project Managment.” IEEE Software. May/June 2005.