Software Development Life Cycle

Week 1

design phase

requirements gathering, analyzing requirements, design

development phase

develop, test, user acceptance testing

delivery phase

release, maintenance

methodology

category of concepts and practices

framework

implementation of methodology

Scrum

2-4 week sprints, defined roles

Kanban

visualize work on a board, focus on flow

Extreme Programming (XP)

engineering focus, pair programming, test-driven development

Lean

uses manufacturing principles for software

SAFe (Scaled Agile Framework)

needed for large organizations to deploy agile at scale

Agile

flexible, iterative, collaborative, adaptable, incremental delivery, a methodology

Big Bang

straight to project development

Waterfall

SDLC completed in order, common myth is that you can’t go back to previous steps

sprint

fixed timebox of incremental and shippable work

sprint planning

meeting at the beginning of sprint to schedule work and assign story points

daily standup

15 min daily sync of progress yesterday, today, and blockers

sprint review

meeting at the end of sprint to show completed work to stakeholders and get feedback

sprint retrospective

team-only meeting to reflect on sprint

backlog refinement (grooming)

sessions to estimate and prioritize backlog items

release planning

higher-level planning at the feature or product level, when they will be delivered across multiple sprints

user story

individual feature or requirement

user epic

group of related features broken up into stories

story points

level of difficulty of user story

velocity

sum of story points completed during sprint