2022-09-12 ITSDs and Requirements Meeting notes
Date
Attendees
Agenda/Notes
- What should be our approach for gathering requirements for ITSDs (excluding ITSDs that turn into projects)?
- Up-front requirements – All requirements are gathered and approved by the customer before IT begins work.
- Proof-of-concept – High-level requirements are gathered up front, and more requirements are gathered through user acceptance testing. Requirements are considered complete and approved when user acceptance testing passes.
- Some other approaches …
- Dean - Both approaches have merit depending on the situation
- Dan - The proof-of-concept approach is more flexible but makes it difficult for us to estimate our work,
- Sonny question - IT does both approaches today. How are estimates impacted? Dan answered that we don't provide estimates today for work but are being asked to do so.
- Dan shared his concern that the proof-of-concept approach often leads to new requirements and requests being added to the original ITSD.
- Dean suggested:
- New requirements and requests should be put into new ITSDs.
- Proof-of-concept requests can be vague at first, and filling the details in later.
- All attendees agreed with Dean's approach