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.
...
Consider Waterfall if: When to Use Waterfall and When to Use Scrum
- Customers know largely what they want in advance and do not expect major changes.
- Business users involvement will be high during initial planning and testing phases and on The team has done similar projects before and full scope of work is known in advance
- Except for reviews, approvals, status meetings, etc., a business user presence is not strictly required after the requirements phase. Meetings can still occur on an "as needed" basis during development.
- Any feedback from users is either addressed in a subsequent project or not at all
- You’re working with fixed-price / fixed-bid contracts
- The team has done similar projects before and has a well-defined path to delivery
- You’re working with fixed scope unchanging projects
- You anticipate only minor mistakes throughout the project
Consider Scrum if:
- Your customer does not know exactly what they want at first or could change their mindProject has a high degree of complexity and uniqueness (high risk)
- Business users involvement is recommended at daily scrum .and has early opportunity
- Priority shifts can occur during mid-sprint
- The final product may not be fully defined and the details can unfold iteratively over multiple sprints.
- Some part of the project is different or is of moderate complexity
- You want the option of closing a project early once sufficient value is created (avoiding "everything but the kitchen sink" pitfall)