Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 146 Next »

The OIT Systems Development Life Cycle (SDLC) is an important guideline to use when developing systems or implementing third-party solutions. In addition to helping implement more robust and secure systems for UCI, it also helps address future audits of IT systems by providing the procedures and documentation required to meet the expectations of the auditors.

The SDLC described here is meant to provide a flexible set of guidelines that can be adapted to any project by tailoring the steps, processes, and procedures to meet specific needs of a project. For more information, see Tailoring the SDLC. An overview diagram of the entire process can be downloaded in PDF or Microsoft Visio 2010 format.

Waterfall vs Scrum

Both Waterfall and Scrum are widely used models in SDLC with their respective pros and cons.  Although most projects adopt one methodology over the other, the non-traditional hybrid method of using parts of each methodology can also be effective in arrive at the desired project outcome.  Table below provides some characteristics of both Waterfall and Scrum.  Detailed information on each methodologies tailored for OIT can be found in the following links.

 WaterfallScrum
Fundamental AssumptionsSystems are fully specifiable, predictable, and can be build through meticulous and extensive planning.High-quality, adaptive software can be developed by small teams using principles of continuous design improvement and testing based on rapid feedback and change.
ControlProcess centricPeople centric
Management StyleCommand-and-controlLeadership-and-collaboration
Knowledge ManagementExplicitTacit
Role AssignmentIndividual - favors specializationSelf-organizing teams - encourages role interchangeability
CommunicationFormalInformal
Customer's RoleImportantCritical
Project CycleGuided by tasks or activitiesGuided by product features
Development ModelLife cycle modelEvolutionary delivery model
Desired Organizational StructureMechanistic (bureaucratic with high formalization)Organic (flexible and participative, encouraging cooperative social action)

 

 

  • No labels