INFO 380 Lecture Notes - Lecture 3: Deliverable
INFO 380 Lecture 3
- Determine approach
o Methodologies, such as waterfall, parallel, v model, agile
▪ Waterfall method – series of steps
• Cons: tech might be out of date by the time released, harder to
respond to change, people often don’t know what they want
▪ Agile – incrementally build solution
• Deliverable is working code
• Backlog – working list of deliverables, function, + priority
• Sprint: plan spring, do work, daily stand up, demo, retrospective
• Pros: frequent software delivery, continuous user involvement,
quick response to change, multidisciplinary teams
• Cons: can be hard to budget/contract for, requires team discipline
• Good for: web development, digital marketing + product design,
app development, UX/concept design
• Bad for: infrastructure projects, security projects, packaged
software w many dependencies
o Requirements specification document – details all requirements
- Work plan
o Structure:
▪ Hierarchical decomposition of work to be done
▪ Identifies major project phases
▪ Gives stakeholders + team members project estimates
o Resources
▪ Assign team members
▪ Make sure tasks are fit + not overloaded
o Dependencies – tasks that must be completed before other tasks can be
completed
▪ E.g., resource approval, software/hardware installment, UI design before
coding, coding before testing, etc.
o Estimate tasks
