ARTICLE · How software is shaped
The software development life cycle
Building a streaming service begins with deciding whose problem it solves. The development life cycle keeps that question connected to design, delivery, and maintenance.
The software development life cycle
YouTube stays disconnected until you choose to load this player. Loading connects to Google/YouTube, which receives your IP address and may use cookies or browser storage.
Building a Netflix competitor is ambitious enough to expose every stage of software work. A video player alone does not make a service. Someone has to find content, understand access, recover from playback failure, and return later to a coherent experience.
The life cycle gives those concerns a sequence of conversations: discover the need, define the scope, design a solution, implement it, test it, release it, and learn from its operation. Real projects revisit earlier decisions as new evidence arrives.
Let one small release answer a real question#
A first release might test whether a particular audience can find and finish a short lesson. That requires a complete journey, but not a recommendation engine, original television division, and global subscription business.
The result feeds the next decision. If viewers cannot find the right lesson, a faster encoder may not address the immediate problem. If playback fails on their devices, more catalog entries will not make the existing experience usable.
The research unit and capstone sprints connect these stages in the course. Keep a thread from one participant's problem to one acceptance criterion to one observed result. That thread is more valuable than producing a separate document for each stage without letting any stage influence the next.
See also