This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: 4113 Review for Final AGILE PROJECT MANAGEMENT VS SDLC • Agile- an approach developed for projects in which the end project is not well defined and evolves over time. o Require flexibility and the ability to manage changes as more is learned. o Based on incremental, iterative development cycles. o Project manager is just a facilitator; Doesn’t have authority of team members. o Better for smaller projects (5-9) o Continuous design, Freeze design as late as possible o High uncertainty, Embrace change, High customer interaction, Self-organized project teams o Uses iterations (“time boxes”) to develop a workable product that satisfies the customer and other key stakeholders. o Limitations and Concerns of Agile OM It doesn’t satisfy top management’s need for budget, scope, and schedule control. Its principles of self-organization and close collaboration can be incompatible with corporate cultures. It requires active customer involvement and cooperation o Example of Popular Agile PM- Scrum Originally developed for new product development, but also used on high-tech and software development projects. Begins with a high level scope definition and ballpark cost and time estimates. Uses product features as deliverables • Feature= a piece of a product that delivers some useful functionality to a customer (e.g., a customer being able to change their PIN in a bank system) • Features are prioritized by their perceived highest value. • Project team tackles the highest, feasible priority features first; then they are re-evaluated after each iteration. • Features are created according to 4 distinct phases: o Analysis, Design, Build, Test Scrum relies on specific roles, meetings and documents/logs to manage the project within this framework. o 4 core principles underlying all Agile Methods Individuals and interactions over processes and tools Working results over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan • SDLC/Traditional approach o Firmly establish the project scope o Defines every detail of the project through the WBS o Potential problems and risks defined before the project begins o Estimates made and resources assigned to create the baseline schedule and budget o Project control—compare plan vs actual o Design up front, Fixed scope, Deliverables o Freeze design as early as possible, Low uncertainty, Avoid change o Low customer interaction, Conventional project teams Which approach is likely to be most suitable in these system development project situations? 1. When system requirements are emergent and changing rapidly? Agile 2. When the system to be built has high criticality, reliability and safety requirements? SDLC 3. Team size—will Agile work?...
View Full Document
This note was uploaded on 02/15/2012 for the course ISDS 4113 taught by Professor Staff during the Spring '08 term at LSU.
- Spring '08